In my fresh installation of the module, it did not object to the absence of the fakeobjects js plugin. Later, as things were crashing, I found that it was looking for the file in the core/assets/vendor/ckedit/plugin directory. I loaded it in there and all is finally well.
Was that just some local weirdness, or is that a real bug?
| Comment | File | Size | Author |
|---|---|---|---|
| #5 | fakeobjects-missing_plugin-3002953-5.patch | 907 bytes | sherakama |
| #3 | fakeobjects-missing_plugin-3002953.patch | 950 bytes | pookmish |
Comments
Comment #2
pookmish commentedI too have encountered this error.
I'm starting to investigate
Comment #3
pookmish commentedI was able to make progress on the issue. the problem is when the page has a CKEditor formatted field but the CKEditor text format is not using any button that uses the fakeobjects. So the CKEditor doesn't load the FakeObjects plugin. This patch extends another interface which forces the plugin to load on every CKEditor area.
Comment #4
bkosborneBut why is CKEditor trying to load the plugin in that scenario?
Comment #5
sherakama commentedRe-roll for version 8.1.1
Comment #6
bygeoffthompson commentedTested and working. Rerolled patch works with D9 ready version 1.1.
Thank you
Comment #7
kevinquillen commentedI've not encountered this scenario. Why would FakeObjects be needed to be force loaded when no active plugins require it? This plugin is a behind the scenes wiring for other plugins that leverage it to represent object data in the editor.
Is this some edge case item or is there a common way to replicate this that causes issues?