-
-
Notifications
You must be signed in to change notification settings - Fork 2.9k
Wekan board cards disappear #2249
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
Comments
are these subtask boards by any chance? |
@rjevnikar Hi, all board who disappeared contains subtasks. I can reproduce the problem if i create a new board and set up the current board as subtask boards. |
same/similar to #2247. |
Hi, I am also having a similar issue, but not with cards, with boards. I am using wekan on ubuntu server set up with snap. when I enter the main page, board list appears and disappears after .5 seconds. If I can catch to click, I can enter the board without any issue. |
I also have this issue. When loading the home page/board overview one specific board is shown for about half a second and then disappears. |
In Wekan v2.43 is new feature Hide Subtask boards from All Boards. I did get that feature request from Wekan users. After implementing it, I did get this bug report that Subtask boards are hidden. Nice. Well, how it should work? |
if a subtask board is the one you create by adding some subtask to a board, I also think they should be hidden. But this board disappearing problem happens on my main board. |
Well, that's the point. Editing subtasks is possible in cards, and currently Subtasks are added to new Subtasks boards. But Subtasks were hidden from All Boards, because some did think it is a bug to see all the clutter from all the Subtask boards. |
Moved to #641 |
Also had the problem that this board was not actually a subtask board. But maybe it was created as one, I can neither confirm or deny this. ;-) For a Solution/Workaround: You can fix this issue by running a query against the MongoDB database removing the subtask link. If you are running it via snap connect to mongodb on port 27019 on the machine running the board: Use the wekan database: And remove the subtask link: The commit changing the behavior/causing this issue is: |
thanks @fvalka ! that solved my issue |
Hello friends,
|
Please wait that Wekan v2.46 is available at https://snapcraft.io/wekan or https://quay.io/wekan/wekan and then upgrade. Snap is upgraded automatically or manually with |
Confirmed. Thanks! |
Dear @xet7 |
Server Setup Information:
Did you test in newest Wekan?: yes
For new Wekan install, did you configure root-url correctly https://github.com/wekan/wekan/wiki/Settings ? yes
Wekan version: 2.45.0
Operating System: Ubuntu 18.04.2 LTS
Deployment Method(snap/docker/sandstorm/mongodb bundle/source): snap
Http frontend if any (Caddy, Nginx, Apache, see config examples from Wekan GitHub wiki first): Nginx
Node Version: 8.15.1
MongoDB Version:
ROOT_URL environment variable http(s)://(subdomain).example.com(/suburl):
Problem description:
While loading the page, some wekan board cards disappear after 0.5 sec. Not all only the half. I've tested this with safari and chrome browser. If i mark one of them as favorit i still see it in the top bar and i'am able to open the board.
Explain steps how to reproduce
I reload the main (index) page and can see all card's for a short moment.
2019-03-12T05:08:39Z wekan.wekan[15018]: Note: you are using a pure-JavaScript implementation of bcrypt.
2019-03-12T05:08:39Z wekan.wekan[15018]: While this implementation will work correctly, it is known to be
2019-03-12T05:08:39Z wekan.wekan[15018]: approximately three times slower than the native implementation.
2019-03-12T05:08:39Z wekan.wekan[15018]: In order to use the native implementation instead, run
2019-03-12T05:08:39Z wekan.wekan[15018]: meteor npm install --save bcrypt
2019-03-12T05:08:39Z wekan.wekan[15018]: in the root directory of your application.
2019-03-12T05:08:40Z wekan.wekan[15018]: Presence started serverId=jG9KhtKq5iB9y8SNm
2019-03-12T05:08:41Z wekan.wekan[15018]: > Starting fix-circular-reference_ migration.
2019-03-12T05:08:41Z wekan.wekan[15018]: > Finishing fix-circular-reference_ migration.
2019-03-12T05:08:41Z wekan.wekan[15018]: Kadira: completed instrumenting the app
The text was updated successfully, but these errors were encountered: