Leap2a support for pages with custom flexible layouts
Bug #1231205 reported by
Aaron Wells
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Mahara |
Fix Released
|
Medium
|
Aaron Wells | ||
Bug Description
The current leap2a import code for flexible layouts can't handle a page with a custom layout. If the page's layout doesn't match any of the ones in the database, it just skips that page.
What we ought to do instead, is, if the layout described is legal, just create a new custom layout for the user, and use that.
Revision history for this message
| Mahara Bot (dev-mahara) wrote A change has been merged | #1 |
| Changed in mahara: | |
| status: | In Progress → Fix Committed |
| Changed in mahara: | |
| milestone: | 1.8rc1 → 1.8.0 |
| Changed in mahara: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Reviewed: https:/
Committed: http://
Submitter: Robert Lyon (<email address hidden>)
Branch: master
commit 9822e06d5038fcf
Author: Aaron Wells <email address hidden>
Date: Thu Sep 26 11:50:49 2013 +1200
Leap2a import support for custom flexible layouts
Bug1231205 - If the page's layout doesn't match a standard layout,
just create a custom layout for the user.
Change-Id: Id06b182ee3e90d
Signed-off-by: Aaron Wells <email address hidden>