[5.x] Missing configurations and settings?

[zsavajji]

Description

We updated a project to craftcms/ckeditor 5.x and we noticed that our custom configurations disappeared.
Is this intended behavior? Is there no mention of it in the changelog?

Steps to reproduce

1. Update to 5.x
2. Search for CKEditor settings
3. ???

Additional info

• Craft version: 5.9.14
• PHP version: 8.3.30
• Database driver & version: MariaDB 10.11
• Plugins & versions: CKEditor 5

[linear]

PT-3055

[i-just]

Hi, thanks for getting in touch! Yes, that’s expected. The concept of separate CKEditor Configs was dropped in v5. You can now define all of that directly within the field’s settings: https://github.com/craftcms/ckeditor/blob/5.x/README.md#configuration.

I’ll close this now, but feel free to reply if anything’s unclear.

[zsavajji]

Hi @i-just thank you for the response.
I find though that after updating to 5.0.1, my fields completely lose configuration, is there no automatic migration path to apply the settings from the old configs to the fields themselves except for moving them manually?

Thanks

[i-just]

That should already be happening automatically through the migration we wrote.
Let me check if I understand this correctly. You upgraded to 5.0.1, ran migrations, and when you edit the CKEditor field in the control panel, the Toolbar, Config Options, Custom Styles, etc, don’t include the items/code that were there in the CKEditor Config before the upgrade?

Can you provide some details on what exactly is happening in your case? Which version were you on before updating to 5.0.1? What settings were used by the CKE field where the configuration is lost during upgrade, and what CKE Config was used by that field (screenshots should be a good place to start).

[zsavajji]

Hi,
here you go. After the update i quickly reverted yesterday, but now I can see that the field config goes full error after the update:

Also, it gets displayed as such:

Here you can also find the situation before the update:

Thank you

[i-just]

Thanks for the extra info! I am not able to reproduce this issue. If I upgrade to CKEditor 5.0.1 and apply pending migrations, the config gets migrated to the fields as expected.

The error you showed in your first screenshot suggests that something’s trying to use the old markup for the field’s settings page. Can you please clear all caches and see if the issue persists?

[zsavajji]

Hi @i-just, applied the update again on a database backup, updated the plugin and cleared all caches: here is where we stand now:

Content is still unstyled :(

[mnlmaier]

@i-just — To clarify: Did you drop the concept of global field configs entirely? What happens if I need to adjust a config across several CKEditor fields which have previously shared their configurations?

[i-just]

Thanks for the update! Any chance you could send your composer.json, composer.lock, and database export from before you updated to CKEditor 5.0.1, along with composer.json, composer.lock from after the upgrade, to support@craftcms.com so we can try to reproduce and dig deeper?

Did you drop the concept of global field configs entirely?

yes

What happens if I need to adjust a config across several CKEditor fields which have previously shared their configurations?

you'll need to adjust all the fields that require those changes

[samuelreichor]

@i-just What's the point of removing the global configs? We always had 2 or more global configs that are shared across a lot of ckEditor/Redactor fields. This makes things unmaintainable if someone uses a lot of different fields..

[i-just]

@samuelreichor, have a look at #504. It explains our motives for removing the global configs.