Blocks lost when importing a leap2a from mahara.org
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mahara |
Fix Released
|
Medium
|
Son Nguyen | ||
1.7 |
Fix Released
|
Medium
|
Son Nguyen |
Bug Description
When I export my account from mahara.org to a leap2a file, and then try to import it into a clean Mahara 1.7 installation, I find that it creates all the pages, but some of the Pages are missing their blocks, or their block content.
The problem seems to be because it's processing the leap.xml file sequentially from top to bottom. The artefacts that cause problems are listed further down in the XML file than the View they are used in. When the View is processed, it can't find the artefacts, and so it drops their blocks.
Leap2a import should be fully backwards-
I suspect this will not be a trivial issue to fix. The simplest thing we can do is to change our export format so that it puts artefacts first, but that won't solve for backwards compatibility. We should also take care that any solution is at least somewhat cross-platform compatible. So, for instance, parsing out all those that have a <mahara:
Changed in mahara: | |
milestone: | none → 1.7.3 |
Changed in mahara: | |
milestone: | 1.7.3 → none |
no longer affects: | mahara/1.8 |
Changed in mahara: | |
status: | Fix Committed → Fix Released |
Which blocks were affected, Aaron? Just so we know what to watch out for testing.