I am on Rails 3 and using authlogic, I followed Ryan Bates RailsCast #160 on the matter and things worked (although the cast was using an older version). I relate to your pain though. I know there is light at the end of the tunnel but I have been cursing a lot and having flashbacks to my C#.net days.
Good thing is the Rails community overall is pretty helpful. If you can give me some more specifics I could compare with my code. Also, may or may not make a difference but I am using Ruby 1.9.2. David On Fri, Oct 8, 2010 at 8:56 AM, Marnen Laibow-Koser <[email protected]>wrote: > aperture science wrote: > > I have been trying for a few days to set up a basic user registration/ > > login system with rails 3 and nearly every single piece of > > documentation is outdated. > > Probably because Rails 3 just came out and not everything's been updated > yet. > > > Restful_authentication has several git > > branches, none of which appear to result in a working installation. > > All of them leave me with "could not find generator authenticated". > > Glad to hear it. restful_authentication is bad. Avoid. > > [...] > > authlogic finally got installed and I could generate some models but > > the documentation broke down when the singular guide I could find for > > rails 3 was unable to account for an uninitialized constant > > userSessionController. I could not find much of any documentation on > > the general "uninitialized constant" error anywhere. > > It just means that you have a constant (usually a class name, but could > be any constant) that the interpreter has never heard of. In this case, > that means that it wasn't seeing the UserSessionController definition. > > There are people using Authlogic with Rails 3, I think. A quick Google > search on "authlogic rails 3" yields lots of hits. > > > > > I still see most references saying to use "script/*" method. > > > > Am I better off downgrading to some old version of rails? > > Probably not. > > > Or have I > > just been horribly wrong in everything? > > I don't know. > > > > > > > I would really like to use rails for my projects, but it seems as > > though there is no unification in the project. > > There's lots of unification in the Rails project. Third-party gems are > another story, of course. > > > Nothing works together > > from moment to moment, and updates seem to break every thing. > > That's not really true in general. You're coming in as version 3 -- a > complete rewrite -- gains traction. Of course things will break. > > > If > > rails 3 is too new, what is the recommended rails version with > > compatibility with plugins in mind? Or can anyone suggest a > > registration/authentication framework/plugin for rails 3 that has > > concise clear and functional documentation that isn't fragmented and > > pieced together from semi-working examples taken from blog sites? > > Authlogic should work, from what I understand. Have you taken the time > to understand the Rails framework and the Ruby language before getting > plugins working? > > Best, > -- > Marnen Laibow-Koser > http://www.marnen.org > [email protected] > -- > Posted via http://www.ruby-forum.com/. > > -- > 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 [email protected]. > To unsubscribe from this group, send email to > [email protected]<rubyonrails-talk%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/rubyonrails-talk?hl=en. > > -- 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 [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
