The WYSIWYG editor and preview do not work in Wiki

[SlavekB]

• Gitea version (or commit ref): 1.13.1
• Git version: 2.20.1
• Operating system: Debian 10.x (Buster)
• Installed: downloaded official binary
• Started: as systemd service
• Database (use [x]):
  • PostgreSQL
  • MySQL
  • MSSQL
  • SQLite
• Can you reproduce the bug at https://try.gitea.io:
  • Yes – wiki of any project
  • No

Description

When creating a new wiki page and opening an existing wiki page for editing, the WYSIWYG editor toolbar is not displayed there. At the same time, the preview does nothing at all.

This seems similar to issue #12971 except that the WYSIWYG editor is not displayed at all, so there is no need to switch to textarea – it doesn't work from the beginning.

[zeripath]

I just tried this on try.gitea.io with Google Chrome | 87.0.4280.88 (Official Build) (64-bit) on ubuntu focal and it worked perfectly.

[zeripath]

what browser are you using? if you look at the development console do you get errors etc?

[SlavekB]

• Palemoon 28.17
• Firefox 68.9 (ESR)
• Chromium 57

In Firefox, I watched the browser console, but there were no new messages.

[SlavekB]

Another test performed – another browser where it doesn't work:

• Firefox 78.6 (ESR)

[zeripath]

It is working on firefox 84 here

[zeripath]

Is it possible you have cached assets?

[SlavekB]

If you mean in the browser, then I do not normally use Firefox or Chromium on my machine == these have not been running for a long time. The same goes for Firefox 78.6 on a Windows test machine. Furthermore, I only rarely go to try.gitea.io, so it doesn't seem possible that I have any old content cached there either.

[zeripath]

have you logged in? are you certain that there no console errors? Without having a clear way to reproduce or some errors to work with we're a bit stuck.

[zeripath]

Have you tried CTRL-F5? To forciblyreload in case you have an oldcached ServiceWorker

[SlavekB]

Another attempt – another machine where I never accessed any Gitea instance, this time Firefox 84. I assume that using a newer Firefox could be a change in that try.gitea.io works:

But Gitea 1.13.1 still has the same problem:

You can see an open Firefox console window in the screenshot. There is no new record at all.

[micheleCTDE]

Same issue on my machine. Firefox ESR 78.6 on Debian testing. Also same issue on a Windows 10 machine with Gitea Version: 1.14.0+dev-485-g632800eda.

[vanous]

Same issue here, both Firefox 84.0 (64-bit) and Chromium Version 87.0.4280.88 (Developer Build) built on Debian bullseye/sid, running on Debian bullseye/sid (64-bit), happening on Codeberg.

[mibuthu]

I have the same problem: Gitea 1.13.1 installed via Docker, tried with multiple browsers (e.g. Firefox 84, Brave 1.18, Opera 73).
I also cannot see any error in the browser console.

[gytisrepecka]

Did you try to clear Firefox cache?

After upgrading Gitea to version 1.13.1 I had visual editor and preview gone. Perhaps some static files were cached from previous version as clearing browser cache brought editor and preview back.