Site menus not working after wordpress upgrade to 5.6

Hello talbotp,

recent versions of WordPress do contain some changes in jQuery library which is used by basically every theme and plugin. Pleaes try to install https://wordpress.org/plugins/enable-jquery-migrate-helper/ to see if that fixes the issue.

What theme are you using? Is it free to download, so that I can give it a try?

Please also send output of Settings -> FV Player -> Tools -> System Info.

Thanks,
Martin

Hello talbotp,

it appears this is a bug in the BuddyBoss theme. It has this code which listens to the “ready” event and when it occurs it initializes the menu click action in BuddyBossTheme.init().

$( document ).on(
  'ready',
  function () {
    BuddyBossTheme.init();
    ...
  }
);

However it just listens to any “ready” event in the document, including the child elements. So when the Flowplayer library which we use triggers “ready” for the video as it starts playing, BuddyBoss will init that menu handler again. And then when you click the menu icon it counts as two clicks – one to open it and the other to close it.

There was no recent change in FV Player that would cause this, but it’s possible this issue is more visible with new jQuery in WordPress 5.6

So I would recommend you do not update to WordPress 5.6 until BuddyBoss developers fix this as what they do is not listed among:

jQuery offers several ways to attach a function that will run when the DOM is ready. All of the following syntaxes are equivalent

Which you can check here: https://api.jquery.com/ready/

That document also says:

As of jQuery 3.0, only the first syntax is recommended; the other syntaxes still work but are deprecated.

They recommend using

$( handler )

…which is the second example here: https://learn.jquery.com/using-jquery-core/document-ready/

Thanks,
Martin

Hello talbotp,

please let us know if this is still an issue or if BuddyBoss developers managed to improve this.

Thanks,
Martin

Hello Dax,

I hope they will be able to fix it as it doesn’t change anything structurally. It’s just about rewriting some of their JavaScript event hooks to the form which jQuery recommends.

Thanks,
Martin