Wrong page content displayed in Gutenberg editor

  • Resolved deklankvanroos

    (@deklankvanroos)


    2 weeks, 4 days ago

    Hello,

    I’m experiencing an issue with the WordPress Block Editor on my website.

    Some pages are displaying the wrong content when I open them in the editor. For example, my Music page displays the content of my homepage, even though the Music page itself contains the correct content when viewed in the Pages overview.

    The content is therefore not lost, but it appears to be displayed incorrectly in the editor.

    My setup:

    • WordPress 7.0.4
    • Otter 3.2.2
    • Neve Free 4.1.3
    • PHP 8.2.33

    I also use Otter blocks such as Button Group and Icon List on my pages.

    We have already tested this in WordPress Troubleshooting Mode. With The Events Calendar disabled and Twenty Twenty-Four as the active theme, the editor still displays the wrong/mixed page content. So the issue does not appear to be caused by the Neve theme.

    There is also a separate issue involving The Events Calendar: when that plugin is active, the Gutenberg editor becomes completely blank. The Events Calendar support team is investigating that separately.

    Could you please let me know whether this incorrect/mixed page content could be related to Otter blocks, saved block data, or an Otter/Gutenberg compatibility issue?

    I would appreciate any suggestions for how to diagnose this further.

    Thank you!

    The page I need help with: [log in to see the link]

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Support Poonam Namdev

    (@poonam9)

    2 weeks, 4 days ago

    Hi @deklankvanroos,

    I noticed that you are using a cache plugin on your site. Have you already tested the editor after temporarily deactivating the cache plugin and clearing all existing cache?

    If not, could you please try this and check whether the affected pages display the correct content in the Block Editor afterward?

    I recommend performing this test on the live site rather than only through WordPress Troubleshooting Mode, as caching plugins can sometimes continue to affect cached content or requests even while Troubleshooting Mode is enabled.

    This will help us rule out caching as a possible cause of the incorrect/mixed page content.

    Please let us know what you find.

    Thread Starter deklankvanroos

    (@deklankvanroos)

    2 weeks, 3 days ago

    Hi,

    I completed the cache test as requested.

    I temporarily deactivated Speed Optimizer and flushed the SiteGround cache completely.

    The result is very clear:

    • With Troubleshooting Mode disabled, the Music page displays its correct content in the Block Editor.
    • With Troubleshooting Mode enabled, the Music page displays the wrong content again (the homepage content).
    • This happens even with Speed Optimizer disabled and the SiteGround cache completely cleared.

    So caching does not appear to be the cause. The incorrect/mixed page content only occurs when WordPress Troubleshooting Mode is enabled.

    Thank you for your help.

    Plugin Support rodicaelena

    (@rodicaelena)

    2 weeks, 2 days ago

    Hi,

    Thank you for testing caching.

    However, we would need a bit more information, as your last message is a bit confusing.

    When you are referring to WordPress Troubleshooting Mode, are you referring to the troubleshoot mode offered by the HealthCheck plugin? https://docs.themeisle.com/wordpress/theme-doesnt-work-as-expected-troubleshooting-guide

    If so, you mentioned that everything appears correct, when the troubleshooting mode is disabled, which is the default mode, as that shouldn’t be enabled, so it’s not very clear when the issue occures.

    Can you please let us know if you followed the steps suggested here https://docs.themeisle.com/wordpress/theme-doesnt-work-as-expected-troubleshooting-guide to temporarily disable all plugins except Otter Blocks, and if in that case, everything is working well or not?

    Thank you!

Viewing 3 replies - 1 through 3 (of 3 total)

You must be logged in to reply to this topic.