• I am running into a situation where editing / creating a new post or page goes into a blank screen with lots of javascript errors in the console. The errors are random but mostly React errors. The error doesn’t happen right away after deployment, takes a couple of hours or a day for the page to break (there is no change to the page during that duration). The only way to fix the issue is to rollback to a previous deployment and redeploy the current deployment.

    There is no log of error on the server side (no memory issue, etc). I am using WordPress 5.7.0 docker image to spin up the website. I also don’t have any caching plugin or caching on any level.

    Some of the examples of error are

    
    Cannot read properties of undefined (reading 'mark')
    
    Cannot read properties of undefined (reading 'languageProcessing')
    
    Cannot read properties of undefined (reading 'helpers')
    
    undefined is not an object (evaluating 'window.yoast.editorModules.analysis')
    
    undefined is not an object (evaluating 'i.SETTINGS_DEFAULTS')
    
    

    What I have tried so far?

    * I have tried all options mentioned on other forums of using Health Check Plugin, disabling plugins and themes – that didn’t help.
    * I tried installing Classic Editor, activating it and that did help load the page but its not Gutenberg Editor plus remember the page doesn’t fail for some time after deployment. Is there some sort of memory leak that the Gutenberg editor is causing? In that case there should be some error log on server side, which we don’t see.

Viewing 3 replies - 1 through 3 (of 3 total)
  • Moderator bcworkz

    (@bcworkz)

    It would help in debugging if you found a way to cause the error immediately. Try upgrading to the latest WP version (or at least reinstalling the current version. One or more of the WP files may have become corrupted.). Restart troubleshooting mode to eliminate plugin or theme influence.

    Thread Starter emarketerpsharma

    (@emarketerpsharma)

    @bcworkz – We use docker images to spin up container for WP, so with every deployments we are getting fresh new copy of the core WP files

    Moderator bcworkz

    (@bcworkz)

    evaluating ‘window.yoast.editorModules.analysis’ sounds like not all plugins have been deactivated. We basically need to get to something working in order to find what isn’t. A fresh WP installation with no plugins and a Twenty* default theme should be error free. From there, incrementally add your site specific stuff until errors occur. The last added item would be the cause.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Broken Post / Page Pages’ is closed to new replies.