I know I'm not speaking for a popular opinion, but consider this: Scaffolding is a good way to get a prototype off the ground and show something to a client nearly instantly. Clients care about authentication. Clients would prefer to see the prototype with authentication working as the authentication is intimately associated with IA, use cases, application flow, what have you. Clients want to be able to visualize the completed application as much as possible.
Finally, for newbies out there, out of the box, auth blanket applies to your controller methods when invoked in the controller. It's totally unintuitive for it to treat scaffolding any differently. So, what's the compelling reason not to support auth in scaffolds? On Jan 29, 11:14 am, Gwoo <[email protected]> wrote: > the best way to solve it definitely to add more ! > something like....SCAFFOLD IS NOT FOR PRODUCTION USE!!!! --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CakePHP" 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 -~----------~----~----~----~------~----~------~--~---
