TypeError when opening specific projects #2246
Loading…
x
Reference in New Issue
Block a user
No description provided.
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?
Description
When opening specific projects from the https://try.vikunja.io/projects page, the site hangs and throws below error in the console endlessly:
runtime-core.esm-bundler.js:195 [Vue warn]: Error in https://vuejs.org/error-reference/#runtime-1: "TypeError: Cannot read properties of undefined (reading 'length')" (found in <Anonymous>)
This only happens with projects that have a background image and at least one task.
Steps to reproduce:
Vikunja Version
v0.23.0+438-f0d695e789
Browser and version
Google Chrome 119.0.6045.160 (Official Build) (64-Bit) (cohort: Stable)
Can you reproduce the bug on the Vikunja demo site?
Yes
Screenshots
Maybe related to https://github.com/go-vikunja/vikunja/issues/233
I couldn't exactly reproduce it with the same error message, however I was able to trigger an error when setting a background image on a new project. This should be fixed with
8bee5aa806
- please check with the next unstable build if that fixes your issue as well (I was not able to reproduce it with that commit anymore, but it might have been a different issue I fixed)Unfortunately that doesn't fix it. I've fixed it for me with this: https://kolaente.dev/benimautner/vikunja/src/branch/fix_redirecttofirstviewifnecessary
I've never used Vue before, so I might be lacking some basic understanding about the inner workings of the framework. Just let me know if I should change anything. If you think it's fine I can create a pull request.
I guess this is the same as https://community.vikunja.io/t/vikunja-freezes/2246/5 ?
This time I was able to reproduce it properly, pushed a fix in
9eb19e0362
. Please check with the next unstable build (ready in ~45min, also on try) if the problem went away.There was nothing wrong with the fix you proposed, I've just decided to add the fallback at the root, rather than in the template :)
Perfect, it now works on try.
Yeah no, that fix makes a lot more sense :)
I don't know whether you want to keep this open until you release the fix, but it's fixed now, so feel free to close the issue!