I'll give the authorize thing a try again, although I didn't have it in the previous version, I don't think it will make a difference.
I did read a lot about whether to use the salt or not, for other things rather than just the password hashing and Cake doesn't only use it for the password hashing but also for other things, like cookies I believe. So I rather keep using the Cake salt, just not for password hashing. I will give it a shot removing it from the core config and removing my own hashpassword function. Just to see if I get the right behavior. I'm pretty confused at the last thing though. Empty beforeFilter() functions make the controllers behave as intended? that's just weird :) And everything else does look correct. Will give the authorize and salt thing a try tonight, I won't be able to work on it until late today. Maybe the session is confusing the salt when opening an add or edit function and spitting me out straight to "The controller has been saved". (Which would be a bug since if there's problems with the salt and its not letting me into the add or edit form, the flash should say something like "Cannot add controller" or "Cannot edit controller" instead of the message I'm getting. Thanks. On Sep 17, 9:17 am, Miles J <[email protected]> wrote: > Try removing the isAuthorized, especially if there is no logic in it. > That may be the problem, not sure. Everything else looks correct > though. > > Also, if you want to use md5() hashing but not use a salt, just set > the salt to empty in the core config. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
