This particular issue is the framework trying to baby it's users. Telling us that we can't implement our own security practices. It's not even that you can turn it off if you don't want it, you just can't turn it off. You literally have to "deal with it" with a little workaround of some sort. Not that it's super hard to work around, but it is a work around. It's just annoying, and silly.. like I said.
On Jan 18, 1:14 pm, Baz <[EMAIL PROTECTED]> wrote: > Now it's comments like this that help me understand why the developers > sometimes get frustrated with this mailing list. This statement serves > absolutely no purpose. It is a blind criticism without any productive > alternative. > > Frameworks are developed for the mass, not individuals. Meaning, what's > there is going to serve 85% of the people just fine. If you have a _better_ > alternative, then please suggest. > > Otherwise, quit whining. It's not compiled code; it's PHP. If you don't like > it, open up the bloody file and hit the delete key move on. > -- > Baz L > Web Development 2.0http://WebDevelopment2.com/ > > On Jan 18, 2008 1:31 PM, rtconner <[EMAIL PROTECTED]> wrote: > > > > > I'll just say, I love any and all complaints about that auto hashing > > thing. I think it's silly and annoying and shouldnt be part of cake. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Cake PHP" group. To post to this group, send email to cake-php@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
