MyArcade plugin

Please try installing https://www.ads-software.com/plugins/enable-jquery-migrate-helper/ to see if that fixes the issue.

For more information on what this is all about, see https://wptavern.com/major-jquery-changes-on-the-way-for-wordpress-5-5-and-beyond

If the plugin helps, please contact the developers of the plugins or themes noted in its admin messages: I recommend asking at https://www.ads-software.com/support/plugin/myarcadeblog/#new-post so the plugin’s / theme’s developers and support community can help you with this.

Hi, this worked! Thank you! Guess I will have to wait for MyArcade dev to make the plugin work with WP 5.5.

Cheers!

Note that that plugin now has the following notice: “This plugin has been closed and is no longer available for download”.

THis could be for various reasons that inlcude a plugin violation and an unresolved security issue. It may be time to consider replacing that plugin with one that is regaularly maintained.

Hi,

MyArcadePlugin works well with the latest WordPress version. The most issues are caused my the plugin WP Favorite Posts that many MyArcadePlugin users use, too.

Please try to deactivate that plugin if you use it.

@barnez The user uses our pro or a free version which is available at GitHub.

Best regards
Daniel

MyArcadePlugin Support

@daniel Bakovic

Great. Happy to hear that MyArcade lives on ??

Hi Daniel,
I don’t have WP Favorite Posts plugin installed. I use the Pro version of MyArcade

Hi Barnez,
I don’t see the issue with the Jquery plugin in the WP repository. No warning about deprecation. Plugin works fine. Only gives warning when installed about the EU notice on Jetpack widget. Site works 100% with it installed.

Glenn

Because you’re using a commercial plugin, please use their official support channel. We feel they are best equipped to support their products.

https://myarcadeplugin.com/forum/

Commercial products are not supported in these forums.

Hi Steven,
I did post there…while I was waiting for a response I posted here. I know that the issue was caused by the WP 5.5 update. Just wanted to get a resolution. Sorry for the inconvenience.

Glenn