X Theme and WPML cs-vendor.js error

[TechCritic]

Hello,

We are using X Theme Pro on our site with Version: 1.2.7

We are also using the latest WPML plugin for translation.

We are experiencing trouble creating a copy of header and footer. While trying to copy, we see the following error in the console

cs-vendor.js:19500 ReferenceError: error is not defined
at cs.js:48760
at tryCatch (cs-vendor.js:51261)
at invokeCallback (cs-vendor.js:51276)
at publish (cs-vendor.js:51244)
at publishRejection (cs-vendor.js:51179)
at cs-vendor.js:40727
at invoke (cs-vendor.js:1335)
at Queue.flush (cs-vendor.js:1399)
at DeferredActionQueues.flush (cs-vendor.js:1207)
at Backburner.end (cs-vendor.js:521)
defaultDispatch @ cs-vendor.js:19500

[ruenel]

Hi @TechCritic,

Thanks for writing in! Pro 2.35 is now available in automatic updates! This release contains fixes for several issues so be sure to check out the changelog (https://theme.co/changelog/). Please do update to the latest version. After doing the updates, always remember to clear all caches when updating so that the code from the latest release is always in use. This will help you to avoid any potential errors.

Please let us know how it goes.

[TechCritic]

We tried updating the theme to the latest version, all it did was break the layout. Do you know why?

[mldarshana]

Hi There @TechCritic

Most common issues after updates are related to caching, child theme customizations or plugin conflicts.

Could you please try following the recommendations below and see if you can resolve your issue.

1. If you’re using CDN service like CloudFlare, you need to login to your CloudFlare account and purge full cache.
2. If you’re using a caching plugin on your server, you need to purge server cache as well.
3. Head over to X/Pro -> Settings page and clear style cache.
4. Clear your browser cache as well before testing.

If you’re still having issues and if you’re using a child theme, you can then switch to your parent X/Pro theme and further test your issues.

If you’re still having issues, you need to disable your 3rd party plugins and test for a plugin conflict as well. If the issue resolved, you can then activate your plugins one by one to see which plugin cause the issue.

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.

Thanks!