github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-03-14 11:56:41 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

The WYSIWYG editor and preview do not work in Wiki #6609

New Issue
Closed
opened 2025-11-02 07:01:14 -06:00 by GiteaMirror · 22 comments
GiteaMirror commented 2025-11-02 07:01:14 -06:00
Owner
Copy Link

Originally created by @SlavekB on GitHub (Dec 30, 2020).

  • 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.

Originally created by @SlavekB on GitHub (Dec 30, 2020). <!-- 1. Please speak English, this is the language all maintainers can speak and write. 2. Please ask questions or configuration/deploy problems on our Discord server (https://discord.gg/gitea) or forum (https://discourse.gitea.io). 3. Please take a moment to check that your issue doesn't already exist. 4. Make sure it's not mentioned in the FAQ (https://docs.gitea.io/en-us/faq) 5. Please give all relevant information below for bug reports, because incomplete details will be handled as an invalid report. --> - Gitea version (or commit ref): 1.13.1 - Git version: 2.20.1 - Operating system: Debian 10.x (Buster) - Installed: downloaded official binary <!-- Please include information on whether you built gitea yourself, used one of our downloads or are using some other package --> - Started: as systemd service <!-- Please also tell us how you are running gitea, e.g. if it is being run from docker, a command-line, systemd etc. ---> <!-- If you are using a package or systemd tell us what distribution you are using --> - Database (use `[x]`): - [ ] PostgreSQL - [x] MySQL - [ ] MSSQL - [ ] SQLite - Can you reproduce the bug at https://try.gitea.io: - [x] 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.
GiteaMirror added the outdated/theme/markdowntype/bug labels 2025-11-02 07:01:14 -06:00
GiteaMirror commented 2025-11-02 07:01:16 -06:00
Author
Owner
Copy Link

@zeripath commented on GitHub (Dec 30, 2020):

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 commented on GitHub (Dec 30, 2020): 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.
GiteaMirror commented 2025-11-02 07:01:16 -06:00
Author
Owner
Copy Link

@zeripath commented on GitHub (Dec 30, 2020):

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

@zeripath commented on GitHub (Dec 30, 2020): what browser are you using? if you look at the development console do you get errors etc?
GiteaMirror commented 2025-11-02 07:01:16 -06:00
Author
Owner
Copy Link

@SlavekB commented on GitHub (Dec 30, 2020):

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

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

@SlavekB commented on GitHub (Dec 30, 2020): + Palemoon 28.17 + Firefox 68.9 (ESR) + Chromium 57 In Firefox, I watched the browser console, but there were no new messages.
GiteaMirror commented 2025-11-02 07:01:16 -06:00
Author
Owner
Copy Link

@SlavekB commented on GitHub (Dec 30, 2020):

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

  • Firefox 78.6 (ESR)
@SlavekB commented on GitHub (Dec 30, 2020): Another test performed – another browser where it doesn't work: + Firefox 78.6 (ESR)
GiteaMirror commented 2025-11-02 07:01:16 -06:00
Author
Owner
Copy Link

@zeripath commented on GitHub (Dec 30, 2020):

It is working on firefox 84 here

@zeripath commented on GitHub (Dec 30, 2020): It is working on firefox 84 here
GiteaMirror commented 2025-11-02 07:01:17 -06:00
Author
Owner
Copy Link

@zeripath commented on GitHub (Dec 30, 2020):

Is it possible you have cached assets?

@zeripath commented on GitHub (Dec 30, 2020): Is it possible you have cached assets?
GiteaMirror commented 2025-11-02 07:01:17 -06:00
Author
Owner
Copy Link

@SlavekB commented on GitHub (Dec 30, 2020):

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.

@SlavekB commented on GitHub (Dec 30, 2020): 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.
GiteaMirror commented 2025-11-02 07:01:17 -06:00
Author
Owner
Copy Link

@zeripath commented on GitHub (Dec 30, 2020):

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 commented on GitHub (Dec 30, 2020): 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.
GiteaMirror commented 2025-11-02 07:01:17 -06:00
Author
Owner
Copy Link

@zeripath commented on GitHub (Dec 30, 2020):

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

@zeripath commented on GitHub (Dec 30, 2020): Have you tried CTRL-F5? To forciblyreload in case you have an oldcached ServiceWorker
GiteaMirror commented 2025-11-02 07:01:17 -06:00
Author
Owner
Copy Link

@SlavekB commented on GitHub (Dec 30, 2020):

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:
snimek82

But Gitea 1.13.1 still has the same problem:
snimek83

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

@SlavekB commented on GitHub (Dec 30, 2020): 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: ![snimek82](https://user-images.githubusercontent.com/9537053/103372250-c8a7ea00-4ad1-11eb-961c-c6b52c68a157.png) But Gitea 1.13.1 still has the same problem: ![snimek83](https://user-images.githubusercontent.com/9537053/103372273-dbbaba00-4ad1-11eb-9393-833d86d3cabb.png) You can see an open Firefox console window in the screenshot. There is no new record at all.
GiteaMirror commented 2025-11-02 07:01:18 -06:00
Author
Owner
Copy Link

@micheleCTDE commented on GitHub (Dec 31, 2020):

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.

@micheleCTDE commented on GitHub (Dec 31, 2020): 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.
GiteaMirror commented 2025-11-02 07:01:18 -06:00
Author
Owner
Copy Link

@vanous commented on GitHub (Jan 2, 2021):

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.

@vanous commented on GitHub (Jan 2, 2021): 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](https://codeberg.org/).
GiteaMirror commented 2025-11-02 07:01:18 -06:00
Author
Owner
Copy Link

@mibuthu commented on GitHub (Jan 4, 2021):

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.

@mibuthu commented on GitHub (Jan 4, 2021): 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.
GiteaMirror commented 2025-11-02 07:01:18 -06:00
Author
Owner
Copy Link

@gytisrepecka commented on GitHub (Jan 4, 2021):

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.

@gytisrepecka commented on GitHub (Jan 4, 2021): 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.
GiteaMirror commented 2025-11-02 07:01:19 -06:00
Author
Owner
Copy Link

@SlavekB commented on GitHub (Jan 4, 2021):

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.

@SlavekB commented on GitHub (Jan 4, 2021): 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.
GiteaMirror commented 2025-11-02 07:01:19 -06:00
Author
Owner
Copy Link

@BLumia commented on GitHub (Jan 5, 2021):

I also have this issue on my selfhosted gitea 1.13.1 instance, the issue will be gone if I switch back to 1.13.0. Either 1.13.0 or the try.gitea.io instance (with version 1.14.0+dev-506-g126c9331d) doesn't have this issue. Use 1.13.1 with a clean installed firefox browser also wont fix this issue.

I found there was a commit between 1.13.0 and 1.13.1 that most likely related to this issue, which will try not use simpleMDE editor on mobile devices for 1.13 (4f296f7436). simply revert that commit seems fixes this issue (at least on my machine).

Let me know if you need any other information.

@BLumia commented on GitHub (Jan 5, 2021): I also have this issue on my selfhosted gitea `1.13.1` instance, the issue will be gone if I switch back to `1.13.0`. Either `1.13.0` or the try.gitea.io instance (with version `1.14.0+dev-506-g126c9331d`) doesn't have this issue. Use `1.13.1` with a clean installed firefox browser also wont fix this issue. I found there was a commit between `1.13.0` and `1.13.1` that most likely related to this issue, which will try not use simpleMDE editor on mobile devices for 1.13 (4f296f7436e35af0b72c03e01b6cca46266052c8). simply revert that commit seems fixes this issue (at least on my machine). Let me know if you need any other information.
GiteaMirror commented 2025-11-02 07:01:19 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Jan 5, 2021):

I can confirm this is a bug and should be fixed on v1.13.2

@lunny commented on GitHub (Jan 5, 2021): I can confirm this is a bug and should be fixed on v1.13.2
GiteaMirror commented 2025-11-02 07:01:19 -06:00
Author
Owner
Copy Link

@miklobit commented on GitHub (Jan 9, 2021):

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.

Same with me. Fresh installation with docker image gitea/gitea:1.13.1

@miklobit commented on GitHub (Jan 9, 2021): > 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. Same with me. Fresh installation with docker image gitea/gitea:1.13.1
GiteaMirror commented 2025-11-02 07:01:20 -06:00
Author
Owner
Copy Link

@ojn commented on GitHub (Jan 20, 2021):

Same, on Gitea 1.13.1 using Firefox 84.0.2 and Chromium 87.0

@ojn commented on GitHub (Jan 20, 2021): Same, on Gitea 1.13.1 using Firefox 84.0.2 and Chromium 87.0
GiteaMirror commented 2025-11-02 07:01:20 -06:00
Author
Owner
Copy Link

@trepmag commented on GitHub (Jan 25, 2021):

Do someone have a quick turn around for 1.13.1 docker until 1.13.2?

@trepmag commented on GitHub (Jan 25, 2021): Do someone have a quick turn around for 1.13.1 docker until 1.13.2?
GiteaMirror commented 2025-11-02 07:01:20 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Jan 25, 2021):

