CKEditor not rendering for some users

[remcoov]

Some users in my clients website are reporting CKEditor not being rendered. Strange thing is, for one user it does and the other it does not. I am running the latest CKEditor version (5.1.0) and the latest Craft 5.9.15 version. I am not seeing any console errors.

FWIW, I updated this site from Craft 4 last week. It already had CKEditor working.

[linear]

PT-3062

[i-just]

Hi, thanks for getting in touch!

Strange thing is, for one user it does and the other it does not.

Are they both using the same browser? For a user who doesn’t see the CKEditor field rendered, does it happen with all the CKEditor fields or only some? If only some don’t render, do they have anything in common, any special configuration?

[remcoov]

Hi, it happens with all the CKEditor fields. The user tried different types of browers.

[apoupart]

Hello!
I am currently experiencing the same issue in Chrome and Firefox (I haven't tested other browsers).
After migrating from Craft 4 and CKEditor 4 this week, the textarea/editor doesn't render properly in the control panel.

Interesting finding: I noticed that if the user changes their account preferences to use English as the language, the field renders normally and the content is there. However, if the language is set to anything else (like French, for example), the field and its content seem to disappear entirely.

[i-just]

Thanks both! I was hoping the language tip would help me reproduce this, but I’m still not able to stop it from rendering. Any chance you could send your database export, along with composer.json and composer.lock, to support@craftcms.com, and point out which user is experiencing this behaviour and on which element edit page?

[remcoov]

Just sent this to you! :-)

[remcoov]

@apoupart Totally missed your comment and we came to the same conclusion on our own, haha. Changing user language fixes it, because the translations file (in our case: cpresources/*/lib/translations/nl-nl.js) not being found is a blocking error.

[i-just]

Thanks both! I can reproduce this if I set the defaultCpLanguage() in the config/general.php to a value like nl-NL or pl-PL, etc. Setting it to nl, pl, en-GB or en-US doesn’t.

Now that I know how to reliably reproduce, I’ll have a look at what’s causing it and how we can fix it.

[i-just]

Quick update: I just raised a PR to address this.

[brandonkelly]

We just released v5.2.0 with the fix for this. Thanks again!