
Can't seem to disable magic states in production
Reported by Locv39KnvwDeXGpKpisHDaKw | March 13th, 2009 @ 06:54 PM
Having a hell of a time disabling magic states in production. Got it working in development.
I tried putting this in the UserSession model:
disable_magic_states true
I also tried putting this both in an initializer of its own as
well as at the end of environment.rb.
UserSession.configure do |config|
config.disable_magic_states = true
end
Any ideas what I might be doing wrong? This is with Rails 2.2, Authlogic 1.4.3.
Comments and changes to this ticket
-
Ben Johnson March 13th, 2009 @ 07:14 PM
- State changed from new to open
Sounds like a caching issue. Are other config options working?
-
Ben Johnson March 23rd, 2009 @ 03:19 AM
Try updating and see if this fixes the issue. I released a new version today.
-
Ben Johnson March 25th, 2009 @ 02:53 PM
Well you should be able to just set disable_magic_states to true, look at Authlogic::Session::MagicStates. It is impossible for magic states to be validated if it is false.
-
Ben Johnson March 25th, 2009 @ 03:10 PM
I guess it doesn't hurt, the problem is that the names of the modules are somewhat internal. There is no contract between me and you that I won't change them. Where as the configuration option will stay there, and if it changes, I will at least give a deprecation notice or some kind of warning. But I doubt the name will change, and the memory you will save it probably not even noticeable.
-
Ben Johnson April 3rd, 2009 @ 01:20 AM
- State changed from open to resolved
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
Object based authentication solution that handles all of the non sense for you. It's as easy as ActiveRecord is with a database.