|
Jason, do you have config.gem "authlogic" in your environments file?
Yes, I do.
I even installed the authlogic gem on the server since I was getting some gem dependency errors as well. Which controllers rely on authlogic? I've added it to ApplicationController and CatalogController (since I've had to override those anyway). Others that will need the before_filter? There's some larger issue than using the activate command in the controllers. I don't believe you should need to call activate. The demo app is running fine without calling activate. Something's not configured correctly somewhere as Authlogic mixes into the controllers.
Even though it is working in the demo app is it known to be working with a fresh rails and installation of the blacklight plugin?
Jason, I'm in the middle of installing BL in a fresh rails application for the first time. I'd say the instructions are wrong in several places and we need some serious work on this, so I'm going to get on it ASAP.
Anyway, once I got things up and running, I had no load issues. No errors with the controllers, etc. Did you remove application_controller.rb from the main rails app? Also, do you have require File.join(File.dirname(__FILE__), '../vendor/plugins/engines/boot') above the initializer and config.gem 'authlogic' config.plugin_paths += ["#{RAILS_ROOT}/vendor/plugins/blacklight/vendor/plugins"] config.plugins = %W(engines blacklight acts_as_taggable_on_steroids resource_controller) inside? I believe this was fixed when we ditched auth_logic (to avoid dependency on bcrypt to avoid problems for windows users) and started using simplest_auth instead.
|
|||||||||||||||||||||||||||||||||||||||
before_filter :activate_authlogic
In my controllers seems to have solved this issue from cropping up occasionally.
http://www.themomorohoax.com/2009/02/23/authlogic-session-notactivated-you-must-activate-the-authlogic-session-base-controller-with-a-controller-object-before-creating-objects