You got some nice functionality there. I think it could be reorganised a bit. At least from how I see a ticket system. I went with a slightly different approach a few years ago when I needed similar functionality. It is the same basic functionality but the code has a different organisation from your code. http://bakery.cakephp.org/articles/view/ticket-component-resetting-user-passwords
-The component deals only with ticket management and is the only place where tickets are created and managed. -Generally components should not have their own models I hear but in this situation it is totally valid, I think. -The controller uses the component to create and check and use tickets, for password resets in this case. -Another controller uses the same ticket component to keep sessions alive and "pseudo authenticate" requests from embedded plugins. I still use it and like it. Maybe you see some detail or two you like. /Martin On Oct 24, 10:51 pm, Smelly_Eddie <[EMAIL PROTECTED]> wrote: > Allowing users the ability to change passwords is a no brainer. > > But what do you do if a user losses their password? Several months > ago I wrote a very simple component that works in conjunction with my > user model to issue tickets to user emails. > > The ticket can be retrieved via email and allows users to enter a new > password. > > The tickets are valid for 24 hours, carry a unique code that aligns to > that users email. It is the bet way I could think to solve this > issue. > > If you want to check it out and share advice, please do. > > http://edwardawebb.com/programming/php-programming/cakephp/reset-lost... --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CakePHP" 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 -~----------~----~----~----~------~----~------~--~---
