You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using the CKEditor Custom Field in a Strapi Content-Type or Component the field name is not displayed, instead it always shows "CKEditor" as can be seen in the screenshot below. Customizing the "Label" through the "Configure the view" option also doesn't change the displayed label. This is a big issue when having multiple CKEditor Custom Fields in the same Content-Type or Component. The only workaround can be seen in the attached screenshot, where the second CKEditor field has a description from "Configure the view" that is displayed under the field.
To Reproduce
Steps to reproduce the behavior:
Create a Content-Type or Component with a CKEditor Custom Field.
Create an Entity of the Content-Type or use the Component
CKEditor field always has "CKEditor" displayed as field label, not the actual field name or cusotm label from "Configure the view"
Expected behavior
The actual field name or the custom label from "Configure the view" if it exists should be displayed as the label.
Describe the bug
When using the CKEditor Custom Field in a Strapi Content-Type or Component the field name is not displayed, instead it always shows "CKEditor" as can be seen in the screenshot below. Customizing the "Label" through the "Configure the view" option also doesn't change the displayed label. This is a big issue when having multiple CKEditor Custom Fields in the same Content-Type or Component. The only workaround can be seen in the attached screenshot, where the second CKEditor field has a description from "Configure the view" that is displayed under the field.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The actual field name or the custom label from "Configure the view" if it exists should be displayed as the label.
Screenshots
please complete the following information:
The text was updated successfully, but these errors were encountered: