Gitlab issue: WYSIWYG editor doesn't save when editing wiki

Hi, I’m not sure where to reach out about a rather annoying issue in Gitlab’s WYSIWYG editor, namely: it not working.

I opened up this issue 3 months ago and no one has responded or been assigned: WYSIWYG editor doesn't save when editing wiki (#411525) · Issues · / GitLab · GitLab

It seems like a serious issue that can lead to data loss.

Has it gotten lost? How do I get someone to notice it?

What do you mean by WYSIWYG editor? When I edit a wiki page, I only see the option to change from markdown to rdoc, asciidoc, org.

I am using Gitlab 16.3.1 though. I don’t see any other option to change the editor. Maybe you can show some screenshots? I know in editing files in the project, there is the Web IDE, or by editing a single file that I now have. Prior to this I believe there was some other kind of editor, but never used it. So perhaps in Gitlab 16 and higher it got removed and could explain the lack of interest in the issue on something no longer being used.

When you click “Switch to Rich Text”

I’ve just tested what you wrote in the issue (thx for the screenshot, mine is shown in a different place and didn’t see it the first time around), I cannot replicate your problem with rich text mode and saving it. Or even switching from rich text to markdown, it still keeps all my changes.

Perhaps your issue is related to your gitlab configuration or something, or perhaps you can upgrade to the latest version to see if it fixes it.

The only other difference is I use omnibus version 16.3.1 on a VPS, so without docker. But other than that, basic gitlab.rb config.

I would suggest upgrading to see if the problem goes away, or check/verify your Gitlab configuration is OK and not causing any issues. You may need to report more info in the issue you opened and linked here. Check the log files to see if anything appears there that might be useful. You may wish to add that to your issue linked above, but I don’t see a major bug that is affecting everyone. So either something that has already been resolved in versions higher than yours, or something unique to your configuration with running Gitlab on docker.

I’m using latest Gitlab. I get the following errors in the console:

Check all your logs in the /var/log/gitlab directory in your container. The browser stuff doesn’t really suggest anything to me. Check your configuration also, and explain exactly what you have configured to run Gitlab in your container, what ports have been allowed to the container, etc.

Sounds to me, that it is something wrong with your install, especially since I can do everything on mine without problems.

What would you like me to check?

root@gitlab:/var/log/gitlab# ls -l
total 20
drwx------. 1 gitlab-prometheus git   1664 May 19  2019 alertmanager     
drwx------. 1 git               git   1918 Sep  2 15:36 gitaly           
drwx------. 1 git               git   1070 Sep  2 15:36 gitlab-kas       
drwx------. 1 git               git   1664 May 19  2019 gitlab-monitor   
drwx------. 1 git               git     88 Jul 17  2021 gitlab-pages     
drwx------. 1 git               git  82228 Sep  2 12:31 gitlab-rails     
drwx------. 1 git               git   1334 Jun 14  2019 gitlab-shell     
drwx------. 1 git               git   1772 Sep  2 15:36 gitlab-workhorse 
drwx------. 1 root              root  1664 Sep  2 15:36 logrotate        
drwx------. 1 git               git   1664 Feb  7  2019 node-exporter    
drwx------. 1 gitlab-redis      git   1664 May 19  2019 postgres-exporter
drwx------. 1 gitlab-psql       git   1664 Sep  2 15:36 postgresql       
drwx------. 1 gitlab-prometheus git   1664 May 19  2019 prometheus       
drwx------. 1 git               git   1724 Sep  2 15:36 puma             
drwxr-sr-x. 1 root              root  3360 Sep  2 15:36 reconfigure      
drwx------. 1 gitlab-redis      git   1772 Sep  2 15:36 redis            
drwx------. 1 git               git   1664 May 19  2019 redis-exporter   
drwx------. 1 git               git   1772 Sep  2 15:36 sidekiq
drwxr-sr-x. 1 root              root   616 Sep  2 15:36 sshd
drwx------. 1 git               git   4580 Jun  8  2020 unicorn

I have it configured from docker-compose.yml:

      context: ./services/gitlab
        - VERSION=${GITLAB_VERSION:-9.3.6-ce.0}
    hostname: $GITLAB_HOSTNAME
        external_url 'https://${GITLAB_HOSTNAME}'
        gitlab_rails['time_zone'] = 'US/Pacific'
        gitlab_rails['lfs_enabled'] = true
        gitlab_rails['smtp_enable'] = false
        gitlab_rails['gitlab_email_from'] = 'gitlab@domain'
        gitlab_rails['gitlab_email_display_name'] = 'Gitlab'
        gitlab_rails['gitlab_email_reply_to'] = ''
        puma['enable'] = true
        puma['worker_processes'] = 2
        nginx['enable'] = false
        gitlab_rails['trusted_proxies'] = [ '', '${NGINX_LISTEN_IP}', '', '' ]
        gitlab_workhorse['listen_network'] = "tcp"
        gitlab_workhorse['listen_addr'] = ""
        node_exporter['enable'] = false
        prometheus_monitoring['enable'] = false

The container starts the command /assets/wrapper.

I might have had some permissions related issues during a migration that could be affecting this, but I ran update-permissions from within the container.