WooCommerce products not editable after Cornerstone update

Support
#1

After updating to the latest version of Cornerstone we are unable to edit products in WooCommerce. Please help!

The error displayed is “A conflict on the front end of your site has prevented the preview from loading.”

We noticed these errors in the browser console log:

EmberError
description
:
undefined
fileName
:
undefined
lineNumber
:
undefined
message
:
“Assertion Failed: You cannot use the same root element (body) multiple times in an Ember.Application”
name
:
“Error”
number
:
undefined
stack
:
“Error: Assertion Failed: You cannot use the same root element (body) multiple times in an Ember.Application↵ at EmberError (https://www.mitegen.com/wp-content/plugins/cornerstone/assets/dist-app/js/cs-vendor.js?ver=2.1.2:19423:21)↵ at assert (https://www.mitegen.com/wp-content/plugins/cornerstone/assets/dist-app/js/cs-vendor.js?ver=2.1.2:7123:13)↵ at Object.assert (https://www.mitegen.com/wp-content/plugins/cornerstone/assets/dist-app/js/cs-vendor.js?ver=2.1.2:19235:34)↵ at Class.setup (https://www.mitegen.com/wp-content/plugins/cornerstone/assets/dist-app/js/cs-vendor.js?ver=2.1.2:43617:24)↵ at Class.setupEventDispatcher (https://www.mitegen.com/wp-content/plugins/cornerstone/assets/dist-app/js/cs-vendor.js?ver=2.1.2:4310:18)↵ at Class._bootSync (https://www.mitegen.com/wp-content/plugins/cornerstone/assets/dist-app/js/cs-vendor.js?ver=2.1.2:4229:14)↵ at Class.didBecomeReady (https://www.mitegen.com/wp-content/plugins/cornerstone/assets/dist-app/js/cs-vendor.js?ver=2.1.2:5243:20)↵ at invoke (https://www.mitegen.com/wp-content/plugins/cornerstone/assets/dist-app/js/cs-vendor.js?ver=2.1.2:1335:16)↵ at Queue.flush (https://www.mitegen.com/wp-content/plugins/cornerstone/assets/dist-app/js/cs-vendor.js?ver=2.1.2:1399:11)↵ at DeferredActionQueues.flush (https://www.mitegen.com/wp-content/plugins/cornerstone/assets/dist-app/js/cs-vendor.js?ver=2.1.2:1207:17)”
proto
:
Error

#2

Hello There,

Thanks for writing in! You have mentioned that after the update your site no longer works. I found out that you are using CloudFlare. Please always keep in mind that after doing every updates, you must clear your site cache first before testing your site. In your case, you will have to do the following:
1.) Please log in to your CloudFlare account and enable the development.
2.) Login to your WordPress dashboard, and do the theme or plugin updates.
3.) After the updates, if you have installed a caching plugin, please clear the plugin cache as well.
4.) Go back to your CloudFlare account and purge everything.
5.) Disable the development mode and you are good to go.

For best results, please make sure that you are using the best recommended CloudFlare settings from this tip:
https://xthemetips.com/using-cloudflare-rocket-loader-with-x-pro-and-x5/928/

Hope this helps.

#3

Thanks @RueNel.

We did both clear our sitewide Cloudflare cache (purge everything) and WPengine cache after making the X-theme and Cornerstone updates. (Though I’m not sure what your step one suggestion to “enable the development” means.)

As a sidenote: we don’t employ a caching plugin and neither Rocket Loader or Minification in Cloudflare are turned on. As a precaution, I did have Cloudflare exclude /x/* from caching and disable performance enhancements.

We’re still experiencing the problem as described last week. Any ideas as to our next move?

#4

We got to the bottom of it: the new version of Cornerstone and Breadcrumb NavXT conflict.

We wouldn’t need Breadcrumb NavXT, if X-theme supported Woocommerce breadcrumbs of the style home > shop > category-name > product-name. Any chance support for that is on your development list?

#5

Hello There,

Could you please update to the latest versions?
Our latest versions are:

  • Pro theme 1.2.3
  • X theme 5.2.2
  • Cornerstone 2.1.3

This latest release contains fixes for several issues so be sure to check out the changelog (http://theme.co/changelog/).

The category name in the breadcrumb is added in our enhancement lists as a feature request. this will be taken into consideration for future development.

Best Regards.