Sorry to hear you’re getting errors with widgets. I haven’t been able to reproduce this. Which Charitable extensions do you have installed?
In the meantime, the following plugin may resolve the problem:
Restoring jQuery Migrate via the Plugin does resolve the issue. Do you plan to update your jQuery library for Charitable?
Here are the 4 Charitable Plugins that may have contributed to Widgets not being editable:
Charitable Recurring Donations
Charitable Stripe Payment Gateway
Charitable User Avatar
I also had an issue with WPBakery Page Builder (may or may not be necessary) and Advanced Custom Fields (might be the key piece) where the page edit screen would encounter a fatal JS error due to jQuery UI being undefined when Advanced Custom Fields tried to load the timepicker addon JS.
Deactivating Charitable resolved the issue, and re-enabling Charitable had the issue resurface.
I then installed https://wordpress.org/plugins/enable-jquery-migrate-helper/, as mentioned, and it went back to working with Charitable & ACF enabled on the site at the same time.
Not sure of the exact cause/conflict, but I imagine this is something that shouldn’t need an additional plugin to have things work properly.
Oddly, this is the only thing Enable jQuery Migrate Helper output on these pages (“odd” since this warning is present on pages where the fatal JS error wasn’t happening):
jQuery Migrate Helper — Warnings encountered
This page generated the following warnings:
/wp-content/plugins/better-font-awesome/vendor/mickey-kay/better-font-awesome-library/js/admin.js: 'ready' event is deprecated
Please make sure you are using the latest version of all of your plugins, and your theme. If you are, you may want to ask the developers of the code mentioned in the warnings for an update.
Hey @kzeni and @swmarlow,
jquery-core library in WordPress (instead of the more commonly used
jquery). It looks like
jquery-core was removed in WP 5.5, which is why this started causing problems in a few different places, where Charitable’s scripts were loading before the jQuery library.
That makes sense based on what I was seeing. Thanks for getting it resolved and letting us know! 🙂