mahara-contributors team mailing list archive

[Mahara Bot <1788710@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://reviews.mahara.org/9088
Committed: https://git.mahara.org/mahara/mahara/commit/a6c082d35b5e3e0950d7c92a34b05c805561624a
Submitter: Cecilia Vela Gurovic (ceciliavg@xxxxxxxxxxxxxxx)
Branch:    master

commit a6c082d35b5e3e0950d7c92a34b05c805561624a
Author: Robert Lyon <robertl@xxxxxxxxxxxxxxx>
Date:   Fri Aug 24 09:16:04 2018 +1200

Bug 1788710: Altering db upgrade step to avoid unrelated 'tags' error

When using normal commit() method the block tries to do some artefact
related checks as well, which are not needed.

We will save the block configdata back directly instead

behatnotneeded

Change-Id: I0defae0de6b5f97d75f79c1d9059dadb0a64c686
Signed-off-by: Robert Lyon <robertl@xxxxxxxxxxxxxxx>

-- 
You received this bug notification because you are a member of Mahara
Contributors, which is subscribed to Mahara.
Matching subscriptions: Subscription for all Mahara Contributors -- please ask on #mahara-dev or mahara.org forum before editing or unsubscribing it!
https://bugs.launchpad.net/bugs/1788710

Title:
  DB upgrade problem with plans from 17.04

Status in Mahara:
  Fix Committed
Status in Mahara 18.10 series:
  Fix Committed

Bug description:
  We now require people to upgrade to at least 17.04 before upgrading to
  18.10 to avoid upgrade problems.

  However, there is still a problem with an alteration of the Plans
  block configuration.

  We should just do a direct db update rather than via the commit method
  as the change is only to the structure of the configdata (artefactid
  => artefactids) rather than actually changing details the block
  itself.

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