mahara-contributors team mailing list archive
-
mahara-contributors team
-
Mailing list archive
-
Message #25188
[Bug 1430111] A change has been merged
Reviewed: https://reviews.mahara.org/4525
Committed: http://gitorious.org/mahara/mahara/commit/5d65649c2af1a09258bb17f64d97e5851e71beae
Submitter: Robert Lyon (robertl@xxxxxxxxxxxxxxx)
Branch: 15.04_STABLE
commit 5d65649c2af1a09258bb17f64d97e5851e71beae
Author: Aaron Wells <aaronw@xxxxxxxxxxxxxxx>
Date: Thu Mar 26 16:12:19 2015 +1300
Automatically clear insert_record()'s table column cache
Bug 1430111. When the table structure changes, automatically
clear the cache for that table in insert_record().
Change-Id: I0612755bd5fa6646a26ff51d1d2844df211be61d
--
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/1430111
Title:
New block order not set up when upgrading via CLI from 1.10
Status in Mahara ePortfolio:
Fix Committed
Bug description:
To replicate:
1. Install Mahara 1.10
2. Upgrade to Mahara 15.04dev using the CLI upgrade script
3. Edit your dashboard page (or examine the contents of the
blocktype_installed_category table in the DB)
Expected result: The blocks in the "General" category should be
ordered starting with: profileinfo, socialprofile, wall,
entireresume...
Actual result: The blocks in the "General" category are ordered
starting with: creativecommons, inbox, navigation, latest pages....
(And in the database, all the blocks have sortorder 100,000).
To manage notifications about this bug go to:
https://bugs.launchpad.net/mahara/+bug/1430111/+subscriptions
References