-
-
Notifications
You must be signed in to change notification settings - Fork 23
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
Solidus Support 0.9 breaks loading of Solidus Auth Devise in Rails 5.2 (and possibly other extensions) #73
Comments
Hi @Noah-Silvera ! I was able to confirm your issue, and it seems I was able to work around it by downgrading SolidusSupport to 0.8.1. Please see Noah-Silvera/solidus-support-0.9-engine-bug#1. Is there a reason you need to use SolidusSupport 0.9.0 on your Rails 5.2 app? Based on https://endoflife.date/rails and https://guides.rubyonrails.org/maintenance_policy.html, support for Rails 5.2 has already ended. Thus, it's not likely we'll update this gem to support Rails 5.2. |
Hey @gsmendoza! Yeah, it can definitely be worked around by downgrading to 0.8.1! I was able to workaround that on my app. |
I appreciate you looking into this and confirming this! |
@Noah-Silvera Good to hear you were able to work around the issue. I'll be closing this issue. |
In solidusio#65 and solidusio#71 they changed how the engine i loaded using the Rails initializers. This updates causes some issues when using Rails <6.1 because the initializers are totally different. The solution is to load the extension outside of the initializer block until we use Rails 6.1 or newer version. Ref: solidusio#73.
In solidusio#65 and solidusio#71 they changed how the engine is loaded using the Rails initializers. This updates causes some issues when using Rails < 6.1 because the initializers are totally different. The solution is to load the extension outside of the initializer block until we use Rails 6.1 or newer version. Ref: solidusio#73.
A change introduced Solidus Support 0.9 #65 causes the solidus auth devise controllers not to be eager loaded on boot in rails 5.2
This results in this error message when trying to access the solidus admin. This is a failure to load a controller constant from solidus_auth_devise
This can be reproduced in an app with the following setup
Rails 5.2.8.1
Solidus 2.11.17
Solidus Support 0.9.0
Solidus Auth Devise 2.5.4
eager_load = true
in development.rbHere is a repository with a pre-setup app to reproduce it.
https://github.com/Noah-Silvera/solidus-support-0.9-engine-bug
If you comment out this initializer block,
The error is resolved.
I suspect this is due to a different in code loading in Rails 5 and Rails 6, which introduced zeitwerk, or a change in how/when railties processes initializers.
The text was updated successfully, but these errors were encountered: