customConfig conflicts with other CKEDitor instance customConfig #3361
Labels
core
The issue is caused by the editor core code.
status:confirmed
An issue confirmed by the development team.
type:bug
A bug.
Milestone
Type of report
Bug
Provide detailed reproduction steps (if any)
I'm using Pimcore as Content Management System, which implements CKEditor as their WYSIWYG editor for rich text fields. It allows specifying a
customConfigfile (Reference) for each field, which will be passed to CKEditor. This is a follow-up from pimcore/pimcore#1124 since Pimcore mentioned that the following bug is related to CKEditor itself.In the backend interface, where users can edit fields using CKEditor, I have several different fields on one page, all with an individual CKEditor instance and sometimes with different configuration files (
customConfig).Imagine the following situation:
One instance of CKEditor for field A with the following custom config file contents (acutally doesn't matter, it's just differently to the other field below):
Then another instance of CKEditor for field B with the following custom config file contents (acutally doesn't matter, it's just differently to the other field above):
And finally, another CKEditor instance for field C with the exact same custom config file like field A.
Now, in this case field C should have the exact same toolbar like field A, because they are referencing to the same
customConfigfile. But because field B - with a separate CKEditor instance - is rendered between those two fields, with a different configuration, field C and any subsequent CKEditor instance gets the configuration of field B - the wrong configuration.So, just to visualize the issue, this is the toolbar for field A:
In this screenshot you can also see field B ("Content"), which has a different
customConfig.And this is the config for field C:
In this screenshot you can see that field C get's a the wrong toolbar, it should look like field A.
Expected result
A CKEditor instance should always use the provided
customConfig.Actual result
When mixing several CKEditor instances with different
customConfigfiles, CKEditor uses the wrong configuration.Other details
The text was updated successfully, but these errors were encountered: