From 205f330f8a68bb4210d16d5985327a7106ddcdd7 Mon Sep 17 00:00:00 2001 From: kolaente Date: Tue, 13 Feb 2024 22:21:59 +0100 Subject: [PATCH] fix(migration): make sure to correctly check if a migration was already running 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. --- .../src/views/migrate/MigrationHandler.vue | 23 ++++++++++--------- pkg/modules/migration/handler/handler.go | 6 ++--- 2 files changed, 15 insertions(+), 14 deletions(-) diff --git a/frontend/src/views/migrate/MigrationHandler.vue b/frontend/src/views/migrate/MigrationHandler.vue index d9ec6febc0..d8d8d0f563 100644 --- a/frontend/src/views/migrate/MigrationHandler.vue +++ b/frontend/src/views/migrate/MigrationHandler.vue @@ -3,7 +3,7 @@

{{ $t('migrate.titleService', {name: migrator.name}) }}

{{ $t('migrate.descriptionDo') }}

-