Editing a post produces a blank screen.

  • I’ve set up a local 5.8.2 site [on SeaMonkey 2.53.7] and am having difficulties editing a post. I deleted the setup and used an older version (5.7.?) and when I go about in editing a post, the editor works.

    So I go back to 5.8.2 (via automatic upgrade) and when I go into Edit post, I get a blank page again.

    I took a gander at the errors in the browser console and notice a whole bunch of errors, particularly “SyntaxError: invalid identity escape in regular expression” in editor.min.js:7:23325. I had thought it was wp-admin/js/editor.min.js; but it was actually wp-includes/js/dist/editor.min.js.

    It was complaining about the following part:

    deburr)(e).replace(/[\s\./]+/g,”-“).replace(/[^\p{L}\p{N}_-]+/gu,””).

    Not being familiar with the above replacement, I changed the /gu to /g, and restarted the website.

    When I reloaded the edit-post, the Editor appeared; but the contents within the editor contained markups.

    There were a lot of other errors after the initial invalid identity escape error:

    1) “An error occurred while running ‘mapSelect’: n(…) is null”
    2) TypeError: Object(…)(…) is undefined
    StackTrace:

    TypeError: Object(...)(...) is undefined
Stack trace:
Xs@https://192.168.17.22/wp-includes/js/dist/edit-post.min.js?ver=3656613c515e40e95a15114467097b39:49:131322
we@https://192.168.17.22/wp-includes/js/dist/vendor/react-dom.min.js?ver=16.13.1:84:293
zj@https://192.168.17.22/wp-includes/js/dist/vendor/react-dom.min.js?ver=16.13.1:226:496
Th@https://192.168.17.22/wp-includes/js/dist/vendor/react-dom.min.js?ver=16.13.1:152:223
tj@https://192.168.17.22/wp-includes/js/dist/vendor/react-dom.min.js?ver=16.13.1:152:152
Te@https://192.168.17.22/wp-includes/js/dist/vendor/react-dom.min.js?ver=16.13.1:146:151
Ja@https://192.168.17.22/wp-includes/js/dist/vendor/react-dom.min.js?ver=16.13.1:224:381
md@https://192.168.17.22/wp-includes/js/dist/vendor/react-dom.min.js?ver=16.13.1:173:43
nd/<@https://192.168.17.22/wp-includes/js/dist/vendor/react-dom.min.js?ver=16.13.1:175:222
Rh@https://192.168.17.22/wp-includes/js/dist/vendor/react-dom.min.js?ver=16.13.1:147:64
nd@https://192.168.17.22/wp-includes/js/dist/vendor/react-dom.min.js?ver=16.13.1:175:208
I.render@https://192.168.17.22/wp-includes/js/dist/vendor/react-dom.min.js?ver=16.13.1:238:412
el@https://192.168.17.22/wp-includes/js/dist/edit-post.min.js?ver=3656613c515e40e95a15114467097b39:49:135127
window._wpLoadBlockEditor</<@https://192.168.17.22/wp-admin/post.php?post=1&action=edit:1849:13

    3) TypeError: Object(…)(…) is undefined edit-post.min.js:49:131322

    TypeError: Object(...)(...) is undefined
Stack trace:
Xs@https://192.168.17.22/wp-includes/js/dist/edit-post.min.js?ver=3656613c515e40e95a15114467097b39:49:131322
we@https://192.168.17.22/wp-includes/js/dist/vendor/react-dom.min.js?ver=16.13.1:84:293
zj@https://192.168.17.22/wp-includes/js/dist/vendor/react-dom.min.js?ver=16.13.1:226:496
Th@https://192.168.17.22/wp-includes/js/dist/vendor/react-dom.min.js?ver=16.13.1:152:223
tj@https://192.168.17.22/wp-includes/js/dist/vendor/react-dom.min.js?ver=16.13.1:152:152
Te@https://192.168.17.22/wp-includes/js/dist/vendor/react-dom.min.js?ver=16.13.1:146:151
Ja@https://192.168.17.22/wp-includes/js/dist/vendor/react-dom.min.js?ver=16.13.1:224:381
md@https://192.168.17.22/wp-includes/js/dist/vendor/react-dom.min.js?ver=16.13.1:173:43
nd/<@https://192.168.17.22/wp-includes/js/dist/vendor/react-dom.min.js?ver=16.13.1:175:222
Rh@https://192.168.17.22/wp-includes/js/dist/vendor/react-dom.min.js?ver=16.13.1:147:64
nd@https://192.168.17.22/wp-includes/js/dist/vendor/react-dom.min.js?ver=16.13.1:175:208
I.render@https://192.168.17.22/wp-includes/js/dist/vendor/react-dom.min.js?ver=16.13.1:238:412
el@https://192.168.17.22/wp-includes/js/dist/edit-post.min.js?ver=3656613c515e40e95a15114467097b39:49:135127
window._wpLoadBlockEditor</<@https://192.168.17.22/wp-admin/post.php?post=1&action=edit:1849:13

    Obviously, this isn’t a solution to this issue. Since I am using SeaMonkey 2.53.7 (ESR 57), it could be that 5.8.x doesn’t support SeaMonkey. I tried loading the same screen (w/o any changes to the code i.e. restored the /gu) in Firefox(93.0), and the editor loads; but with the markup. i.e.

    <!– wp:paragraph –>
    <p>This is a test.</p>
    <!– /wp:paragraph –>

    So I edit the post and remove the markup. Update it. And view the post. Then I edit again and the markups are gone.

    But when I use SeaMonkey again, I see a blank page. The cache is empty. I have no add-ons to SeaMonkey. The ‘view source’ does show me the source code for the page, so while it is loading, I guess some javascript code is not working.

    I’ve seen a bunch of posts on here with similar effects and there was a github issue page which detailed a similar problem. Clearing the cache (at least for me) didn’t work. (Cache is currently at 0bytes).

    I’m posting this here as a FYI. Not sure if it is fixable since if it works in Firefox and not in SeaMonkey, it means SeaMonkey is missing some support for some javascript functions.

    The only option I see is to go back to 5.7.x and ignore the ‘upgrade’ suggestions.

    Addendum: I changed the editor.min.js from (/gu to /g), restarted the webserver and went to edit the post, and it worked. No markups (I suspect it was something else).
    Thanks

    • This topic was modified 3 years, 4 months ago by ewx9041.
    • This topic was modified 3 years, 4 months ago by ewx9041.
Viewing 1 replies (of 1 total)
  • Moderator bcworkz

    (@bcworkz)

    Forgoing updates isn’t a good option, you could miss out on important security patches. These are normally back-ported to earlier versions if automatic minor updates are enabled, but they only go back so far. Eventually you’ll drop off the back end of getting security patches. If automatic minor updates are disabled, then you will get no security patches at all.

    Let’s be sure it’s really a browser issue and not some theme or plugin. Revert WP to its “plain vanilla” state by switching to twenty twenty-one theme and deactivating all plugins. After flushing the browser cache and clearing cookies, we’d expect the editor to work in any modern browser.

    FYI, SeaMonkey 2.53.9.1 is available. Not that much later than your version, but it does contain some bug fixes. I recommend updating before making any determination of fitness for purpose.

    If you find there are still editor issues with plain vanilla WP on the latest SeaMonkey, I suggest raising an issue at the Gutenberg Project’s GitHub site: https://github.com/wordpress/gutenberg

Viewing 1 replies (of 1 total)
  • The topic ‘Editing a post produces a blank screen.’ is closed to new replies.