Uncaught TypeError: Cannot read property | post-edit-1611.js

  • Resolved Feras

    (@orostudios)


    5 years, 1 month ago

    Hello, I have this 2 warnings:

    blocks.min.js?ver=:3 The block “yoast-seo/breadcrumbs” is registered with an invalid category “yoast-internal-linking-blocks”.

    blocks.min.js?ver=:3 The block “yoast-seo/breadcrumbs” is registered with an invalid category “yoast-internal-linking-blocks”.

    And this 2 errors:

    Uncaught TypeError: Cannot read property ‘registerPlugin’ of undefined at o.registerPlugin (post-edit-1611.js:1) at new o (post-edit-1611.js:1) at t.default (post-edit-1611.js:1) at HTMLDocument.<anonymous> (post-edit-1611.js:1)

    Uncaught TypeError: Cannot read property ‘registerPlugin’ of undefined at o.registerPlugin (post-edit-1611.js:1) at new o (post-edit-1611.js:1) at t.default (post-edit-1611.js:1) at HTMLDocument.<anonymous> (post-edit-1611.js:1)

    all of this errors appeared after the last update, what to do to fix this?
    FYI I’m using flatsome theme also updated to the latest version.

    Thanks a lot.

Viewing 6 replies - 1 through 6 (of 6 total)
  • devnihil

    (@devnihil)

    5 years, 1 month ago

    @orostudios We’re sorry to hear you are experiencing this issue on your site.

    To resolve this, can you please try the following?:

      1. Install & activate the Yoast Test Helper plugin
      2. Go to Tools -> Yoast Test
      3. Hit the “Reset Indexables & Migrations” button
      4. Under SEO → Tools, click the “Start SEO Data Optimization” button.

    `

    Thread Starter Feras

    (@orostudios)

    5 years, 1 month ago

    Unfortunately it didn’t work, I still have the same problem nothing changed.

    Plugin Support Michael Tiña

    (@mikes41720)

    5 years, 1 month ago

    Hi,

    Can you confirm that you updated to the latest version of Yoast SEO for WordPress v16.1.1 and that the rest of your plugins and themes are also updated, and you are meeting the necessary plugin requirements?

    Just to be sure, we would like to rule out any plugin or theme conflicts that may occur. The fastest way to do this is to deactivate all non-Yoast plugins and switch to a standard theme like Twenty Nineteen. 

    Test this on your development or staging site, if you have one. If not, we recommend using the Health Check & Troubleshooting plugin. This plugin allows you to run a conflict check without affecting normal visitors to your site.

    As we can imagine that you’re unfamiliar with checking for conflicts, we’d like to point you to a step-by-step guide that will walk you through the process: How to check for plugin conflicts.

    Thread Starter Feras

    (@orostudios)

    5 years, 1 month ago

    Hi,
    Thank you very much for your fast reply.

    Yes everything on my site is updated to the last version and and i’m using the latest version of yoast seo.

    I already tried to deactivate all plugins and i just kept yoast seo plugin and the theme active and the warnings and errors still appears.

    FYI all of this warnings and errors appeared only with flatsome theme editor (UX Builder) so there is no point from tring another theme because i think the problem isn’t going to happen.

    Plugin Support Michael Tiña

    (@mikes41720)

    5 years, 1 month ago

    Hi,

    With the health check & troubleshooting plugin, you can use the troubleshooting mode to enable just the Yoast SEO v16.1.1 plugin and your chosen Flatsome theme — https://yoast.com/help/how-to-check-for-plugin-conflicts/#live-site (this won’t affect your front-end users)

    If you are still able to reproduce the issue of those generated errors with just Yoast SEO & Flatsome, and everything else is set to default, we believe it may be a bug, which we would then recommend that you submit a new bug report here — https://yoast.com/help/how-to-write-a-good-bug-report/

    devnihil

    (@devnihil)

    5 years, 1 month ago

    We are going ahead and marking this issue as resolved due to inactivity. If you require any further assistance please create a new issue.

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

The topic ‘Uncaught TypeError: Cannot read property | post-edit-1611.js’ is closed to new replies.