Commit Graph

7 Commits

Author SHA1 Message Date
0b9ef27d04
fix(migration): show correct message after starting a migration
Some checks failed
continuous-integration/drone/push Build is failing
Related to https://github.com/go-vikunja/vikunja/issues/238
2024-04-07 15:11:59 +02:00
89b01e86bc
fix(projects): load all projects when first opening Vikunja 2024-03-02 13:43:04 +01:00
178cd8c392
fix: open external migration service in current tab
Some checks failed
continuous-integration/drone/push Build is failing
2024-03-02 11:22:03 +01:00
997fb6bc54
fix(migration): show correct help message when a migration was started 2024-02-27 16:36:18 +01:00
cc5f48eb74
fix: lint
All checks were successful
continuous-integration/drone/push Build is passing
2024-02-14 14:13:17 +01:00
205f330f8a
fix(migration): make sure to correctly check if a migration was already running
Some checks reported errors
continuous-integration/drone/push Build was killed
This change fixes a bug where Vikunja would not correctly check if a migration was already running. That meant it was not possible for users who had never before migrated anything to start a migration, because Vikunja assumed they already had a migration running for them.
This state was neither properly reflected in the frontend, which is now fixed as well.
2024-02-13 22:21:59 +01:00
fc4676315d
chore: move frontend files 2024-02-07 14:56:56 +01:00