Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Contributor pewgeuges

    (@pewgeuges)

    @a223123131

    Thank you for catching this! Indeed there is an instance in jQuery Tools and it needs to be replaced.

    Curiously the tools meant to alert said nothing about this, and when jQuery.browser was redacted based on https://clorith.net/updating-jquery-code-in-your-unmaintained-wordpress-plugin-or-theme/ following several bug reports, we didn’t suspect that we weren’t done.

    When I tried to fully migrate to jQuery?UI using a new custom library downloaded for the purpose, I failed to get it running.

    I’m confident that Ben ( @rumperuu ) will succeed. Meanwhile I’ll fix the $.isFunction() for next release.

    Thanks!

    Thread Starter a223123131

    (@a223123131)

    No stress here… I just saw it in the official “jQuery Helper” plugin reported. Right now, there is no issue with it. WordPress is doing changes in jQuery since a while and finalize this with 5.7 as far as I know. So no issue right now, but maybe with the next WP release. So it is better to prepare now with no stress ??

    Plugin Contributor pewgeuges

    (@pewgeuges)

    Thank you. Indeed WordPress itself still seems to keep using lots of deprecated jQuery functions.

    To get the warning, I needed to check a box in jQuery Migrate Helper’s dashboard, then after reloading a page, look up the log in the dashboard’s second tab.

    It doesn’t tell with what to replace it though, unlike other functions have their replacement shown in the browser console. Official https://api.jquery.com/jquery.isfunction/ gives typeof x === "function" “in most cases”.

    Luckily in Footnotes’ case it seems to work. At least the plugin seems to keep working, tooltips are still functional. We can only hope that the fix doesn’t generate a new bug somewhere.

    Thank you a lot for directing us to fix this issue!

    As you know, despite my label I’m not a plugin author. I’m helping with some maintenance when I can. Earlier I asked WordPress to sync labels with reality, but the very role scheme used in the blog engine is wrong, mistaking publishers for “authors”, while calling “contributors” only those who cannot publish. Sadly the easy fix of unregistering me for commits after registering a second account didn’t come to mind earlier. Departing from the status quo so late is not likely to be well-taken.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Deprecated jQuery Code’ is closed to new replies.