Javascript errors in admin backend, v2.0.1

  • Resolved Joe

    (@joewa1980)


    5 years ago

    Similar to what @robertstaddon was experiencing in https://wordpress.org/support/topic/version-2-0-causes-javascript-errors-in-divi-builder/

    …lots of JS errors appearing in some of our backend admin editing pages even with v2.0.1.

    Some examples:

    frontend.js:1 Uncaught TypeError: Cannot read property 'has' of undefined
    at Object.handle (frontend.js:1)
    at gettext_with_context (frontend.js:1)
    at Object.applyFilters (hooks.min.js:1)
    at Object.u [as _x] (i18n.min.js:2)
    at tags-suggest.min.js:2
    at tags-suggest.min.js:2
    Uncaught TypeError: Cannot read property 'has' of undefined
    at Object.handle (frontend.js:1)
    at gettext_with_context (frontend.js:1)
    at Object.applyFilters (hooks.min.js:1)
    at Object.u [as _x] (i18n.min.js:2)
    at tags-box.min.js:2
    at tags-box.min.js:2
    frontend.js:1 Uncaught TypeError: Cannot read property 'has' of undefined
    at Object.handle (frontend.js:1)
    at gettext (frontend.js:1)
    at Object.applyFilters (hooks.min.js:1)
    at Object.__ (i18n.min.js:2)
    at a11y.min.js:2
    at HTMLDocument.u (a11y.min.js:2)
Viewing 7 replies - 1 through 7 (of 7 total)
  • Plugin Author Lee Willis

    (@leewillis77)

    5 years ago

    If you’re getting that error, then you’re not running v2.0.1 – it doesn’t call has() at all so wouldn’t generate those issues

    Thread Starter Joe

    (@joewa1980)

    5 years ago

    We are running 2.0.1, it was auto-updated ~8hrs ago.

    Screenshot from plugins page:
    https://ibb.co/KqN8Zjm

    • This reply was modified 5 years ago by Joe.
    Plugin Author Lee Willis

    (@leewillis77)

    5 years ago

    Either:
    a) The upgrade didn’t complete correctly and you still have stale files from v2.0.0
    b) You have something on your site that is serving out of date assets

    The problematic call is a call to lodash.has (https://plugins.trac.wordpress.org/browser/say-what/tags/2.0.0/assets/build/frontend.js#L158).

    That doesn’t exist in v2.0.1 – we don’t use lodash at all in fact in the updated version (https://plugins.trac.wordpress.org/browser/say-what/tags/2.0.1/assets/build/frontend.js)

    Thread Starter Joe

    (@joewa1980)

    5 years ago

    Same errors on two separate sites, and then when Say What? is deactivated the errors disappear.

    I’ll try manually adding the files from https://plugins.trac.wordpress.org/browser/say-what/tags/2.0.1 tomorrow.

    Plugin Author Lee Willis

    (@leewillis77)

    5 years ago

    No problem.

    If you’re still seeing this after then if you can reach out at https://plugins.leewillis.co.uk/enquiries/ with details of the site URL and we’ll happily take a look – although I’m confident those calls aren’t in the released version

    Thread Starter Joe

    (@joewa1980)

    5 years ago

    This looks to be a potential conflict with jQuery Migrate. Both sites are running 2.0.1 with files directly from the repository.

    For now we’ve allowed Say What? to run everywhere except for anywhere that matches /wp-admin/post.php?post=*

    It means we can run the admin pages as usual while having the plugin work on the frontend.

    It’s a workaround that we may have to live with, no huge issue.

    Plugin Author Lee Willis

    (@leewillis77)

    5 years ago

    I’d love to look at this if you can reach out at the URL above – you really shouldn’t be seeing that issue from v2.0.1 …

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

The topic ‘Javascript errors in admin backend, v2.0.1’ is closed to new replies.