Automated Drupal 11 compatibility fixes for ckeditor_div_manager

This is an automated patch generated using Upgrade Status and Drupal Rector. Please see the issue summary for more details. A merge request (MR) is also openend and updated.

It is important that any automated tests available are run and that you manually test the changes.

Drupal 11 Compatibility

According to the Upgrade Status module → these changes make this module compatible with Drupal 11! 🎉
Therefore these changes update the info.yml file for Drupal 11 compatibility.

Leaving this issue open, even after committing the current patch or merging the MR, will allow the Project Update Bot → to post additional Drupal 11 compatibility fixes as they become available in Drupal Rector.

Debug information

These packages were used to generate the fixes:

1. drupal/upgrade_status: 4.3.1
2. mglaman/phpstan-drupal: 1.2.11
3. palantirnet/drupal-rector: 0.20.1

Besides the other open issues, it runs nicely with Drupal 11. No additional problems found due to Drupal 11.

I have applied the patch successfully and now the module (ckeditor_div_manager) is compatible with Drupal 11, "Local 11-ready" as reported by the 'Upgrade Status' module.

nice :-) thank you…

Perhaps the maintainers should close this issue and release a new version?

This will not work with Drupal 11.2 despite appearing as compatible under the 'Upgrade Status' module;

D11.2 upgrades CKE5 to v45, which includes changes that break the CKE4 Div Manager plugin. More detail in this ticket.

@timfletcher A fix has been done in issue #3531695, so once that get's committed, then the above changes should allow this to run on 11.2+.

This has been included with the 3.0.0-alpha2 release.

It would make sense for the 3.0.x branch to require ^10.3 || ^11.0.

Also, a release node for branch 3.0.x should be created.

@liam what’s the reasoning behind specifying ^10.3 || ^11.0? If anything, it might make more sense to require ^10.5 || ^11.2, since those are the versions where CKEditor 5 was upgraded to v45 in core. That said, I’d lean toward keeping the requirements more open for flexibility, unless we hit specific compatibility issues.

Also worth noting, a related ticket that addressed CKEditor5 v45 compatibility was just merged, targeting changes introduced in 10.5 and 11.2 - 3531695 🐛 does not work after the Drupal update to version 10.5 Active .

It's pretty easy to be compatible with Drupal 11 and also as old as 10.3. Older than that can be more difficult. It wouldn't be wrong to require more recent versions. I would generally at least support all currently-supported versions, though I can see the argument for a module related to CKEditor to require v45.

Automatically closed - issue fixed for 2 weeks with no activity.