-
-
Notifications
You must be signed in to change notification settings - Fork 5.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The WYSIWYG editor and preview do not work in Wiki #14196
Comments
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. |
what browser are you using? if you look at the development console do you get errors etc? |
In Firefox, I watched the browser console, but there were no new messages. |
Another test performed – another browser where it doesn't work:
|
It is working on firefox 84 here |
Is it possible you have cached assets? |
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 |
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. |
Have you tried CTRL-F5? To forciblyreload in case you have an oldcached ServiceWorker |
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. |
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. |
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). |
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. |
As I wrote above: I used browsers that I have not used for a long time => they did not have a chance to have such data in the cache, none worked. I used latest Firefox on another virtual machine, where there had never been access to any Gitea instance before => had no chance to have such data in the cache, it worked on try.gitea.io (i.e. 1.14.0-devel), but it didn't work on our 1.13.1. |
I also have this issue on my selfhosted gitea I found there was a commit between Let me know if you need any other information. |
I can confirm this is a bug and should be fixed on v1.13.2 |
Same with me. Fresh installation with docker image gitea/gitea:1.13.1 |
Same, on Gitea 1.13.1 using Firefox 84.0.2 and Chromium 87.0 |
Do someone have a quick turn around for 1.13.1 docker until 1.13.2? |
I think we can just remove the preview tab because there is already a preview button on the toobar. |
I think the issue is here: https://github.com/go-gitea/gitea/blob/release/v1.13/web_src/js/index.js#L1362 should be |
[x]
):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.
The text was updated successfully, but these errors were encountered: