Uh Oh! Content Failed to save on Movimentogroup.com

[FPStechdept]

Hi. We currently can’t save on our website:

https://movimentogroup.com/

Can you help me out?

I also can’t save the license when I press enter I just get a blank screen,

[ruenel]

Hello @FPStechdept,

Thanks for writing in!

First of, there is a JS error on the page. This is because you have added an invalid JS code.

<script src=\"//static.getclicky.com/js\" type=\"text/javascript\"></script>
<script type=\"text/javascript\">try{ clicky.init(100918733); }catch(e){}</script>
<noscript><p><img alt=\"Clicky\" width=\"1\" height=\"1\" src=\"//in.getclicky.com/100918733ns.gif\" /></p></noscript>

The proper way of adding this to your site is by installing “Insert Headers and Footers” plugin (https://wordpress.org/plugins/insert-headers-and-footers/). Once installed, please go to Settings > Insert Headers and Footers > Footer and insert the code.

By the way, I noticed that you are using an older version of the theme. X 6.4.6 and Cornerstone 3.4.6 are now available in automatic updates! This release contains fixes for several issues so be sure to check out the changelog (http://theme.co/changelog/). Please do update to the latest version. After doing the updates, always remember to clear all caches (if you are using WP Rocket, WP SuperCache or W3 Total Cache) 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.

[FPStechdept]

Hi,

I removed the code but unfortunately I am still having the same issue. And I still get a blank white page once I register the theme.

Any other ideas?

Thanks!

[friech]

Hi @FPStechdept,

You updated the X theme, but not the Cornerstone. To update the Cornerstone easily, please navigate to plugins panel, deactivate and delete the Cornerstone, then navigate to X > Validation, wait for a few seconds and X will automatically install a compatible version of Cornerstone for you.

Remember to clear all your caching features (plugin, server-side, CDN, and browser’s cache) after updating so that the code from the latest release is always in use. This will help you to avoid any potential errors.

If you still experiencing the issue after the updating, please do a testing for a plugin conflict. You can do this by deactivating all third-party plugins, and seeing 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.

Let us know how it goes,
Cheers!