Something went wrong while optimising the SEO data of your site. Please try agai

  • Resolved Group Of Oceninfo

    (@princebhalani143)


    4 years, 7 months ago

    Hello Team,

    I’ve updated to the latest update and when proceeding with update it’s throwing an below error when it was almost done.

    Something went wrong while optimising the SEO data of your site. Please try again later.

    When I’ve enable debug mode getting below errors.

    [28-Apr-2020 13:02:01 UTC] PHP Fatal error:  Uncaught Exception: Term could not be found. in /wp-content/plugins/wordpress-seo/src/builders/indexable-term-builder.php:49

Stack trace:
#0 /wp-content/plugins/wordpress-seo/src/builders/indexable-builder.php(164): Yoast\WP\SEO\Builders\Indexable_Term_Builder->build(3, Object(Yoast\WP\SEO\Models\Indexable))
#1 /wp-content/plugins/wordpress-seo/src/actions/indexation/indexable-term-indexation-action.php(83): Yoast\WP\SEO\Builders\Indexable_Builder->build_for_id_and_type(3, 'term')
#2 /wp-content/plugins/wordpress-seo/src/routes/indexable-indexation-route.php(210): Yoast\WP\SEO\Actions\Indexation\Indexable_Term_Indexation_Action->index()
#3 /wp-content/plugins/wordpress-seo/src/routes/indexable-indexation-route.php(171): Yoast\WP\SEO\Routes\Indexable in /wp-content/plugins/wordpress-seo/src/builders/indexable-term-builder.php on line 49

[28-Apr-2020 13:02:13 UTC] PHP Deprecated:  wpseo_opengraph is <strong>deprecated</strong> since version 14.0! Use wpseo_frontend_presenters instead. in /wp-includes/functions.php on line 5088

[28-Apr-2020 13:02:13 UTC] PHP Deprecated:  WPSEO_Frontend::canonical is <strong>deprecated</strong> since version WPSEO 14.0 with no alternative available. in /wp-includes/functions.php on line 4723
Viewing 15 replies - 1 through 15 (of 35 total)

  • Exactly the same here.

    Same here ??

    I’m seeing this in my logs:

    Uncaught exception 'PDOException' with message 'SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry '2236-2235' for key 'PRIMARY'' in /httpdocs/wp-content/plugins/wordpress-seo-premium/vendor_prefixed/j4mie/idiorm/idiorm.php:464

    Different than the above error, so just reporting it.

    • This reply was modified 4 years, 7 months ago by tunjic.

    The problem is Polyland. Line: 38 of polylang/modules/plugins/wpseo.php use wpseo_opengraph

    Same issue here: “Something went wrong while optimizing the SEO data of your site. Please try again later.”

    Same

    same

    same

    14.0.1 has been released with a few hotfixes. @princebhalani143 can you check if this release solves your error? The deprecated warnings are most likely the cause of custom code or another plugin, you will need to check for that yourself.

    I’m guessing Polylang will receive an update soon, I see they have acknowledged the issue and are working on a fix https://github.com/Yoast/wordpress-seo/issues/14698

    In my case, when clicking on the speed up button, after the job has been done, it remains always “Object 0 of 1 processed.” When clicking again the speed up button, the “Object 0 of 1 processed” remains again.
    It appears the “Good job! You’ve sped up your site” message, but the “NEW: Yoast SEO can now store your site’s SEO data in a smarter way! Click here to speed up your site now
    Or hide this notice (everything will continue to function as normal)” message reappears again and again.

    It does not work for me either with the hotfixes.

    In the JS console I have the following 2 errors:

    
wp-seo-indexation-1401.js?ver=14.0.1:1 GET https://xxxx/wp-json/yoast/v1/indexation/posts 404

wp-seo-indexation-1401.js?ver=14.0.1:1 TypeError: Cannot read property 'length' of undefined
    at wp-seo-indexation-1401.js?ver=14.0.1:1
    at tryCatch (wp-polyfill.min.js:1)
    at Generator.invoke [as _invoke] (wp-polyfill.min.js:1)
    at Generator.t.<computed> [as next] (wp-polyfill.min.js:1)
    at r (wp-seo-indexation-1401.js?ver=14.0.1:1)
    at wp-seo-indexation-1401.js?ver=14.0.1:1

    When I manually do a GET on https://xxxx/wp-json/yoast/v1/indexation/posts I have 404 with the JSON content:

    
{"code":"rest_no_route","message":"No route was found matching the URL and request method","data":{"status":404}}
    • This reply was modified 4 years, 7 months ago by Fabian.

    Same here with Version 14.0.1

    Thread Starter Group Of Oceninfo

    (@princebhalani143)

    @djennez: Updating 14.0.1 solved the issue.

    14.0.2 solved the issue for me.

Viewing 15 replies - 1 through 15 (of 35 total)
  • The topic ‘Something went wrong while optimising the SEO data of your site. Please try agai’ is closed to new replies.