Hobo 0.6.1 released
Posted by
Tom | August 25, 2007 6 Responses comments

Not too bad — only one day later than advertised :-) It’s time to

gem update hobo

or

svn up vendor/plugins/hobo

Not content to fix a few of the problems in 0.6, we’ve added some major new features in 0.6.1

There’s a major overhaul to the Ajax part update mechanism. It’s now more secure and can cope with parts that need access to local variables.

Hobo now supports multiple user models, so you could for example have a separate model for regular users and administrators. Each has its own login and signup pages.

As always, see the changelog for the nitty gritty.

Reader Comments Add your comment »

Thanks for the great software. I am trying to figure out how to use the new user authentication system in 0.6.1. Is it documented anywhere yet? If not, I guess I’ll have to brew my own pot of Darjeeling…

Great news the multiple user security is just what I wanted. Thank you tom that has saved me some work :)

Keith – first check out the changelog.

You could also try something like this:

  • Create a new app with the hobo command
  • ruby script/generate hobo_user_model administrator
  • ruby script/generate hobo_user_controller administrator

It’s worth having a look at user.rb and administrator.rb in app/models.

Then fire up the server and have a look at

  • /user_signup
  • /user_login
  • /admin_signup
  • /admin_login

Hi Tom,

Maybe I’m missing something, but the user tables don’t appear to be created. Is there a migration missing? After some trial and error, I created a user table with ‘username’, ‘password’, ‘crypted_password’ and ’salt’ fields and was then able to create users.

I then found that the ’show’ controller action was not working, apparently because of a missing ‘humantype’ method. I changed ‘humantype’ on line 4 of ‘generators/hoborapid/templates/themes/default/views’ to ‘typename’. That seems to work.

Now I seem to be back on the track.

Keith

Keith – we used to generate a migration stub which you could modify to add your own fields. We don’t do that anymore because we now generate the whole migration for you. Add your app specific user fields to the fields do block in user.rb, then run script/generate hobo_migration

Oh – and the other one was indeed a bug. I could have sworn I checked that was working :-)


Write a Comment

Please do not use blog comments for support or reporting bugs.

Please use the hobousers google group for help and support.

Comments are formatted using markdown. To include code, either quote it in `backticks` or indent a code-block by 4 spaces.