Easiest solution: Use UserEngine. ;)

2006/2/8, da pendragon <[EMAIL PROTECTED]>:
> Hi, first of all, thanks for making the login engine, it suits my needs
> perfectly.
>
> I've been using the login engine for a web application I've developed, but
> I've run into a small problem.
>
> Using before_filter on other controllers works just fine, but I also
>
> want methods in the UserController that is included in the Login Engine
> to be protected in some cases. For instance, I'd like the signup action
> to be unavailable unless a user is logged in (only valid users can add
>
> new accounts). I've added the normal before_filter to the
> UserController, but this is obviously not the correct way of doing
> this.
>
> So in short: how can I secure all actions except login in
> UserController?
>
>
> My thanks in advance for any help you can give
>
> Regards,
> Vegard
>
> _______________________________________________
> engine-users mailing list
> [email protected]
> http://lists.rails-engines.org/listinfo.cgi/engine-users-rails-engines.org
>
>
>
_______________________________________________
engine-users mailing list
[email protected]
http://lists.rails-engines.org/listinfo.cgi/engine-users-rails-engines.org

Reply via email to