The primary reason is so that I can use the security component to require that data is sent using POST to my functions that update data. I think It's also generally a cleaner to separate the GET functions from the POST ones--this way I don't have to have conditional statements either.
On Jun 4, 3:59 pm, Grant Cox <[EMAIL PROTECTED]> wrote: > Validation errors are stored in the model, and transferred to the view > when the page is rendered. You could copy them into the session, then > redirect, then read from the session, but this doesn't seem like the > best solution. Can you give me an example of why you shouldn't be > submitting to the same action? > > The only thing I can think of is where the submit form is actually a > small element of a greater page (like a "create account" form down the > side of every page). This would submit to a /accounts/create action, > but I would expect that any errors are then rendered in a new "/ > accounts/create" page - it wouldn't need to remain on whatever content > page I was on when I decided to create an account... --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Cake PHP" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~----------~----~----~----~------~----~------~--~---
