Ensure that the database update will be processed anyway
This commit is contained in:
parent
9f11476ca0
commit
ee300a7db6
|
@ -36,11 +36,10 @@ class Update
|
||||||
die('You try to update from a version prior to database version 1170. The direct upgrade path is not supported. Please update to version 3.5.4 before updating to this version.');
|
die('You try to update from a version prior to database version 1170. The direct upgrade path is not supported. Please update to version 3.5.4 before updating to this version.');
|
||||||
}
|
}
|
||||||
|
|
||||||
if ($build < DB_UPDATE_VERSION) {
|
// Calling the database update directly via the worker enables us to perform database changes to the workerqueue table itself.
|
||||||
// When we cannot execute the database update via the worker, we will do it directly
|
// This is a fallback, since normally the database update will be performed by a worker job (which doesn't work for changes to the "workerqueue" table itself).
|
||||||
if (!Worker::add(PRIORITY_CRITICAL, 'DBUpdate') && $via_worker) {
|
if (($build < DB_UPDATE_VERSION) && $via_worker) {
|
||||||
self::run($basePath);
|
self::run($basePath);
|
||||||
}
|
|
||||||
}
|
}
|
||||||
}
|
}
|
||||||
|
|
||||||
|
|
Loading…
Reference in a new issue