Skip to content

Commit

Permalink
pkp#101 Attempts to re-run the migrations whenever the plugin is goin…
Browse files Browse the repository at this point in the history
…g to run a sync
  • Loading branch information
jonasraoni committed Feb 1, 2025
1 parent 0b3d4f2 commit 3bd1d8d
Showing 1 changed file with 4 additions and 0 deletions.
4 changes: 4 additions & 0 deletions classes/tasks/Depositor.php
Original file line number Diff line number Diff line change
Expand Up @@ -20,6 +20,7 @@
use APP\plugins\generic\pln\classes\deposit\Repository as DepositRepository;
use APP\plugins\generic\pln\classes\depositObject\Repository as DepositObjectRepository;
use APP\plugins\generic\pln\classes\DepositPackage;
use APP\plugins\generic\pln\classes\migration\install\SchemaMigration;
use APP\plugins\generic\pln\PlnPlugin;
use Exception;
use PKP\db\DAORegistry;
Expand Down Expand Up @@ -56,6 +57,9 @@ public function executeActions(): bool
{
$this->addExecutionLogEntry('PKP Preservation Network Processor', ScheduledTaskHelper::SCHEDULED_TASK_MESSAGE_TYPE_NOTICE);

// @todo Re-running the plugin migrations shouldn't be needed. But users are having issues, so better to keep it until we can ensure plugin migrations are executed properly
(new SchemaMigration())->up();

/** @var JournalDAO */
$journalDao = DAORegistry::getDAO('JournalDAO');
// For all journals
Expand Down

0 comments on commit 3bd1d8d

Please sign in to comment.