Frontend hangs when opening a task (process crash/eternal loop) about vikunja

[simeoncode]

It was a typo. I meant :unstable, of course.

[kolaente]

If you open the dev tools, are there any errors logged in the console when you open the task?

[devikrishnamk0123]

we have also faced the same issue.
The following are the steps used to reproduce the issue

• Ran the application in docker using the unstable version of the image.
• Imported a board from trello as user1
• Logged in as user1
• From the imported board, user1 was able to view all tasks, click on a particular task and view it.
• Logged in as user2.
• From the imported board, the frontend hangs when user2 clicks on a particular task.

[simeoncode]

If you open the dev tools, are there any errors logged in the console when you open the task?

[kolaente]

I think I've commented this elsewhere already, but can you reproduce this with all tasks or only a specific task? Which attributes does the task have? Are you able to reproduce this on try?

[devikrishnamk0123]

If you open the dev tools, are there any errors logged in the console when you open the task?

No errors are shown in the console

[devikrishnamk0123]

I think I've commented this elsewhere already, but can you reproduce this with all tasks or only a specific task? Which attributes does the task have? Are you able to reproduce this on try?

There is no option to import from trello in try.

[kolaente]

Are you able to reproduce this when the project has a background vs when it does not have one?

Might be related to https://kolaente.dev/vikunja/vikunja/issues/2246

[kolaente]

This might be fixed in c1d06c5. Please check again with the latest unstable build or on try.

I think the problem you're describing only happened when opening a task which belongs to a shared child project where the current user does not have access to the parent project (if that's the case, the project the task belongs to will not show up in the sidebar menu). It then couldn't load the project for display in the task detail page. This specific bug is now fixed, so please check if it works with the latest unstable build.

[kolaente]

I've pushed a potential fix for this in 0bc9a67. Can you check with the latest unstable build if the problem still exists?

[simeoncode]

I've pulled :latest:unstable and according to some clicking around, the issue is now resolved 👍

[kolaente]

latest is the last release, which does not have the fix (nor the bug). You'll want to check with unstable. Check out the docs for more info about the versions.