-
Notifications
You must be signed in to change notification settings - Fork 386
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Potential load-order incompatibility with rails_admin #147
Comments
I had this problem exactly! Thanks for your help... |
OMG <3 |
Closed?! |
Yes this deserves to be closed, although this problem was not exclusive to only production for me. Also appeared in development yet oddly not in test. |
@kirs the issue can be closed, I've added link to the documentation provided by @stas here: https://github.com/NoamB/sorcery/wiki/Known-incompatibilities |
Please notice that the 'Known-incompatibilities' may be outdated (or this issue may be already fixed in rails_admin since 2 years) |
A bit of a follow-up and additional work on problems I've had related to: #74 ... could be useful for the Known Incompatibilities page on the Wiki for some poor soul.
The popular
rails_admin
gem (https://github.com/sferik/rails_admin) mucks around with the User model, similar to Refinery CMS.In addition to renaming the
sorcery.rb
initializer to load before therails_admin.rb
initializer, I found that I had to force Sorcery's inclusion as the final line of my initializer file:ActionController::Base.send(:include, Sorcery::Controller)
That way rails_admin can actually see and manage User records.
Happy to answer any questions. Thanks for this gem, which I enjoy despite the occasional trouble!
The text was updated successfully, but these errors were encountered: