Broken for good

  • Resolved hudin

    (@hudin)


    4 years, 2 months ago

    Greetings, I realize that this is work being done for free, but I’m curious to know if with the WordPress 5.6 update that it’s going to be permanently broken and I should suck it up and just use Gutenberg’s horrid interface or is there work that’s being done to fix the issues with adding tags, changing the date, etc.?

    Ever since the update, it’s clear to see that there’s some kind of JQuery JS issue and the Console tosses up:

    jquery.min.js?ver=3.5.1:2 Uncaught TypeError: this._addClass is not a function
    at $.<computed>.<computed>._create (autocomplete.min.js?ver=1.12.1:9)
    at $.<computed>.<computed>._create (jquery-ui.js?ver=1.0:415)
    at $.<computed>.<computed>._createWidget (jquery-ui.js?ver=1.0:585)
    at new $.<computed>.<computed> (jquery-ui.js?ver=1.0:376)
    at HTMLInputElement.<anonymous> (jquery-ui.js?ver=1.0:531)
    at Function.each (jquery.min.js?ver=3.5.1:2)
    at s.fn.init.each (jquery.min.js?ver=3.5.1:2)
    at s.fn.init.$.fn.<computed> [as autocomplete] (jquery-ui.js?ver=1.0:523)
    at s.fn.init.u.fn.wpTagsSuggest (tags-suggest.min.js?ver=5.6:2)
    at HTMLInputElement.<anonymous> (tags-box.min.js?ver=5.6:2)

    I have caching turned off when debugging as well as for WordPress Admin. I’ve cleared the cache multiple times but this issue persists and it’s the same for when I tried to use the Disable Gutenberg plugin, which I’d never installed before.

    Thank you for maintaining this to date and I hope this isn’t the end of it…

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Andrew Ozz

    (@azaozz)

    Hi @hudin, thanks for the good description and the error logs.

    Can you figure out where the jquery-ui.js script comes from? I’d guess it is the old jQuery UI script, perhaps version 1.11.4, all in one file.

    The error seems to be that autocomplete.min.js that is part of UI 1.12.1 and is in core is loaded after the old autocomplete script that is included in jquery-ui.js.

    It is likely there’s a plugin that uses the old UI scripts and doesn’t use core’s versions, and another one that uses core’s versions. If that’s the case the first plugin would need to be fixed/updated.

    • This reply was modified 4 years, 2 months ago by Andrew Ozz.
    • This reply was modified 4 years, 2 months ago by Andrew Ozz.
    Thread Starter hudin

    (@hudin)

    Okay, there we go. It was being called by the “Redirect After Login, Registration & Logout” plugin. No idea why it was dumping it in there. Deactivated and now it all is working again. Pretty shabby plugin anyways.

    What’s weird, if that I only had it active on one site and yet it was horking up all my sites. Annoying.

    Have to assume that not terribly many people are using this plugin which is why the pitchforks have been less than one would expect with the 5.6 update, but it’s clear some weirdness happened in WP cleaning things up.

    Plugin Author Andrew Ozz

    (@azaozz)

    Glad to hear you were able to fix this. Yeah, unfortunately some plugins may not “behave” in the best way. It wouldn’t have been a problem if that plugin was loading jQuery UI from WordPress (like most other plugins) instead of adding it’s own version.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Broken for good’ is closed to new replies.