Cornerstone inspector won't load on multisite

[Falise]

I’m having an issue where updating from Cornerstone 4.2.3 to any of the 5.x versions breaks the inspector pane as soon as I click something in the preview pane.

I can use the Outline tool to add elements and I can see them appearing in the preview but as soon as I click the search icon in an element (still in the outline tool on the left hand of the screen) I get a loading circle (in 5.33 a circle, in 5.0.11 & 5.1.5 the outline remains totally empty) but nothing else.

I get no errors in the JS console (Firefox & Chrome) and no failed loading urls of any kind.
I do get an error in the JSON response when saving the document that says “No response for path: save”

Switching to the X-theme instead of the X-child does not help. Disabling any / all plugins does not help. Reverting to the default .htaccess does not help.

It is probably worthy to mention that the site is part of a multisite environment and all sites using Cornerstone 5.x suffer the same fate. The only plugin I could not disable is the WordPress MU Domain Mapping plugin.

Can you give any hints or tips on how to debug / fix this?

[marc_a]

Hi @Falise,

Thanks for reaching out!

Please make sure that you have the latest version of the X theme and Cornerstone plugin. Please follow the steps below.

1.) First, deactivate and remove the Cornerstone plugin
2.) Update the X theme to the latest version
3.) Install again the latest Cornerstone plugin

Hope that helps and let us know how it goes.

Thank you.

[Falise]

Hi Marc,

I did all these steps multiple times. I even created a new multisite website to experiment with.
I have found one issue in my .htaccess file, so now I’m one step further and I see this in my browser console:
“Failed to get late app data No response for path: late-data”
What does that mean?

[Falise]

To be complete:
Cornerstone 4.2.3 - works
Cornerstone 5.3.3 - doesn’t
X-theme 8.3.3
WP 5.7.2
Php 7.3.28

[tristup]

Hi @Falise,

If you are still having the issue Failed to get late app data No response for path: late-data, your server might be doing a 301 redirect to automatically add trailing slashes to all requests. You need to remove the 301 redirection or exclude the WordPress Rest API endpoints from it.
To know more on the Rest API endpoints, please go through the following article:

Reference | REST API Handbook | WordPress Developer Resources

If you are getting any other issue, please specify the exact issue you are having along with login credentials for your site in a secure note to examine it further, including:

– WordPress Site URL & Login URL
– WordPress Admin username/password

To create a secure note, click the key icon underneath any of your posts.

Thanks

[tristup]

Hi @Falise,

Unfortunately, the Login URL is not accessible due to the HTTP authentication. I would suggest you provide the credentials for the HTTP authentication to access the Login URL.

Thanks

[Falise]

I’ve disabled it for now

[marc_a]

Hi @Falise,

We can’t log in to your second website where you are having an issue because of the Google Authentication. I suggest that you disable the Google Authentication in the meantime so that we can check it.

Thank you.

[Falise]

Also disabled that!

[tristup]

Hi @Falise,

Unfortunately, submitting the Login page, redirected to the Error 521 page. I have tried refreshing it multiple times but still, it shows the same.

I would request you to check this once and let us know once it is accessible.
Thanks

[Falise]

Cloudflare has been recently installed to block a DDOS attack, it seems you are looking at a Cloudflare screen. On my end the website is accessible. Maybe try a VPN that connects to a Dutch server?

[tristup]

Hi @Falise,

I have checked that through the VPN and it found that the User doesn’t have the Admin privileges to check the issue mentioned by you. I would suggest you give the user admin privileges and let us know to check.

Thanks

[Falise]

You are now a superadmin

[Falise]

So I seems I have fixed the issue by comparing the Apache & Nginx settings in Plesk. The test site that was working had the Nginx Proxy mode enabled, whereas the broken site had it turned off. Turning the Proxy mode ON seems to have fixed the issue.

For our multisite setup we have multiple domains pointing to the same http directory. From there the multisite together with the domain mapping plugin decides which site to show. 99% of the sites work without Proxy mode turned on, but some wp-json requests fail with this setting turned off. This includes themeco related rest calls but also some of the Redirection plugin calls.

I hope this helps someone in the future!

PS Testing the rest of the site now …

[christian]

Hey @Falise,

Thank you for sharing the cause of the issue. What shows up in the console is just Admin Ajax error which is a generic error pointing to a server issue.