-
Notifications
You must be signed in to change notification settings - Fork 1
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
product_wysiwyg_editor_enabled preference not defined #1
Comments
Ok, I'm guessing, we should add the preference under your configuration.rb file. Currently, I added it within my Spree initializer by following official documentation:
And this fixes the pb |
Thanks @Kulgar, I will have a look and try to make it work if this setting is not available. |
@mrbrdo : well, yes... in fact your gem even fixed some issues I had with spree_globalize and latest spree version. For instance: when searching for products in the CMS (for button links), I didn't have the product names displayed with spree_globalize. I only had an empty blank dropdown even if the product actually exists. This is no longer the case with your gem and I do get the product names properly. And yes, I activated the wysiwyg editor for translations field and so far, I didn't get any other issues. Thanks for your work ^^ Regarding the above issue, I think you would only have to add these two preferences within configuration.rb, wouldn't you? |
No need, these settings are part of Spree config, but it was moved to Spree::Backend::Config in 4.4 (previously Spree::Config). The issue you had with spree_globalize is probably because fallbacks don't work very well with it. Making fallbacks work was probably half of the work for this gem :) |
Oh yeah, right, 4.4 is the version where they cut Spree into several pieces. Ow, and it seems that I'm facing the same issue as the one you posted on spree_globalize: spree-contrib/spree_globalize#99 (creating another issue for that) |
Hello,
I know this gem was tested with Spree 4.3.1.
But just to let you know, with Spree 4.4, I get this error:
I'll try to patch it :-)
The text was updated successfully, but these errors were encountered: