[EMAIL PROTECTED] wrote:
I assume that most of your problems are solved now, given what we've discussed on the bakery ;-)
Yes. Thanks. For those people who don't read the bakery comments (or read the text properly like me ;) ), The hash problem was due to the code in the Bakery for the sha1.js file actually being changed by the markup parser ob the page http://bakery.cakephp.org/articles/view/152. This rendered it incomplete and non working. the download code link does not currently work but hopefully, this will be fixed soon. In the interim, please use the sha1.js implementation from http://www.movable-type.co.uk/scripts/SHA-1.html
Except the "headers already sent one" that's probably still unresolved.. i've looked a bit around in the sources (of both dAuth and cake/libs) but couldn't find the real culprit; when i have more time i'll further look into it, or maybe someone else can help you on this for now.
I am sure the headers already sent one is due to the controller flash message from line 195 of the d_auth.php component. I have not used flash message before, so I am unsure how it works, or indeed why it is not redirecting to the new page rather than sending headers on top of the existing page. For the mean time, I will change this to a session flash message so the message can appear on the destination page rather than an intermediate page Paul --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