I think we can just remove the preview tab because there is already a preview button on the toobar.

@lunny commented on GitHub (Jan 25, 2021): I think we can just remove the preview tab because there is already a preview button on the toobar.
GiteaMirror commented 2025-11-02 07:01:20 -06:00
Author
Owner
Copy Link

@jpraet commented on GitHub (Jan 28, 2021):

I think the issue is here: https://github.com/go-gitea/gitea/blob/release/v1.13/web_src/js/index.js#L1362

should be isMobile()

@jpraet commented on GitHub (Jan 28, 2021): I think the issue is here: https://github.com/go-gitea/gitea/blob/release/v1.13/web_src/js/index.js#L1362 should be `isMobile()`
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
$20
$250
$50
$500
backport/done
💎 Bounty
docs-update-needed
good first issue
hacktoberfest
issue/bounty
issue/confirmed
issue/critical
issue/duplicate
issue/needs-feedback
issue/not-a-bug
issue/regression
issue/stale
issue/workaround
lgtm/need 2
modifies/api
modifies/translation
outdated/backport/v1.18
outdated/theme/markdown
outdated/theme/timetracker
performance/bigrepo
performance/cpu
performance/memory
performance/speed
pr/breaking
proposal/accepted
proposal/rejected
pr/wip
pull-request
Mirrored from GitHub Pull Request
 reviewed/wontfix
💰 Rewarded
skip-changelog
status/blocked
topic/accessibility
topic/api
topic/authentication
topic/build
topic/code-linting
topic/commit-signing
topic/content-rendering
topic/deployment
topic/distribution
topic/federation
topic/gitea-actions
topic/issues
topic/lfs
topic/mobile
topic/moderation
topic/packages
topic/pr
topic/projects
topic/repo
topic/repo-migration
topic/security
topic/theme
topic/ui
topic/ui-interaction
topic/ux
topic/webhooks
topic/wiki
type/bug
type/deprecation
type/docs
type/enhancement
type/feature
type/miscellaneous
type/proposal
type/question
type/refactoring
type/summary
type/testing
type/upstream
No Label outdated/theme/markdown type/bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#6609
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?