github-starred/vikunja
2
0
Fork 0
mirror of https://github.com/go-vikunja/vikunja.git synced 2026-07-15 22:32:29 -05:00
Code Issues 690 Packages Projects Releases 11 Wiki Activity

[GH-ISSUE #126] Projects do not properly keep their parent project #5974

New Issue
Closed
opened 2026-04-20 16:26:57 -05:00 by GiteaMirror · 7 comments
GiteaMirror commented 2026-04-20 16:26:57 -05:00
Owner
Copy Link

Originally created by @SevenSoulsss on GitHub (Jan 4, 2024).
Original GitHub issue: https://github.com/go-vikunja/vikunja/issues/126

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" :
image

it goes correctly
image2

But when I refresh the page, it does not retain its position
image3

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

Originally created by @SevenSoulsss on GitHub (Jan 4, 2024). Original GitHub issue: https://github.com/go-vikunja/vikunja/issues/126 ### 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" : ![image](https://github.com/go-vikunja/frontend/assets/46326574/9f5712f6-2f22-4da3-b244-be05a36c6a6e) it goes correctly ![image2](https://github.com/go-vikunja/frontend/assets/46326574/31ad5243-918d-40c3-b776-8b8887aed344) But when I refresh the page, it does not retain its position ![image3](https://github.com/go-vikunja/frontend/assets/46326574/a9ab68a2-02c3-4a47-9bb4-c1598937e8a8) 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_
GiteaMirror added the bug label 2026-04-20 16:26:57 -05:00
GiteaMirror commented 2026-04-20 16:26:59 -05:00
Author
Owner
Copy Link

@vladimiroff commented on GitHub (Jan 10, 2024):

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.

<!-- gh-comment-id:1934161576 --> @vladimiroff commented on GitHub (Jan 10, 2024): 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.
GiteaMirror commented 2026-04-20 16:26:59 -05:00
Author
Owner
Copy Link

@ozuzo commented on GitHub (Jan 15, 2024):

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
image
in the database, I see:
image
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 :
image

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).

<!-- gh-comment-id:1934161585 --> @ozuzo commented on GitHub (Jan 15, 2024): 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 ![image](https://github.com/go-vikunja/frontend/assets/5175516/e2bf1e08-cc78-4cc4-bc38-4fff5bb5a723) in the database, I see: ![image](https://github.com/go-vikunja/frontend/assets/5175516/42483b89-795e-4751-8c47-2d88b8f098de) 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 : ![image](https://github.com/go-vikunja/frontend/assets/5175516/aeb9406a-a38e-4411-a396-639d3cc364d3) 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).
GiteaMirror commented 2026-04-20 16:26:59 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Jan 15, 2024):

Thanks for the additional details.
This definitely looks like an api issue.

<!-- gh-comment-id:1934161593 --> @kolaente commented on GitHub (Jan 15, 2024): Thanks for the additional details. This definitely looks like an api issue.
GiteaMirror commented 2026-04-20 16:27:00 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Jan 28, 2024):

This should now be fixed in 96b4f2d1db. Please check with the latest unstable build.

<!-- gh-comment-id:1934161600 --> @kolaente commented on GitHub (Jan 28, 2024): This should now be fixed in https://github.com/go-vikunja/api/commit/96b4f2d1dbd6442fab0df2906d5640fc7193ba2e. Please check with the latest unstable build.
GiteaMirror commented 2026-04-20 16:27:00 -05:00
Author
Owner
Copy Link

@ozuzo commented on GitHub (Feb 1, 2024):

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 :-)

<!-- gh-comment-id:1934161606 --> @ozuzo commented on GitHub (Feb 1, 2024): 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 :-)
GiteaMirror commented 2026-04-20 16:27:01 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Feb 1, 2024):

@ozuzo No changes I can recall from the top of my head. Please open a new issue with this.

<!-- gh-comment-id:1934161609 --> @kolaente commented on GitHub (Feb 1, 2024): @ozuzo No changes I can recall from the top of my head. Please open a new issue with this.
GiteaMirror commented 2026-04-20 16:27:02 -05:00
Author
Owner
Copy Link

@ozuzo commented on GitHub (Feb 1, 2024):

Done, API go-vikunja/vikunja#144

<!-- gh-comment-id:1934161616 --> @ozuzo commented on GitHub (Feb 1, 2024): Done, API go-vikunja/vikunja#144
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
area/api
area/attachments
area/auth
area/avatars
area/backup-restore
area/caldav
area/calendar-view
area/comments
area/config
area/database
area/desktop
area/docker
area/email
area/favorites
area/filters
area/frontend
area/gantt
area/i18n
area/import-export
area/internal-code
area/kanban
area/labels
area/list-view
area/mobile
area/notifications
area/permissions
area/projects
area/pwa
area/recurring-tasks
area/reminders
area/search
area/shortcuts
area/subtasks
area/sync
area/table-view
area/task-editor
area/task-metadata
area/task-relations
area/teams
area/theming
area/time-tracking
area/typesense
area/views
area/webhooks
bug
changes requested
concern/accessibility
concern/performance
concern/regression
concern/ux
confirmed
db/mysql
dependencies
enhancement
good first issue
help wanted
integration/inbound
integration/outbound
kind/bug
kind/feature
needs reproduction
pull-request
Mirrored from GitHub Pull Request
 question
security
support
upstream issue
waiting for reply
wontfix
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/vikunja#5974
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?