Projects do not properly keep their parent project
SevenSoulsss opened this issue · 7 comments
Description
The projects do not correctly keep their parent project in the display while they are well defined in database, example, if I define the project "Hatypik" to go into the parent project "Twitch" :
it goes correctly
But when I refresh the page, it does not retain its position
I can not reproduce the bug on the demo version of vikunja, would the bug come from the stable version ?
No error on my server by putting the logs in debug mode (including in SQL queries in debug)
Vikunja Frontend Version
0.22.0
Vikunja API Version
0.22.0
Browser and version
Google Chrome 120.0.6099.131
Can you reproduce the bug on the Vikunja demo site?
No
Screenshots
No response
This started to happen on my instance only after I began to use Tasks.org via CalDAV. Even though in the project's settings the parent is correct, only visually displays above as a root project in the sidebar.
Seeing something similar. First thought it might be related to me bulk updating a couple of things in the database, but I've also seen it happen when I was sure only modifications were made through the frontend. Both frontend/api are 0.22.0.
With
in the database, I see:
in the browser.
I think it might actually be an API issue - the /projects API call returns a 0 parent_project_id for most (but not all?) projects :
For every "parent" project there is, in these cases, always max 1 sub with the correct parent_project_id. This structure did show correctly at one point, not sure what I did to get to this state (probably something with setting team permissions for a project).
Thanks for the additional details.
This definitely looks like an api issue.
This should now be fixed in 96b4f2d. Please check with the latest unstable build.
Before going crazy - did something change in the handling of logins between 22.0 and 22.1? I updated our version to test, and can't seem to log in anymore wit my browser-saved credentials? Getting a 1011 error on the /login call...
To elaborate: I'm running Vikunja on a shared server where the API port is not exposed, so I added a proxy in Apache to redirect /api calls to the backend running on its own port, until this morning that worked perfectly :-)