Just upgraded to the latest version of Pro, now when I to to edit any page using the pro editor I just get a blank grey screen?

batybat · December 21, 2020, 8:47pm

Hi I have just upgraded to the latest version of Pro on my staging dev server to test and Im using wordpress 5.6

and now when I to to edit any page using the pro editor I just get a blank grey screen with no content at all?

If I use the browser tools to inspect I get this error…

Failed to load resource: the server responded with a status of 502 ()

app.aced3b2.js?ver=1608554957:42

Object
code: “invalid_json”
message: “The response is not a valid JSON response.”
proto: Object

The file it is looking for is - /wp-json/themeco/data/late-data?_locale=user

I also get these errors listed…

TypeError: Cannot read property ‘elements’ of undefined
at app.aced3b2.js?ver=1608554957:42
at r (lodash.min.js?ver=1599471754:88)
at app.aced3b2.js?ver=1608554957:42
at r (lodash.min.js?ver=1599471754:88)
at app.aced3b2.js?ver=1608554957:42
at r (lodash.min.js?ver=1599471754:88)
at Ia (app.aced3b2.js?ver=1608554957:42)
at app.aced3b2.js?ver=1608554957:42
at app.aced3b2.js?ver=1608554957:42
at Object.useMemo (react-dom.min.js?ver=1608554103:216)
Me @ react-dom.min.js?ver=1608554103:125
app.aced3b2.js?ver=1608554957:42 Uncaught (in promise) TypeError: Cannot read property ‘elements’ of undefined
at app.aced3b2.js?ver=1608554957:42
at r (lodash.min.js?ver=1599471754:88)
at app.aced3b2.js?ver=1608554957:42
at r (lodash.min.js?ver=1599471754:88)
at app.aced3b2.js?ver=1608554957:42
at r (lodash.min.js?ver=1599471754:88)
at Ia (app.aced3b2.js?ver=1608554957:42)
at app.aced3b2.js?ver=1608554957:42
at app.aced3b2.js?ver=1608554957:42
at Object.useMemo (react-dom.min.js?ver=1608554103:216)

I have cleared the cache and still get this error

Thanks
Tim

rubin · December 22, 2020, 1:59pm

Hey There,

We’ve released a new version .8 which is addressing several related issues. Please try updating to that version and report back. Thank you!

batybat · December 22, 2020, 4:27pm

Hi Rubin

I have just updated to the new version and cleared the caches but still get the same error.

Thanks Tim

tristup · December 23, 2020, 1:05pm

Hi Tim,

We are not able to check your site, as the first step credentials does not allow us to visit the URLs. Can you please recheck and send it again to us.

Thank

batybat · December 23, 2020, 5:24pm

Hi Tristup

I have just tested and these login details work

mikeandsandi · December 23, 2020, 5:56pm

I was getting the same issue - after I ran the .8 update it seemed to still be doing the blank grey screen, but it did end up loading. Then when I tried to save an update it kept saying “uh oh, failed to save”. I had another person in my office check the front end of the site and it appears to have saved, but not sure why I’m getting those “failure to save” messages.

alexander · December 23, 2020, 9:36pm

Hi Tim,

I’ve checked your site and tested for a plugin conflict. It looks like if the Query Monitor plugin is disabled things work normally. I did some searching regarding the 502 error code and Query Monitor and came across this:

It could be something that can be corrected by increasing the nginx buffer sizes in your server. I’m not sure exactly why this would start happening after the update. It could be that we run a few more queries now for some of the new features and Query Monitor is building up information behind the scenes and it reaches a tipping point where the server isn’t able to handle the output.

I’ve tried testing Query Monitor on some other sites and I’m not experiencing this.

batybat · December 24, 2020, 9:46am

Hi Alexander

Thanks for finding a solution, although I do use the Query monitory frequently to monitor site performance.

I have an enterprise level dedicated cloud hosting for this site and only currently using 2% of resources when I look at the server stats. The NGINX, STATIC CACHE EXPIRY is set at 43200 would you recommend increasing this?

I also use the Pro theme on server other smaller sites on shared wordpress hosting so I am guessing then that the upgrade would not run now with the update on these type of hosting environments?

kory · December 24, 2020, 6:27pm

Howdy, @batybat! You could check in with your host to see what values they might recommend updating and to what level. They should be able to direct you a little more on all that. As for using Pro on shared hosting, you should still be able to run everything there as well. We have users utilizing Pro across all sorts of ecosystems and as every situation is unique, if you happen to run into any issues feel free to let us know and we can help you look into anything.

batybat · December 24, 2020, 10:43pm

That’s great thanks very much for your help.

kory · December 24, 2020, 10:59pm

No problem!

system · January 3, 2021, 10:59pm

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.

christian · January 4, 2021, 12:07pm

Hey @batybat,

The credentials you’ve provided previously doesn’t work anymore. Please provide the updated credentials so we could check again.

For now, please try reinstalling Pro.

Thanks.

marc_a · January 4, 2021, 4:46pm

Hi @batybat,

The credentials your provided is not an administrator. If the issue still persist on your end, please provide us credentials with an administrator level so that we can check your issue.

Hope that helps.

Thank you.