Changes between Initial Version and Version 1 of Ticket #59718, comment 1
- Timestamp:
- 10/24/2023 03:57:14 PM (2 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #59718, comment 1
initial v1 20 20 What was discussed in the slack thread and thus here in this ticket: 21 21 22 1. Could Core not load its class files and/or functions that will be incompatible with different versions of Gutenberg that have the same named classes and/or functions?22 1. **Option 1**: Could Core not load its class files and/or functions that will be incompatible with different versions of Gutenberg that have the same named classes and/or functions? 23 23 24 2. Is there a way to trigger `_upgrade_core_deactivate_incompatible_plugins()` as part of the upgrade processes not using Core's `update_core()`?24 2. **Option 2**: Is there a way to trigger `_upgrade_core_deactivate_incompatible_plugins()` as part of the upgrade processes not using Core's `update_core()`? 25 25 26 3. Could the Gutenberg team fix the incompatibilities in each older version and then ship .x release for each? Note: These upgrade processes will first upgrade the plugin before upgrading WordPress Core.26 3. **Option 3**: Could the Gutenberg team fix the incompatibilities in each older version and then ship .x release for each? Note: These upgrade processes will first upgrade the plugin before upgrading WordPress Core. 27 27 28 28 I'm bringing this ticket into 6.4 for discussion. That said, any changes in Core's source code must be minimal and with very high confidence given how late it is in the cycle.