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
I know scaffolding is not for production use but I'd like to have my
authentication and profilation system working booth in dev and
production scope!
I'm here to tell you thath code i've posted before generates errors...
it was only to suggest a way, not a solution!
I don't think this is a
Well, and what exactly is 'not pretty' at your solution? Except for
fact that it doesn't care about value in var $scaffold of current
controller, off course...
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
CakePHP
Hi,
I'm in truble with AuthComponent 'cause i want to use scaffolding for
simple tasks but I need to restrict access to the application.
Diving into the source I found the point o problem in the
AuthComponent source file (/cake/libs/controllers/components/auth.php
#265).
Inizialization check
The prettier way to solve this would be to use cake's `bake`
application to create all of the methods in a scaffolded way. The
issue here is that if you decide to reconstruct your database and/or
model, you'd have to delete your cache files *and* re-bake your
controller and view files. However,
the best way to solve it definitely to add more !
something likeSCAFFOLD 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
