Block Editor Not Working on this page - Json error
I was helping Marlene with spacing of headers and it seems like the Block Editor stopped working. I saw an JSON error message at the top, but don't see it anymore. Classic editor and Elementor editor work okay
#1 Updated by Boone Gorges 8 months ago
- Status changed from New to Reporter Feedback
I've opened https://sludigitalportfolios.commons.gc.cuny.edu/wp-admin/post.php?post=476&action=edit and it seems to be loading OK for me. In exactly what was the Block Editor not working? Did the content not load at all? Is there perhaps an issue on save? What was the JSON error message? Any additional details would be helpful.
#2 Updated by scott voth 8 months ago
The problem is that you cannot scroll down on the page to edit the content not shown on the initial screen. The JSON error said that the page could not be updated due to a JSON error. I still can't scroll down. I tried in Firefox and Chrome and got the same issue. Can you scroll down in the block editor?
#4 Updated by Boone Gorges 8 months ago
- Status changed from Reporter Feedback to Hold
- Target version set to Future release
Got it, thanks for the additional info.
I saw a JSON formatting issue in the console (not at the top of the page) and I traced it to the coins-metadata plugin. See #14114. That problem is now fixed, but the underlying scroll problem still exists.
I see that this might be a more general problem with Elementor. https://wordpress.org/support/topic/cannot-scroll-down-the-block-templates-section/, https://wordpress.org/support/topic/unable-to-scroll-page-whilst-on-elementor-editing-interface-for-specific-page/, https://github.com/elementor/elementor/issues/4325 I did a few minutes of debugging, trying to identify an obvious culprit, but I'm not seeing anything. The Elementor system is enormously complicated, and this site has many plugins running, so it's not really feasible to do a deeper debug. As long as other tools are available to edit the post content (such as the Classic editor) I'm afraid that this is as far as we can go at the moment. We'll hope for an upstream fix that resolves the problem.