You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While I don't see any mention of spree_frontend in the gemspec file, the LocaleController inherits from StoreController which is provided by the spree_frontend gem.
As a result I get a uninitialized constant Spree::StoreController (NameError) when I run the server in production. For a reason I can't grasp this is not crashing in development.
I doing solely model translations which has been moved from spree_i18n to the spree-globalize gem for Spree 3.1+. However I am using Spree 2.4 and upgrading is not an option at the moment.
Do I have any other option than requiring a (quite bulky) gem that I have no use for (spree_frontend). We use a separate frontend.
What
The text was updated successfully, but these errors were encountered:
I'm having the same issue. I'm not using spree_frontend and same exception in production env. It only occurs in production because on this environment, all the files are loaded at launch. On development env, the classes are loaded when needed.
The thing I've done so far is just to fork the gem and simply remove this single controller. Works.
I'm just looking into conditionally require this controller so I can go back to the official gem.
While I don't see any mention of spree_frontend in the gemspec file, the LocaleController inherits from
StoreController
which is provided by thespree_frontend
gem.As a result I get a
uninitialized constant Spree::StoreController (NameError)
when I run the server in production. For a reason I can't grasp this is not crashing in development.I doing solely model translations which has been moved from
spree_i18n
to thespree-globalize
gem for Spree 3.1+. However I am using Spree 2.4 and upgrading is not an option at the moment.Do I have any other option than requiring a (quite bulky) gem that I have no use for (spree_frontend). We use a separate frontend.
What
The text was updated successfully, but these errors were encountered: