CUNY Academic Commons

See discussion at https://redmine.gc.cuny.edu/issues/15767#note-2 and follow-up. The ml-slider folks have promised to fix the issue, but have not done so. https://wordpress.org/support/topic/call-to-get_plugins-causing-performance-problems/

Until they do, we will need to patch ml-slider each time it's updated. This happens next in the 2.1.5 release.

We should also have some sort of system for notifying the release manager (ie me) whenever this patch needs to be applied. Looking at GitHub Actions results is already part of my workflow, which helps me catch invalid syntax and other items. But this one is kinda hard to catch with static analysis tools. Instead, I'm thinking I'll add something to the wp-cli-cac script that I use for bulk plugin updates, something that throws a huge notice about plugins that need manual attention after they've received an update.