As part of the WP 5.5 upgrade that we'll be performing later in the month, jquery-migrate is no longer enqueued by default when jquery is enqueued. We need to ensure compatibility for bp-nelo, which we can either do by remediating the errors or by enqueuing jquery-migrate (the latter is obviously much easier). But we also might want to consider globally enqueuing jquery-migrate for the time being, because it's likely that other plugins/themes using jQuery on our many sites will break without jquery-migrate. We will need a plan of attack for addressing this problem in the longer term, but for now it might be wise to use the global band-aid. Ray, I'm CCing you in case you have opinions about this.
#1 Updated by Boone Gorges about 1 year ago
- Status changed from New to Staged for Production Release
Here's what I'm going to do for 1.17.4 and the WP 5.5.x update: https://github.com/cuny-academic-commons/cac/commit/0a61df965c67fed4e3b6ffad5839310eef074cb7
This does two things:
1. Enqueues jquery-migrate on the root site, via bp-nelo
2. Enqueues jquery-migrate on all secondary sites where jquery is also enqueued
Doing it separately means that we can roll these changes back separately, as needed.
I'll open separate tickets for the removal of jquery-migrate.