Forum Replies Created

Viewing 4 replies - 1 through 4 (of 4 total)
  • johnReeve

    (@johnreeve)

    Yeah, we had a similar problem yesterday when we were fighting fires caused by the upgrade. Our error logged ended up at something like 12GB before I uninstalled and rolled back Yoast… that was after about 2 hours of running the plugin.

    johnReeve

    (@johnreeve)

    I had the same issue. I have a large site, installed the update, and it 504’d everything for quite a while. There were some other complications, but I had to end up manually removing the plugin.

    New Relic reported a slow query by the plugin:

    UPDATE wp_options SET option_value = ?, autoload = ? WHERE option_name = ?

    Here’s the callstack:

    …d at /srv/bindings/a0c8104cb1604e4b8d9fbfd253938461/code/wp-includes/
    wp-db.php (1924)
    …d at /srv/bindings/a0c8104cb1604e4b8d9fbfd253938461/code/wp-includes/
    wp-db.php (1813)
    …d at /srv/bindings/a0c8104cb1604e4b8d9fbfd253938461/code/wp-includes/
    wp-db.php (2166)
    … at /srv/bindings/a0c8104cb1604e4b8d9fbfd253938461/code/wp-includes/
    option.php (369)
    …d253938461/code/wp-content/plugins/wordpress-seo/inc/
    class-upgrade-history.php (112)
    …d253938461/code/wp-content/plugins/wordpress-seo/inc/
    class-upgrade-history.php (71)
    …4b8d9fbfd253938461/code/wp-content/plugins/wordpress-seo/inc/
    class-upgrade.php (156)
    …4b8d9fbfd253938461/code/wp-content/plugins/wordpress-seo/inc/
    class-upgrade.php (22)
    …b1604e4b8d9fbfd253938461/code/wp-content/plugins/wordpress-seo/
    wp-seo-main.php (306)
    …v/bindings/a0c8104cb1604e4b8d9fbfd253938461/code/wp-includes/
    class-wp-hook.php (286)
    …v/bindings/a0c8104cb1604e4b8d9fbfd253938461/code/wp-includes/
    class-wp-hook.php (310)
    … at /srv/bindings/a0c8104cb1604e4b8d9fbfd253938461/code/wp-includes/
    plugin.php (453)
    … called at /srv/bindings/a0c8104cb1604e4b8d9fbfd253938461/code/
    wp-settings.php (327)
    …ce called at /srv/bindings/a0c8104cb1604e4b8d9fbfd253938461/code/
    wp-config.php (203)
    …once called at /srv/bindings/a0c8104cb1604e4b8d9fbfd253938461/code/
    wp-load.php (37)
    …lled at /srv/bindings/a0c8104cb1604e4b8d9fbfd253938461/code/
    wp-blog-header.php (13)
    …equire called at /srv/bindings/a0c8104cb1604e4b8d9fbfd253938461/code/
    index.php (17)
    • This reply was modified 7 years ago by johnReeve.

    Sorry that wasn’t a solution. That’s very similar to what I was seeing yesterday, but likely a different issue. I think that there are some funky local cache issues with this.

    Right now I’m trying to troubleshoot how to modify the JS vars to customize them… I can’t tell if I am dumb or if the plugin is poorly documented, but I guess I’ll just re-read the code again LOL

    best of luck on finding a solution.

    I dunno if this is super helpful, but I had to do a hard refresh of the admin options page to get the keys to show up.

    I think they were there and the disqus backend thout they were there, but they just weren’t showing up due to some caching issue.

    YMMV, maybe wholly unrelated, etc.

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