-
-
Notifications
You must be signed in to change notification settings - Fork 122
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
Spree.user_class not using my specific class #169
Spree.user_class not using my specific class #169
Comments
Hey @EmCousin, thanks for reporting this issue. It looks a legit bug to me and I'll try to investigate further. |
Currently, when this class is set with a custom value using an initializer in the host application, it is not having any effect because this line is always overwriting the custom value with the default one. Ref: solidusio#169
@EmCousin after a second thought, with the help of @tvdeyen, we realized that this extension is meant to be used with the |
Hi @kennyadsl, first, thank you for your answers. About my use case : I plugged the This installation is rather classic, with a I'm following these guidelines to do so. It works perfectly, except for the Is that information relevant enough? |
Sure, thanks for the detailed explanation. I think the issue here is with |
I'm having a look at that gem right now to see if we can get read of the |
I've opened solidusio-contrib/solidus_reviews#53 which should allow you to use the extension without |
Hi,
I'm following the guidelines to set a custom auth system on my app's backend.
I have this line in my
config/initializers/spree.rb
file :but when booting the app or running the rails console, hitting
Spree.user_class
still returnsSpree::User
.I believe this is due to this line, that is executed after loading the initializers, thus setting
Spree.user_class
back toSpree::User
.I've been able to workaround this issue by overriding the related initializer declaration in my main config file:
Questions
Thanks in advance!
The text was updated successfully, but these errors were encountered: