New block order not set up when upgrading via CLI from 1.10

Bug #1430111 reported by Aaron Wells on 2015-03-10
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mahara
High
Son Nguyen

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).

Aaron Wells (u-aaronw) wrote :

Tagged with "high" priority not because it's a huge problem, but because we need to fix it before 15.04.0 (since it'll be a UI change).

Changed in mahara:
milestone: none → 15.04.0
status: New → Confirmed
importance: Undecided → High
Son Nguyen (ngson2000) on 2015-03-23
Changed in mahara:
assignee: nobody → Son Nguyen (ngson2000)
Son Nguyen (ngson2000) on 2015-03-24
Changed in mahara:
status: Confirmed → In Progress
Son Nguyen (ngson2000) wrote :

I did not see any problem of block order in the "General" category. However, I noticed the sortorder of blocks in the table "blocktype_installed_category" are incorrect.

Aaron Wells (u-aaronw) on 2015-03-26
description: updated
summary: - New block order not set up when upgrading via CLI
+ New block order not set up when upgrading via CLI from 1.10
Mahara Bot (dev-mahara) wrote :

Patch for "master" branch: https://reviews.mahara.org/4474

Reviewed: https://reviews.mahara.org/4474
Committed: http://gitorious.org/mahara/mahara/commit/edaf831d6a025b90a26053470cb5d9a5cbd8ce78
Submitter: Robert Lyon (<email address hidden>)
Branch: master

commit edaf831d6a025b90a26053470cb5d9a5cbd8ce78
Author: Aaron Wells <email address hidden>
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

Robert Lyon (robertl-9) on 2015-03-30
Changed in mahara:
status: In Progress → Fix Committed

Reviewed: https://reviews.mahara.org/4525
Committed: http://gitorious.org/mahara/mahara/commit/5d65649c2af1a09258bb17f64d97e5851e71beae
Submitter: Robert Lyon (<email address hidden>)
Branch: 15.04_STABLE

commit 5d65649c2af1a09258bb17f64d97e5851e71beae
Author: Aaron Wells <email address hidden>
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

Robert Lyon (robertl-9) on 2015-04-17
Changed in mahara:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers