Since early 2025, Drupal has been constantly warning users about the need to upgrade to higher versions and migrate away from version 7. Even websites still running on Drupal 7 can no longer use the update center, and this could potentially lead to security issues.
However, all these warnings and pressures are happening at a time when many modules for Drupal 10 or 11 are still incomplete or even missing altogether. For example, we used to have the CKEditor 4 module, which was extremely full-featured. It had options like a div wrapper, the ability to assign CSS classes or other attributes to images, and many capabilities for links as well.
But now, in CKEditor 5, we practically have nothing. There's not even a div wrapper to group a few paragraphs together, and we can’t add attributes to links or images.
I've thoroughly searched the internet, but I haven’t been able to find a solution. So the question is: what is someone supposed to do if they need an editor with the features of CKEditor 4?
Comments
Comment #2
g.abderrahim commentedHello @mehrdad201,
If i may ask what was the module you were using for ckeditor4 for div wrapper ?
Much appreciated
Comment #3
mehrdad201 commentedDear @gabderrahim,
In Drupal 7, when using CKEditor 4 in full mode, you can see the div wrapper option. However, I believe you need to add the div container button to the active toolbar for it to appear.
This is quite easy. You can also add a ckeditor.styles.js file to your theme folder and define all elements with custom CSS classes.
But in Drupal 11, you're required to use CKEditor 5, as version 4 is deprecated. Unfortunately, many of the features available in CKEditor 4 are no longer present.
If you're using Drupal 10, I recommend checking out ckeditor_div_manager module, which adds a div wrapper button to CKEditor 5. However, it's very basic and lacks the advanced capabilities that CKEditor 4 had in Drupal 7.
Also, please note that ckeditor_div_manager is not supported in Drupal 11.
I'm honestly very disappointed.
Comment #4
cilefen commentedComment #5
timfletcher commented@sime asked about the CKE4-5 plugin issue a while back
I'd advise against using the 3.x release of the CKE Div Manager module if you are using CKE5.
I've been running it in Drupal 10 and now patched in Drupal 11 (just adding '11' to the
core_version_requirementsinckeditor_div_manager.info.ymlwas enough), and it has broken in the update from Drupal 11.1.8 > 11.2.The issue seems to be that the Div Manager module references the deprecated CKE4 Div manager plugin, which has no CKE5 equivalent or clear upgrade path - yet the CKE Div Manager module uses it with CKE5 (in the maintainer's defence, 3.x is currently an alpha build marked as D10 compatible only and well pre-dates this update, so this is uncharted territory).
This breaks because Drupal 11.2 updates the CKE5 version used in Core to one that is incompatible with the CKE4 Div Manager plugin as the location of the CKE icons pack changes.
This also prevents any other non-CKE operations that run on the frontend from executing, such as cleaning HTML, fixing broken tags, and critically, stripping prohibited tags like
<script>!The hunt continues for a future-proof way to manage
<div>s via the UI for editors.It definitely sucks that pretty basic functionality is still missing from CKE5 in Drupal. A lot of progress has been made, but we are being forced to jump from the sinking ship onto the mostly-built one.
Comment #6
nicxvan commentedIt's there any reason you've not updated to Drupal 10 instead of looking at 11? It's still a fully supported version of Drupal and will be until December of next year.
Also, to answer your question about what you can do. You can test patches that provide support for Drupal 11, for example the module you mentioned there is an issue here: #3448621: Automated Drupal 11 compatibility fixes for ckeditor_div_manager this issue has been open for over a year and only just started getting reviews in March.
If a module has not updated you can apply for maintainership and provide releases helping the whole community.
That being said I think you can add div with classes natively in ckeditor 5 but please don't quote me I'm not super familiar with that plugin.
Also, you might want to create an issue in the ckeditor queue, their bc policy doesn't quite align in the way Drupal manages BC.
Comment #7
nicxvan commentedMade an attempt to update the title. Please update it if that's not accurate.
Comment #9
quietone commented@nicxvan provides good guidance here.
Given that the Core issue queue is not the ideal place for support requests you can also check the other support options listed on our Support page, including the Drupal Forums and Drupal Answers. There is also Drupal Slack. You may get better replies in one of those places.
I am closing this per the guidance in Handle or refer a support request in an issue.