Hi, I have developed a mini Rails app using Rails 2.0.2, RESTful authentication and Acts as State Machine. It has the following features: 1. Login 2. Logout 3. User Activation 4. Forgot Password 5. Reset Password You can check out the code from: svn checkout *http*://simply-rich-authenticator.googlecode.com/svn/trunk/simply-rich-authenticator-read-only Happy New Year! -- http://www.rubyplus.org/ Free Ruby and Rails Screencasts --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
Hi, On 29-Dec-07, at 4:13 PM, Bala Paranj wrote:> Hi, > > I have developed a mini Rails app using Rails 2.0.2, RESTful > authentication > and Acts as State Machine. It has the following features: > > 1. Login > 2. Logout > 3. User Activation > 4. Forgot Password > 5. Reset Password > > You can check out the code from: > > svn checkout *http*://simply-rich-authenticator.googlecode.com/svn/ > trunk/simply-rich-authenticator-read-only > >Nice! I think you need a space in that command: svn checkout http://simply-rich-authenticator.googlecode.com/svn/ trunk/ simply-rich-authenticator-read-only -- I did something pretty much exactly like this just before 2.0 was released, except with role_requirement and some timezone stuff. I also needed to add some scope functionality that was pretty specific to the applications I write. It was not as straight forward as I''d hoped. I stopped doing much with it, mostly because I took the opportunity to upgrade one of my applications from 1.0.x to 2.0.x (two years later), but also because I was getting a bit concerned about maintaining such a thing. It seems to me that the modifications I had to do were not specific to a single plugin but were changing/depending on multiple plugins -- the plugins don''t seem particularly modular... and non-modular things don''t upgrade nicely. What do you, and everyone else, find with RoR and plugins. Is there something I''m missing (please say I''m missing something) or is there really a modularity problem? Cheers, Bob> Happy New Year! > > -- > http://www.rubyplus.org/ > Free Ruby and Rails Screencasts > > >--~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I think there is a bug in your password reset code. undefined method `password_reset_code='' You are calling a variable I believe. Jon Bob Hutchison wrote:> Hi, > > On 29-Dec-07, at 4:13 PM, Bala Paranj wrote: > >> Hi, >> >> I have developed a mini Rails app using Rails 2.0.2, RESTful >> authentication >> and Acts as State Machine. It has the following features: >> >> 1. Login >> 2. Logout >> 3. User Activation >> 4. Forgot Password >> 5. Reset Password >> >> You can check out the code from: >> >> svn checkout *http*://simply-rich-authenticator.googlecode.com/svn/ >> trunk/simply-rich-authenticator-read-only >> >> > > Nice! > > I think you need a space in that command: > > svn checkout http://simply-rich-authenticator.googlecode.com/svn/ > trunk/ simply-rich-authenticator-read-only > > -- > > I did something pretty much exactly like this just before 2.0 was > released, except with role_requirement and some timezone stuff. I also > needed to add some scope functionality that was pretty specific to the > applications I write. > > It was not as straight forward as I''d hoped. I stopped doing much with > it, mostly because I took the opportunity to upgrade one of my > applications from 1.0.x to 2.0.x (two years later), but also because I > was getting a bit concerned about maintaining such a thing. > > It seems to me that the modifications I had to do were not specific to > a single plugin but were changing/depending on multiple plugins -- the > plugins don''t seem particularly modular... and non-modular things > don''t upgrade nicely. > > What do you, and everyone else, find with RoR and plugins. Is there > something I''m missing (please say I''m missing something) or is there > really a modularity problem? > > Cheers, > Bob > > >> Happy New Year! >> >> -- >> http://www.rubyplus.org/ >> Free Ruby and Rails Screencasts >> > > >-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHeXImjlOFXww4P/QRAlO5AKCMWGXbI6Br4iTSD1m6OQaM2UAX8ACeJQxV 21BUkvQwj7l+WSS0maZNtLA=MMZ+ -----END PGP SIGNATURE----- --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---