Thanks for your reply. This is certainly a good idea, just doubt if this should be enforced this way.
Tamcy On 11月29日, 下午11時16分, "Mike Squire" <[EMAIL PROTECTED]> wrote: > I think what you might want to do is redirect to another action upon > success. It's generally a good idea to do this after you store something on > the server anyway to prevent duplicate entries from browser refreshes. > > Cheers, > Mike. > > On 11/29/06, Tamcy <[EMAIL PROTECTED]> wrote: > > > > > > > > > Hi devs, > > > Just tried switching my projects to the latest alpha and found this > > issue. I have an action "Post" to handle user input, validation and > > saving inside one action (yes there is a reason of doing so). During > > input or validation fails, user will be asked to correct the field > > values and the form is shown. I use a fillin filter to repopulate the > > field data. When validation and saving succeed, the action will direct > > the user to a successful view, which the form doesn't exist. However > > this now triggers a form not found exception. So I'd like to ask if > > there is any particular reason for such change, or if an extra field > > like "raise_error" (if form doesn't exist) can be added to the > > validate.yml / filter.yml file. Thanks. > > > Tamcy-- > Mike Squire > [EMAIL PROTECTED] 隱藏被引用文字 -- 顯示被引用文字 - --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony developers" 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/symfony-devs?hl=en -~----------~----~----~----~------~----~------~--~---
