Loadtime Error on CKEditor

Help / Discuss
1

Hi There,

we are experiencing ckeditor loadtime error when in page editing or comment editing mode. can anyone advice how to fix this and what is the issue of this error?

Error:

Load timeout for modules: xwiki-realtime-wysiwyg-editor,xwiki-realtime-interface,xwiki-l10n!xwiki-realtime-messages,xwiki-realtime-messages Common Errors

2

What version of XWIki are you using? Does it happen on any page, even when creating a new page? Does it happen for any user? Was this working before? Did you perform an upgrade recently? Have you tried to clear the browser cache and reload the page?

3

Hi, we are using 7.10.4 xwiki open sourve version. Yes it happened any all users when we try create and edit page, create and edit comment. this is new application onboarded to our organization have not been through any version upgrade at this moment

4

I think you meant 17.10.4. What web browser are you using? Do you reproduce with both Firefox and Chrome? Are you using Firefox ESR?

5

We are using MS Edge, yes the version is 17.10.4. yes any browsers are affected

6

hello any advice here? noticed that it was due to CKEditor and wysiwyg editor is enabled.

7

You mentioned:

we are experiencing ckeditor loadtime error

How does this manifest in the user interface, for your users? Is CKEditor loaded? Can you type? Do you see any error notification message?

It looks like the realtime editing JavaScript code failed to be loaded. You should check the Network tab to see why some of the HTTP requests that load JavaScript code are too slow or failing.

Realtime editing is used when creating or editing a page, but not when adding or editing a comment. Are you sure your get the same error in the JavaScript console (from the browser’s developer tools) when adding / editing a comment?

Have you tried disabling the xwiki-realtime plugin from the CKEditor administration section? Realtime editing relies on WebSockets and if you use a (reverse) proxy in front of the Java servlet container (e.g. nginx or Apache) then you need to make sure the proxy is properly forwarding the WebSocket upgrade requests.