That said, I may be able to shed some light on your specific scenario:

1) By changing via logic I mean that you can no longer check for something like “current_user.present?” to determine whether you have a user signed in, because by nature of what this feature does, there will always be a current_user present. Instead, you will have to determine whether it is an AnonymousUser or a User (the logged in kind), in my case, I include a convenience method, “anonymous?” on both of these classes which responds accordingly.

2) Because at any given time, a user may be a User or an AnonymousUser, and the point of this feature is that you want to treat them the same, each must have the same interface: if you have a “has_role?” method on your User, you will have to define “has_role?” on AnonymousUser, even if it just always returns “false”.

By exemple you say :
“You’ll need to change a little view logic as well. For example, you’ll want to check something like current_user.anonymous? instead of present? to conditionally show your “Sign in” and “Sign up” links.”

How would you implement it?

I Also had problem with things like : “current_user.has_role? :admin” in my views which where causing exception : undefined method ‘where’ for nil:nilclass in the lib rolify (line 29).

I solved it by dropping the class AnonymousUser and using the class User instead…

Could you please elaborate a bit?

Thank you

Congratulations on your quick entry into software development!