Support » Plugin: Yoast SEO » Uncaught TypeError: undefined is not a function!

  • Resolved pedrorafael

    (@pedrorafael)


    Hi,

    this error has been presented in different pages…

    WordPress is up to date and Yoast as well.

    Uncaught TypeError: undefined is not a function!
    at b.exports (wp-seo-babel-polyfill-730.min.js?ver=7.3:1)
    at b.exports (wp-seo-babel-polyfill-730.min.js?ver=7.3:1)
    at wp-seo-babel-polyfill-730.min.js?ver=7.3:1
    at Array.map (wp-seo-babel-polyfill-730.min.js?ver=7.3:2)
    at Array.toArray (prototype.js?ver=1.7.1:1021)
    at b.exports (wp-seo-babel-polyfill-730.min.js?ver=7.3:1)
    at Object.139../_add-to-unscopables (wp-seo-babel-polyfill-730.min.js?ver=7.3:2)
    at e (wp-seo-babel-polyfill-730.min.js?ver=7.3:1)
    at wp-seo-babel-polyfill-730.min.js?ver=7.3:1
    at Object.325../modules/_core (wp-seo-babel-polyfill-730.min.js?ver=7.3:4)
    b.exports @ wp-seo-babel-polyfill-730.min.js?ver=7.3:1
    b.exports @ wp-seo-babel-polyfill-730.min.js?ver=7.3:1
    (anonymous) @ wp-seo-babel-polyfill-730.min.js?ver=7.3:1
    map @ wp-seo-babel-polyfill-730.min.js?ver=7.3:2
    toArray @ prototype.js?ver=1.7.1:1021
    b.exports @ wp-seo-babel-polyfill-730.min.js?ver=7.3:1
    139../_add-to-unscopables @ wp-seo-babel-polyfill-730.min.js?ver=7.3:2
    e @ wp-seo-babel-polyfill-730.min.js?ver=7.3:1
    (anonymous) @ wp-seo-babel-polyfill-730.min.js?ver=7.3:1
    325../modules/_core @ wp-seo-babel-polyfill-730.min.js?ver=7.3:4
    e @ wp-seo-babel-polyfill-730.min.js?ver=7.3:1
    (anonymous) @ wp-seo-babel-polyfill-730.min.js?ver=7.3:1
    (anonymous) @ wp-seo-babel-polyfill-730.min.js?ver=7.3:1
    2.core-js/fn/regexp/escape @ wp-seo-babel-polyfill-730.min.js?ver=7.3:1
    e @ wp-seo-babel-polyfill-730.min.js?ver=7.3:1
    (anonymous) @ wp-seo-babel-polyfill-730.min.js?ver=7.3:1
    1.babel-polyfill @ wp-seo-babel-polyfill-730.min.js?ver=7.3:1
    e @ wp-seo-babel-polyfill-730.min.js?ver=7.3:1
    a @ wp-seo-babel-polyfill-730.min.js?ver=7.3:1
    (anonymous) @ wp-seo-babel-polyfill-730.min.js?ver=7.3:1

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Support Md Mazedul Islam Khan

    (@mazedulislamkhan)

    That looks like a plugin or theme conflict. Can you try and gather as much information for us as possible? Please perform the following:
    1. Make sure the issue doesn’t persist when Yoast SEO is disabled.
    2. Check for conflicts.
    3. Check for JavaScript errors with your console.
    If you find any JavaScript errors related to Yoast SEO or if there is a conflict with a plugin or a theme, you can create a new GitHub issue for our developers. Please report the issue to a third party developer as well.
    If you didn’t find any conflicts or errors, we think the issue is specific to your site. We’d need to investigate further but are unable to do so on these forums. You can purchase Yoast SEO Premium and receive our Premium email support and we can help you further.

    Hello,

    this can be treated as a case study for you to improve the plugin, at the moment I just restored the backup, maybe in December I will come back to update your plugin.

    I’ve been getting blank screens in the Gutenberg editor on one of my sites any time that Yoast SEO was activated.

    I found the same errors that @pedrorafael listed (above) in my JavaScript console on the “edit” screen (the Gutenberg editor, not the “classic” / visual editor).

    Because the errors seemed to be coming from Yoast, I have long assumed that Yoast was the source of the problem. The errors went away with Yoast deactivated, as did the blank screen in Gutenberg (in other words, Gutenberg loaded and worked normally with Yoast deactivated).

    After following the advice given by @mazedulislamkhan above, I was able to narrow this down to a plugin conflict between Yoast, Gutenberg, and the Adsense Manager plugin.

    Now, with Adsense Manager deactivated, Gutenberg & Yoast both work as expected.

    For anyone dealing with Gutenberg problems and Yoast, consider checking to see if you are using the Adsense Manager plugin as that may be the combination that produces these errors.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Uncaught TypeError: undefined is not a function!’ is closed to new replies.