On Nov 12, 11:10 am, Action <[EMAIL PROTECTED]> wrote: > Is my aforementioned working method (using /posts/view to handle > comment saving) bad practice? Not at all. I think you're just being distracted by the function name "view" - which probably triggers a response in your brain, based on what you've read of MVC design, that views should never, ever modify the database. In your case, you've got a controller function named 'view' doing controller-y things. Seems completely reasonable.
> If so, is there any way I can save the > data in /posts/addcomment or /comments/add and have it return to the / > posts/view/blog_post_name view with the validation error messages > working? Sure, but why bother? Having Cake automagically handle validation error messages is a nice benefit. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
