• Resolved roaming1

    (@roaming1)


    After updating to SEOPress Version 8.8.1 by The SEO Guys at SEOPress – my Gutenberg post pages are becoming non-responsive-specifically when using the scrollbar and editing headings in a post, but it may also occur at other times when editing a post. Loading a post is also drastically slowed. I have followed traditional troubleshooting procedure and disabled all plugins/swapped to default theme. Only when SEO press is active does the behavior occur. I am not getting any errors in the WP debug file or browser console. More details if needed:

    PHP version 8.2.28 / WordPress Version 6.8.1 / Parent theme Astra Version 4.11.2

    I have disabled all of the SEO Press modules to see if the error was from a certain feature but the behavior still continues when all modules are “off”. Please advise.

    • This topic was modified 1 year ago by roaming1.

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

Viewing 12 replies - 16 through 27 (of 27 total)
  • Thread Starter roaming1

    (@roaming1)

    Closing this thread.

    Plugin Author Benjamin Denis

    (@rainbowgeek)

    Just to confirm: without the legacy FAQ block, is there any issue? Is it better with the new FAQ block?

    Thanks

    Thread Starter roaming1

    (@roaming1)

    Unfortunately, there is no difference if I use the legacy block, the new FAQ block or no block at all.

    Plugin Author Benjamin Denis

    (@rainbowgeek)

    OK, latest test: go to SEOPress dashboard, Advanced settings page, Appearance tab.

    Check “Enable the universal SEO metabox for the Block Editor (Gutenberg)”.

    Uncheck “Disable the universal SEO metabox”.

    Save changes and go back to the editor to see if it’s better.

    Thank you for your help!

    Thread Starter roaming1

    (@roaming1)

    I had tested turning off all of the modules before with no difference. I have just tested again following your suggestion-purged cache and retested. No difference. Retested with all modules “off” again -no difference. Deactivated the plugin and everything is fine.

    Plugin Author Benjamin Denis

    (@rainbowgeek)

    Just to be sure, if you enable the universal SEO metabox, it changes nothing?

    https://www.seopress.org/support/guides/disable-the-universal-seo-metabox-beacon-in-frontend/

    Thread Starter roaming1

    (@roaming1)

    Enabling or Disabling the SEO metabox does not change anything BUT when I go into the advanced settings and and check only “Universal Metabox for the Block Editor” the problem is fixed! Seems like having the content analysis metabox load at the bottom of the page was causing the problem.

    This is strange because when I disable the SEO metabox in the settings-the content analysis metabox still appears at the bottom of the post page. I am not sure, but shouldn’t disabling this module STOP this from happening?

    • This reply was modified 12 months ago by roaming1.
    • This reply was modified 12 months ago by roaming1.
    • This reply was modified 12 months ago by roaming1.
    Plugin Author Benjamin Denis

    (@rainbowgeek)

    When the editor loads with the standard SEO and Content Analysis metaboxes, we automatically request your page’s source code in order to perform our analysis.

    It’s likely that a server configuration issue is preventing this request—this could be due to a firewall, security plugin, .htaccess rule, or similar restriction.

    Please ensure that your server’s own IP address is whitelisted, as the request originates from your server itself.

    We’ve tested this functionality both locally and on a live site, and were unable to reproduce the issue.

    Thread Starter roaming1

    (@roaming1)

    The problem is solved. When I check “Enable the universal SEO metabox for the Block Editor” in the advanced options in the universal SEO metabox settings – the page loads as normal and I can access/edit post content and SEO title and meta without any issues.

    Plugin Author Benjamin Denis

    (@rainbowgeek)

    Perfect!

    We’ll work on a fix for the classic metaboxes.

    Plugin Author Benjamin Denis

    (@rainbowgeek)

    The issue has been identified (was tricky).

    The patch is ready.

    The next update will include it.

    ETA: this week.

    Thread Starter roaming1

    (@roaming1)

    Great to hear. Thanks for sticking with it Benjamin!

Viewing 12 replies - 16 through 27 (of 27 total)

The topic ‘Gutenberg Post Editor Non-Responsive’ is closed to new replies.