github-starred/vikunja
2
0
Fork 0
mirror of https://github.com/go-vikunja/vikunja.git synced 2026-03-22 13:05:43 -05:00
Code Issues 424 Packages Projects Releases 9 Wiki Activity

Cannot read properties of undefined when saving a task #505

New Issue
Closed
opened 2025-11-01 20:57:32 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2025-11-01 20:57:32 -05:00
Owner
Copy Link

Originally created by @Smoot178 on GitHub (May 15, 2025).

Description

When in a full screen task view (I.E. https://task.domain.com/tasks/14), making a change to the title and allowing it to save causes an error to appear. The task will save correctly though.

Steps:

  1. From the home view, click into a task.
  2. Click into the title and change it.
  3. Click out of the title box.
  4. Error appears.

As of this posting the unstable branch appears to be a lower version.

Vikunja Version

0.24.6

Browser and version

Firefox and Chrome

Can you reproduce the bug on the Vikunja demo site?

No

Screenshots

Image

Originally created by @Smoot178 on GitHub (May 15, 2025). ### Description When in a full screen task view (I.E. https://task.domain.com/tasks/14), making a change to the title and allowing it to save causes an error to appear. The task will save correctly though. Steps: 1. From the home view, click into a task. 2. Click into the title and change it. 3. Click out of the title box. 4. Error appears. As of this posting the unstable branch appears to be a lower version. ### Vikunja Version 0.24.6 ### Browser and version Firefox and Chrome ### Can you reproduce the bug on the Vikunja demo site? No ### Screenshots ![Image](https://github.com/user-attachments/assets/b4626c9e-acb0-42a1-b8be-ce04c9ac5293)
GiteaMirror commented 2025-11-01 20:57:33 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (May 16, 2025):

If it works on the demo, it's already fixed in the dev branch.

Quoting from the docs about the version mismatch:

It might happen that the unstable version does not seem to be based on the latest release. For example, the version might report v0.24.1-566-gb3040b846 when the last release is v0.25.5. This does not mean the unstable builds are outdated. Depending on the release, we only backport changes to patch releases. The important part is the commit hash at the end, which you can verify in the git repo.

@kolaente commented on GitHub (May 16, 2025): If it works on the demo, it's already fixed in the dev branch. Quoting [from the docs](https://vikunja.io/docs/versions/#unstable) about the version mismatch: > It might happen that the unstable version does not seem to be based on the latest release. For example, the version might report v0.24.1-566-gb3040b846 when the last release is v0.25.5. This does not mean the unstable builds are outdated. Depending on the release, we only backport changes to patch releases. The important part is the commit hash at the end, which you can verify [in the git repo](https://code.vikunja.io/vikunja).
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
area/api
area/caldav
area/filters
area/frontend
area/gantt
area/internal-code
area/typesense
bug
changes requested
confirmed
dependencies
enhancement
good first issue
help wanted
kind/bug
kind/feature
needs reproduction
pull-request
Mirrored from GitHub Pull Request
 question
security
support
upstream issue
waiting for reply
wontfix
No Label
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#505
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?