Cannot edit or create pages (WYSIWYG not loading, missing buttons) in offline XWiki setup

Help / Discuss
, ,
1

Hello everyone,

I’m facing a blocking issue with my XWiki instance and would like to know if anyone has experienced something similar.

Context

  • Installed version: xwiki-platform-distribution-flavor-jetty-hsqldb-18.1.0

  • Environment: offline Linux

  • JDK properly installed

  • Fully offline installation

  • Set up an offline Maven repository containing all required dependencies and extensions

  • Installed extensions via the Extension Manager

Issue

I can no longer edit pages:

  • When clicking on “Edit”, I get a loading spinner that runs indefinitely

  • The WYSIWYG editor never appears

Additionally, when creating pages:

  • The page opens, but no buttons are displayed (no Save, Save & Continue, or Cancel)

  • This makes it impossible to create or save pages

Strange behavior

  • Page creation works only with certain templates, for example “Create Task” (from Task Manager)

  • But it does not work for basic/blank pages

Question

Has anyone already encountered this kind of issue in an offline setup?
Do you have any ideas or debugging suggestions (missing dependencies, JS/CSS issues, incomplete extensions, caching, etc.)?

Thanks in advance for your help :folded_hands:

2

Did you try disabling the Extension Real Time WYSIWYG editor and then try please. Just my thought..

3

I tried to uninstall and install again in the extension manager the Real Time WYSIWYG but it doesn’t worked.

4

I also tried installing a new instance of XWiki, but I encountered this problem. I cleared the browser data, but it still doesn’t work.

I am using Linux, and for each installation I unzip the distribution (xwiki-platform-distribution-flavor-jetty-hsqldb-17.10.6). Then I copy the contents of the XIP package into data/extension/repository to get a base flavor, and I ignore the replacement of existing files. Is there anything I might be doing wrong in this step?

I previously had this issue on a Windows instance, but I was able to fix it by creating a new instance. However, in this case, the problem persists regardless of the instance.