Problem with Leap2A import and creating custom layout option for user
Bug #1696587 reported by
Robert Lyon
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mahara |
Fix Released
|
High
|
Unassigned | ||
17.04 |
Fix Released
|
High
|
Unassigned | ||
17.10 |
Fix Released
|
High
|
Unassigned |
Bug Description
In the view constructor for 17.04+ there is some code that regenerates the view_rows_columns info if missing but that relies on the view id being known.
During the Leap2A import process the view id is not known yet - so we need the constructor to ignore fixing up view_rows_columns data at this point.
To post a comment you must log in.
Reviewed: https:/ /reviews. mahara. org/7808 /git.mahara. org/mahara/ mahara/ commit/ d85a81d05b45755 94019eb28d29aea 1086a644e4
Committed: https:/
Submitter: Aaron Wells (<email address hidden>)
Branch: master
commit d85a81d05b45755 94019eb28d29aea 1086a644e4
Author: Robert Lyon <email address hidden>
Date: Tue Jun 6 14:09:24 2017 +1200
Bug 1696587: Only replace the missing view_row_columns records if the view has an id
To avoid problem when creating a view from import when layout is
specified by creating a dummy view to create the layout needed
before the real page is created
behatnotneeded
Change-Id: I9e3fc2e9cb1432 1b8697ac37890b3 7191ff2efe1
Signed-off-by: Robert Lyon <email address hidden>