Issue

JSON files can be added to cards as attachments, but they are empty when downloaded from a card.

Server Setup Information

• Did you test in newest Wekan?: 5.90
• Did you configure root-url correctly so Wekan cards open correctly? yes
• Operating System: Ubuntu 20.04
• Deployment Method: snap
• Http frontend if any: Apache
• What webbrowser version are you using? Firefox (reproducible in Brave too)

Problem description

Reproduction Steps

1. Have a JSON file, such as the example from Wikipedia. Name it example.json.
2. Open a card in Wekan.
3. Select + from the Attachments section.
4. Select ”Computer” from the popup.
5. Select example.json.
6. With the JSON file now attached to the card, select to ”Download” it.
7. Open the downloaded JSON file.

What I expect to happen

For the downloaded file contents to match the uploaded file.

What happens instead

The file is empty.

Logs

Nothing in either the browser console nor snap logs when the issue is triggered.

Other info

• Deleting the attachment seems to work.
• The issue can be worked around by renaming the JSON file prior to uploading to have a .txt extension instead of (or in addition to) .json.

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.

Issue

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.

Comments can no longer be updated, as pressing the Edit button just reverts the comment back to what it was prior to editing. Both rich and non-rich editor are affected.

Server Setup Information:

• Wekan version: 3.89
• Operating System: Ubuntu 16.04
• Deployment Method: snap
• Http frontend if any: Apache
• Web browser: both Chrome and Firefox affected

Steps to reproduce

1. Add a comment to a card.
2. Click the edit link to start editing the comment, make some changes.
3. Click the Edit button.

What I expect to happen
For the comment to reflect the changes made when editing.

What happens instead
The comment content reverts back to what it was prior to editing.

Logs
Nothing in browser console log, nothing related in server log.

Problem description
Using ctrl-v to paste content into a comment causes the view to scroll back horizontally so that if the card was already at the right edge of the view, it seemingly pops out of view. This happens when using Firefox; Chrome seems unaffected.

I’m currently unable to test whether the non-rich editor is affected due to #2967, and also, as I was exclusively using non-rich editor prior to this, I can’t say if this occurred with the 3.85 refresh or whether it was here with the rich editor even before.

Server Setup Information

• Wekan version: 3.85
• Operating System: Ubuntu 16.04 (19.10 in another test VM)
• Deployment Method: snap
• What webbrowser version? Firefox 74.0, Chrome 80.0.3987.149

Logs contain nothing related to this AFAICT.

Steps to reproduce

1. Copy something to clipboard
2. Have a board with enough lists to fill the view horizontally, or contract the browser window to have one list at the right edge
3. Open a card from the rightmost list
4. Select the comment field, press ctrl-v

Demo
Here I’m first typing something, then pasting below it (using ctrl-v) to cause the unwanted scrolling to occur.

After today’s snap refresh to 3.85, rich editor is used for comments despite richer-card-comment-editor being set to false. Yesterday this was still working, and I didn’t change the settings, so it’s something to do with the latest refresh.

Server Setup Information:

• Wekan version: 3.85
• Operating System: Ubuntu 16.04 (19.10 in another test VM)
• Deployment Method: snap
• What webbrowser version? Firefox 74.0, Chrome 80.0.3987.149

Problem description:
(Nothing related in any logs)

I think I’ve (accidentally) found a reliable way to reproduce this:

1. Have a card with a checklist
2. From the card’s hamburger menu, select More -> Delete, but don’t touch the (”Delete card?”) confirmation prompt!
3. With the card deletion confirmation prompt still visible, delete the checklist (choose Delete from the checklist title, then confirm the checklist deletion)
4. Now select Delete from the (still lingering) card deletion prompt

Boom! The card (and the board) is now undeletable.

When a checklist item is in edit mode (through the specific steps below), selecting another item for editing does not take the previous item out of edit mode, and upon selecting a third item (or pressing enter) causes the second item to be overwritten by whatever content is in the first selected item.

Server Setup Information:

• Wekan version: 2.74
• Operating System: Ubuntu 16.04
• Deployment Method: snap (stable)
• Http frontend if any: Apache 2.4
• ROOT_URL environment variable: https://my-domain.com/kan

Problem description:

Steps to reproduce

1. Have a card with a checklist with 4 (or more) items with contents A, B, C, D (and so on):
2. Select item A with LBM
3. Select item B with LBM
4. Select item C with LBM
5. Select item D with LBM

What happens
At step 4, when C opens for editing, B remains in edit mode. At step 5, contents of C are overwritten by contents of B (that is, ”C” becomes a ”B”).

What I expect to happen
At step 4, for B to leave edit mode, and at step 5, the contents of C to remain as they are.

Other notes

• Reproducible in both Chrome and Firefox.
• Curiously, this does not seem to affect the firstly selected item: in step 3 above, A leaves edit mode correctly and thus B doesn’t get overwritten by the contents of item A in step 4.
• At step 5, instead of selecting item D, pressing enter has the same effect.

Browser console output
empty

snap logs wekan.wekan
nothing related

Looks like this is exacerbated by Wekan issue #1911, as it turns out 99,8 % of the log is about the socket connection (since 2018-09-15):

root@battra:~# grep -c -v "received client metadata from anonymous unix socket" /var/snap/wekan/common/mongodb.log
23426
root@battra:~# grep -c "received client metadata from anonymous unix socket" /var/snap/wekan/common/mongodb.log
10970660

Log rotation would still be nice, but nowhere near as critical if less than one percent of the current logging was produced (a few megabytes per year in my setup here, if I extrapolated correctly).

I noticed my mongodb.log has grown pretty large:

root@battra:~# ls -lh /var/snap/wekan/common/mongodb.log
-rw-r--r-- 1 root root 3,1G touko  4 21:14 /var/snap/wekan/common/mongodb.log

The first lines in the log are timestamped 2018-03-02T16:39:44.754+0200.

Should the log rotate automatically, but doesn’t for some reason? Alternatively, should I truncate it manually (and if so, how)? I have no use for the logs apart from the occasional bug reports here, so even losing all of it is fine.

There are no related mongodb settings keys AFAICS. (And sorry if this is unrelated to snap packaging, it was just a guess on my part.)

Server Setup Information:

• Wekan version: 2.65
• Operating System: Ubuntu 16.04
• Deployment Method: snap
• Http frontend if any: Apache 2.4

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.