CKEditor not loading since 9.5.6
We just updated to Typo3 9.5.6.
Custom RTE fields are now rendered as simple textareas without RTE and without error message.
Things get clearer when we try to use our custom RTE-YAML-definition. The YAML definition wants to import base functionalities of the CKEditor extension. This creates this error message:
#1485784246 RuntimeException YAML File "EXT:rte_ckeditor/Configuration/RTE/Processing.yaml" could not be loaded
Could this be due to the new security features?
Updated by Josef Glatz about 2 years ago
- Status changed from New to Needs Feedback
Hi Jeff, thank you for your issue!¶
Unfortunately, I can't reproduce your problem in two composer based TYPO3 installations running it with 9.5 master Branch `9.5.*@dev`.
Can you give me some more details about your environment or even share some of your custom RTE presets.?
Updated by Oliver Hader about 2 years ago
- Priority changed from Must have to Should have
Jeff, did you try the usual steps like clearing caches (incl PHP's OPcache) and ensuring that the upgrade to TYPO3 v9.5.6 was successful and complete - e.g. is the according file available in
Updated by Tom Novotny about 2 years ago
- Assignee set to Josef Glatz
I'd like to re-open this issue, since it's not loading on my 9.5.7 installations.
Error in console:
at window.CKEDITOR.window.CKEDITOR.dom.CKEDITOR.resourceManager.<anonymous> (ckeditor.js?bust=dfa3a8a88e23a16215595742343b326855743fc2:249)
at f (ckeditor.js?bust=dfa3a8a88e23a16215595742343b326855743fc2:245)
at Array.n (ckeditor.js?bust=dfa3a8a88e23a16215595742343b326855743fc2:245)
at u (ckeditor.js?bust=dfa3a8a88e23a16215595742343b326855743fc2:245)
at HTMLScriptElement.CKEDITOR.env.ie.d.$.onerror (ckeditor.js?bust=dfa3a8a88e23a16215595742343b326855743fc2:246)
Since it's missing the RTE is not being loaded.
[WIP] Collecting more details...
Updated by Riccardo De Contardi almost 2 years ago
- Status changed from Needs Feedback to Closed
- Assignee deleted (
No feedback since the last 90 days => closing this issue.
If you think that this is the wrong decision or experience the issue again and have more information about how to reproduce your problem, please reopen it or open a new issue with a reference to this one.
Thank you and best regards