Everybody loves restful_authentication, right? RIGHT? Well, along with having plenty of tutorials to get your users registering and logging in, if you want activation you need the acts_as_state_machine plugin. The secret to installing this is to ignore The Google, or else you may get something like:
$ script\plugin install acts_as_state_machine
svn: Connection closed unexpectedly
svn: Can't connect to host 'errtheblog.com': No connection could be made because the target machine actively refused it.
svn: Connection closed unexpectedly
svn: Connection closed unexpectedly
svn: Connection closed unexpectedly
svn: Connection closed unexpectedly
svn: Connection closed unexpectedly
svn: Connection closed unexpectedly
Plugin not found: ["acts_as_state_machine"]
$
Another Google-recommended technique is to install from any number of alternate sites that have hosted this seemingly-hobo plugin over the past couplefew years. They have all been mentioned at one time or another.
However, the secret is to read the output of the plugin install for restful_authentication. Here (as of 2/2009) you will find that the right way to install acts_as_state_machine is (currently):
$ svn export http://elitists.textdriven.com/svn/plugins/acts_as_state_machine/trunk vendor/plugins/acts_as_state_machine
That's all one line, BTW (Blogger sux). Why we have to do an svn ex for something like this is beyond me, but I figure the (typically lazy OSNAP) developers have a good reason. Live and learn!
At least this didn't end in the typical heartbreak of a rails site returning code 500 errors, or a plugin that was abandoned two years ago. Huzzah!
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment