Avainsanana Apache

Description textbox unfocused after click, have to click twice to start editing

9. marraskuuta 2020 klo 16.14
Sijainti: Vianhallintajärjestelmät: Github
Avainsanat: Apache, Chrome, Firefox, MongoDB, Snap, Ubuntu, Wayland, Wekan

Since recently, editing the description takes two clicks instead of just one. The first click turns the content into a textbox, but it remains unfocused until I click it again.


Server Setup Information:

  • Did you test in newest Wekan?: yes
  • For new Wekan install, did you configure root-url correctly so Wekan cards open correctly? yes
  • Wekan version: 4.49
  • Meteor version: 2.0-beta.4
  • Node version: 12.19.0
  • MongoDB version: 3.2.22
  • Operating System: Ubuntu 20.04
  • Deployment Method: snap
  • Http frontend if any: Apache
  • What webbrowser version are you using? Both Firefox 82.0.2 and Chrome 86.0.4240.183 equally affected.
  • If using Snap, what does show command sudo snap logs wekan.wekan? nothing

Problem description:
Sorry for not providing animation, as peek doesn’t support Wayland. The steps below should be sufficient though.

Steps to reproduce:

  1. Open a card
  2. Click on the description once

What I expect to happen:
For the description to have focus (i.e. cursor, to be able to type)

What happens instead:
The description textbox remains unfocused and I can not type into it

Console log contents

site.webmanifest:1 GET https://my-domain.com/site.webmanifest 404 (Not Found)
site.webmanifest:1 Manifest: Line: 1, column: 1, Syntax error.
A bad HTTP response code (404) was received when fetching the script.
mZLgcqMWYXM4o7dmL:1 Uncaught (in promise) TypeError: Failed to register a ServiceWorker for scope ('https://my-domain.com/') with script ('https://my-domain.com/pwa-service-worker.js'): A bad HTTP response code (404) was received when fetching the script.

It seems to refer to to paths in the domain root, whereas my root-url has the path https://my-domain.com/kan. Not sure if that’s related to the issue or not.

Vastaa viestiin sen kontekstissa (Github)

As a workaround, copying the logos and manifest to the root seems to work

16. joulukuuta 2018 klo 9.16
Sijainti: Vianhallintajärjestelmät: Github
Avainsanat: Apache, Snap, Wekan

As a workaround, copying the icons and manifest from public to domain root seems to work (with Wekan snap running behind Apache here). As the files have a wekan- prefix, collisions shouldn’t be an issue. Naturally, this solution does require write access to the domain root directory.

Vastaa viestiin sen kontekstissa (Github)

Use a2ensite instead of ln -s to enable site

2. lokakuuta 2018 klo 16.01
Sijainti: Vianhallintajärjestelmät: Github
Avainsanat: Apache, Debian, Nextcloud

Replace instruction using ln -s to enable Apache site to use a2ensite instead in Debian and derivatives. Closes #884.

Vastaa viestiin sen kontekstissa (Github)

Debian derivatives installation example uses `ln -s` instead of `a2ensite`

30. syyskuuta 2018 klo 13.43
Sijainti: Vianhallintajärjestelmät: Github
Avainsanat: Apache, Debian, Nextcloud, Ubuntu

Under Apache Web server configuration, there’s a prompt to create a symlink to enable the newly created site:

ln -s /etc/apache2/sites-available/nextcloud.conf /etc/apache2/sites-enabled/nextcloud.conf

As the instructions in this section are written for Debian, Ubuntu, and their derivatives, a2ensite should be used instead:

a2ensite nextcloud.conf

The commands are currently functionally equivalent (AFAIK), but should this change sometime, the latter would be more future proof, besides being much shorter and easier to type.

Additionally, immediately following the ln -s there is a section about Additional Apache configurations, which correctly instructs the use of a2enmod to create the symlinks. Replacing ln -s with a2ensitewould thus harmonize the two sections.

Vastaa viestiin sen kontekstissa (Github)

Set DirectoryIndex disabled for the Gitlab directory to fix 404

13. syyskuuta 2017 klo 17.40
Sijainti: Vianhallintajärjestelmät: Gitlab
Avainsanat: Apache, Gitlab

With Gitlab 9.5.4-ce.0 and Apache 2.4.18, I had to set `DirectoryIndex disabled` for the Gitlab directory (in the vhost configuration) to fix this when using RewriteRules. (I’ve now switched to using ProxyPass instead.)

Vastaa viestiin sen kontekstissa (Gitlab)

My installation is served over https too

20. heinäkuuta 2016 klo 20.36
Sijainti: Keskustelupalstat: Nextcloud
Avainsanat: Apache

Forgot to mention that my installation is served over https too, on Apache. But for me there are no SSL errors to be seen either.

Vastaa viestiin sen kontekstissa (Nextcloud)