Cornerstone update 3.3.6 is broken. Can't edit my website

Support
#1

Hi I just updated my theme to 6.3.6 and Cornerstone to 3.3.6 and I can’t edit my website no more. Please check the attached screenshot, it says it couldn’t locate the module ‘react’. The editor is stuck on the loading screen. Please help on priority.

#2

Hello There,

Please follow up the steps below:

  1. Ensure everything is up to date according to our version compatibility list here. Please follow the best practices when updating your theme and plugins. Click here for more information.
  2. Go to X > Settings and click on the Clear Style Cache button.
  3. If you’re using a CDN(ex: CloudFlare), please clear the CDN’s cache and disable optimization services. For the CloudFlare you also need to follow the steps below besides the developer mode: https://xthemetips.com/using-cloudflare-rocket-loader-with-x-pro-and-x5/928/1
  4. Test for a plugin conflict. You can do this by deactivating all third-party plugins, and see if the problem remains. If it’s fixed, you’ll know a plugin caused the problem, and you can narrow down which one by reactivating them one at a time.
  5. Remove custom CSS and Javascript from the options or Child Theme and test the case.
  6. Switch to the parent theme to check if the issue persists.
  7. Reset your htaccess file by renaming it to .htaccess-bak. Then in WP Admin Menu, go to Settings > Permalinks and just click the Save Changes button.
  8. Increase the PHP Memory Limit of your server. Click here for more detailed information and how to increase the PHP memory limit.

If you still have problems kindly get back to us with the result of the steps above and URL/User/Pass of your WordPress dashboard using the Secure Note functionality of the post to follow up the case.

Thank you.

#3

I found the conflict. The update relies on loading static resources via query strings. I had installed a plugin which removes query strings from static resources in to improve caching. What can I do to use both the plugins/features?

#4

Hi There,

Please try with the Remove Query Strings From Static Resources With Code solution:

Hope it helps :slight_smile:

#5

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.