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
When Woo is activated, it seems to conflict with the require.js loading that properly allows the content WYSIWYG to render. The end result is that you can click the 'Edit' link on a post / page, you get the pinwheel momentarily, but then the content area does not become editable. The title works fine, and if you disable WYSIWYG editor in FEE, all works as expected.
The text was updated successfully, but these errors were encountered:
I've been troubleshooting the hell out of this, and so far no luck. Javascript naming / loading conflicts aren't my specialty, unfortunately. However, I'm compelled by an important project to get this sorted out, so I'll be sure to post anything I discover back on this thread.
Know any Aloha / Require.JS geniuses whose brains I could pick? :)
WooCommerce and FEE seem to have a bit of an issue playing nicely. :)
http://d.pr/i/lcwp
When Woo is activated, it seems to conflict with the require.js loading that properly allows the content WYSIWYG to render. The end result is that you can click the 'Edit' link on a post / page, you get the pinwheel momentarily, but then the content area does not become editable. The title works fine, and if you disable WYSIWYG editor in FEE, all works as expected.
The text was updated successfully, but these errors were encountered: