mahara-contributors team mailing list archive

[Robert Lyon <1946301@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

There was a fix in the db/upgrade.php file to turn the setting of
'collection_rollover' cron job to 'unlock_collections_by_rollover'.

And part of this was to add in the 'unlock_collections_by_rollover' cron
if the  'collection_rollover' didn't exist.

But this causes upgrade problems if we are on the latest 21.04 release
and try to upgrade to 21.10 as it tries to add
'unlock_collections_by_rollover' for a second time.

We need to have it so it checks for both
'unlock_collections_by_rollover' and 'collection_rollover' and if both
are missing to add in the new cron

** Affects: mahara
     Importance: High
         Status: In Progress

** Changed in: mahara
    Milestone: None => 21.10rc2

** Changed in: mahara
   Importance: Undecided => High

** Changed in: mahara
       Status: New => In Progress

-- 
You received this bug notification because you are a member of Mahara
Contributors, which is subscribed to Mahara.
Matching subscriptions: mahara-contributors
https://bugs.launchpad.net/bugs/1946301

Title:
  Upgrade issue with unlock_collections_by_rollover

Status in Mahara:
  In Progress

Bug description:
  There was a fix in the db/upgrade.php file to turn the setting of
  'collection_rollover' cron job to 'unlock_collections_by_rollover'.

  And part of this was to add in the 'unlock_collections_by_rollover'
  cron if the  'collection_rollover' didn't exist.

  But this causes upgrade problems if we are on the latest 21.04 release
  and try to upgrade to 21.10 as it tries to add
  'unlock_collections_by_rollover' for a second time.

  We need to have it so it checks for both
  'unlock_collections_by_rollover' and 'collection_rollover' and if both
  are missing to add in the new cron

To manage notifications about this bug go to:
https://bugs.launchpad.net/mahara/+bug/1946301/+subscriptions