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.
This is not uncommon on the open source. With the vast number of changes
from Rails 2.x to Rails 3.0 It's my feeling the community has done an
outstanding job of updating the critical documentation. Of course the
conversion isn't complete, but I think your 90% figure is far to high.
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".
I would highly recommend against restful_authentication. Most Rails
developers have moved to the better solutions like Devise and Authlogic.
With Devise: "could not find generator devise" Which I only got
slightly installed after finding some guy's blog entry on the subject.
I'm not sure about Devise, I've started implementing in Rails 3 and had
no problem running the generator with the documented Rails 3 command:
rails generate devise:install
Are you sure that your Rails 3 environment, and Ruby, is installed and
configured properly?
What platform are you using? (Operating system, Ruby version, RVM, etc)
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.
I've not tried Authlogic. However unless "userSessionController" is just
a typo in this forum post I can certainly see why you would get an
"uninitialized constant" error since class names should be upper camel
case (e.g. UserSessionController). That's basic Ruby and has nothing to
do with poor documentation on the part of Rails or Authlogic.
I still see most references saying to use "script/*" method.
Why is that a big deal? Rails 3 documentation
(The Rails Command Line — Ruby on Rails Guides) clearly states the
usage of the new commands (e.g. rails generate (g), rails server (s),
etc.).
Am I better off downgrading to some old version of rails? Or have I
just been horribly wrong in everything?
I'd say no. For anyone starting out with Rails I'd recommend learning
Rails 3.
Given this stuff is all open source I'd say to start getting used to
figuring things out for yourself. This is a community effort. Most
people working on Rails have other jobs as well. Documentation is
"owned" by the community. Rather than complain about the documentation
start contributing to fix it. If you find something wrong fix it and
submit it. I'm sure the Rails team would appreciate such contributions.
I would really like to use rails for my projects, but it seems as
though there is no unification in the project. Nothing works together
from moment to moment, and updates seem to break every thing. 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?
I have, so far, not run into any of the issues you've mentioned with my
experimentation with Devise. I found their documentation to be clear,
concise and accurate. I think you have some other problems with your
setup.
