All elements return "undefined"

[franticape]

Hello,

I suspect there might be something in my environment creating this but I can’t figure out what it is but any element I add in cornerstone can’t be edited. it says it’s undefined.

I tried:

• revoking and readding the license
• updating the theme
• moving the site to “local by flywheel” as a test
• clearing cache
• test from another browser and another pc
• test in incognito
• test with all the other plugins disabled

I wonder if you can take a look at the site and maybe check what should I test next, because I’m out of ideas.

In case this is useful, I suspect that there’s some sort of outbound call to you that might be blocked on your end? Because before this rarely happened and it just “went away” after just s few mins, however, I’m totally blocked and have been for 2 days if not more and nothing seems to work.

I own the platform it’s in (sandboxcms) and I’ve built many sites without issues and haven’t had any config change in ages.

You can recreate the error by just opening any page with cornerstone (untested it in all the ones that exist on that site). Then just add a new element, section or anything and try to edit it.

For the sake of this conversation test it on “homepage 2” (front-page) or the header.

[prakash_s]

Hello @franticape,

Thanks for writing to us.

I checked your site it seems that the page builder is working fine on my end. It might be an issue with the browser cache I would suggest you please clear your browser cache and recheck it or check it in the private mode of the browser. I have tested it in the Google Chrome browser version 120.0.6099.234. Please have a look at the given screen recording video. If the issue persists please let us know the browser and its version.

Thanks

[franticape]

back when you checked, everything was ok, even without cleaning or clearing anything and today the problem returned.

in general why is this issue created? mean what is it that cornerstone is trying to do and is failing? because i note this issue from time to time and it always “just gets fixed” after a while, the thing is that i’ve tested on different pcs, different browsers so i could rule out a cache issue and the problem still remains there for a while until it just goes away.

[franticape]

in case this might help, here’s the error i get now:

ERR_HTTP2_PROTOCOL_ERROR 200 (OK)

    app.react18.7.4.9.js?ver=7.4.9:6 Failed to get late app data {code: 'invalid_json', message: 'The response is not a valid JSON response.'}
(anonymous) @ app.react18.7.4.9.js?ver=7.4.9:6
Promise.then (async)
(anonymous) @ app.react18.7.4.9.js?ver=7.4.9:6
requestIdleCallback (async)
Ny.onMount @ app.react18.7.4.9.js?ver=7.4.9:6
M @ app.react18.7.4.9.js?ver=7.4.9:5
(anonymous) @ app.react18.7.4.9.js?ver=7.4.9:5
M @ app.react18.7.4.9.js?ver=7.4.9:5
S @ app.react18.7.4.9.js?ver=7.4.9:5
q @ app.react18.7.4.9.js?ver=7.4.9:5
(anonymous) @ app.react18.7.4.9.js?ver=7.4.9:5
Ur @ react-dom.min.js?ver=18.2.0:10
El @ react-dom.min.js?ver=18.2.0:10
(anonymous) @ react-dom.min.js?ver=18.2.0:10
v @ react.min.js?ver=18.2.0:10
ce @ react.min.js?ver=18.2.0:10

My browser version is Version 120.0.6099.225, however i don’t have any updates pending, yet yours seem to be newer. this happens on firefox also, though, so i don’t think the problem is the browser version.

[tristup]

Hi @franticape,

It seems that you are having a similar issue described in the following thread.

Cornerstone inspector won't load on multisite

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 …

Hope it helps.
Thanks

[franticape]

this site uses NGINX, but here isn’t a proxy mode (that’s a plesk thing and we don’t use plesk). the proxy mode, if i recall correctly, does something like porting content from apache to nginx (or the other way around), i’m not sure the problem applies to me but a the same time i wouldn’t know how i could rule this out since i have nothing similar to the other person’s config.

[prakash_s]

Hello @franticape,

We now use the WordPress Rest API for saving and it looks like your web host does not support it. Please ask your web host to support WordPress Rest API or whitelist the URL in the following screenshot.

Hope it helps
Thanks

[franticape]

Hm, may i know what it should show? because if i go to /wp-json i can see everything. i’m looking into it but all the info i can get is highly appreciated.

[tristup]

Hi @franticape,

If the specific API endpoints are whitelisted, it should return 200 instead of 403 what mentioned by my colleague in the screenshot.

Thanks

[franticape]

I’m looking into it (my company owns the server and AFAIK we don’t really have any type of restriction but i asked the systems team about it). however the error is a 401, not a 403, that’s why i asked about it because if the return is a private one, then it won’t be visible by calling to it manually (this is a guess, though).

[tristup]

Hi @franticape,

The error return code might vary from case to case, but it should return 200 if it worked.

Thanks

[franticape]

Got, it, ok, thanks for the info. i’m checking with my team what’s going on because for example i checked it 1h ago and it was giving 401 yet the editor was working flawlessly. i checked just now and i get the 401 in the endpoint and i also can’t see it working.

another thing i noticed is that this only happens in sort of “local” environments (even though this sandbox is actually live).

It’s a very very weird issue that i hadn’t seen before in what more than 5 years working with pro/cornerstone/x (ever since v1.2)

[tristup]

Hi @franticape,

Please let us know what happened after your team whitelisted the endpoint.

Thanks