Cornerstone issue - infinite spinning loader, unable to edit any page

After updating Cornerstone and X-Theme, cornerstone no longer loads making it impossible to edit pages. All I see is the spinning loader, no error message.

Another poster suggested it was linked to W3 Total Cache which I am not running, so I doubt its that.

Please advise asap - this is obviously an issue for many people.

1 Like

@Gingerfizz_Marketing

Would you mind providing us with login credentials in a secure note? I’d like to take a closer look at what’s going on here. Thanks!

Hey,

Please, answer us when you get back.

1 Like

Ok - so I’ve run the latest update to Cornerstone (v 2.1.3) & X theme (v 5.2.2) & now Cornerstone is loading & I can access each page.

BUT All the formatting has gone making each page impossible to edit. At present, everything looks correct on the front end of the site, but in the back, it’s not usable. Please advise - I will give login details in a secure message.

Hi There,

You some of your files seems to be corrupted during the update. I have resolved those issues for you and then I was able to load Cornerstone editor (See secure note).

Thanks!

Hi - you didn’t read my comment properly - I had already fixed the issue re: loading Cornerstone, BUT all page formatting has been lost, making the site impossible to edit - other users seem to be having similar issues.
Examples of the messed up formatting here: https://ibb.co/j3pbvb & here: https://ibb.co/cJULMG

Please advise how to fix this ASAP as this is preventing me working on the site & costing me valuable time & money!! Thanks.

Hi there,

I checked the page you are talking about, and I see it showing the formatting correctly and it is not like the one you showed in the screenshot:

Would you please kindly use another machine and specifically use the Google Chrome browser and get back to us with the result?

Thank you.

It appears to now be resolved - I was using the latest version of Chrome on a mac & this issue was applying to all other machines that I had tested it on too.

Glad that it is fixed. :slight_smile: