Bug #25049
openUpdate WP to 7.0.x series
0%
Description
WP 7.0 was released on May 20. Can we aim for an update to the 7.0.x series for the 2.7.6 release on June 23?
Jeremy, in the past you've looked to see if there are issues with Gutenberg and the CV editor. Perhaps we could start there?
Related issues
Updated by Boone Gorges 3 months ago
- Related to Bug #24759: Disable real time collaboration in WordPress added
Updated by Boone Gorges about 2 months ago
- Target version changed from 2.7.6 to 2.7.8
Updated by Boone Gorges 9 days ago
Jeremy, another ping about this. Anything you see in the CV editor that we should be concerned about?
Updated by Jeremy Felt 7 days ago
I've just pushed an update in https://github.com/cuny-academic-commons/cac/commit/c589c396286a8938bb9f148c8d0402ed4b2ced1c that:
- Transfers @happyprime/ibe-slim (my annoying fork of Automattic's isolated block editor) into the CV editor itself. That fork was single purpose and the transfer makes ongoing maintenance easier.
- Remove even more unused code from the isolated editor.
- Update `wordpress/*` dependencies.
- Adjusted block code code for WP 7.x / future React 19 compatibility.
I've tested this in WP 6.9.7 (current), WP 7.0.4, and in the nightly WP 7.1/2 build with and without the latest version of Gutenberg (23.7.2) active.
All clear for the 7.0 series (or 7.1).
Before 7.2, I'm going to see if the editor components have progressed enough that we can remove the old isolated stuff completely. I'm going to toss that at an agent and see what it comes back with.
Updated by Jeremy Felt 7 days ago
Boone - I just realized I pushed this (and another commit) to 2.8.x instead of 2.7.x. Sorry about that. I'm going to let it be, but happy to apply it on 2.7.x if needed.
Updated by Boone Gorges 6 days ago
Thanks so much for this! Please cherry-pick back to 2.7.x when you get a moment.
Updated by Jeremy Felt 6 days ago
This has been cherry-picked to the 2.7.x branch