Leap2a import of "Just some of my collections" doesn't put the pages into the imported collection
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mahara |
Fix Released
|
High
|
Unassigned | ||
1.10 |
Fix Released
|
High
|
Unassigned | ||
1.9 |
Fix Released
|
High
|
Unassigned | ||
15.04 |
Fix Released
|
High
|
Unassigned | ||
15.10 |
Fix Released
|
High
|
Unassigned |
Bug Description
If you create a Leap2a export using the option "Just some of my collections", and then import it back into Mahara, the pages and collections get created, but the pages are not linked into the collection. Instead the pages are orphan pages and the collection is empty.
I tested this from 1.8 to 15.10dev and found it present in all versions.
To replicate:
1. Create three pages called "A", "B", and "C"
2. Create a collection called "D"
3. Put the three pages in the collection
4. Go to Portfolio -> Export. Select "Leap2A" format, and select "Just some of my pages". Click "Generate Export". Download the resulting Leap2A file
5. Either as the same user, or as a different user, go to Portfolio->Import
6. Use the "Upload Leap2A file" button to pick the leap2a you just downloaded in step #4. Click "Import"
7. Go to "Portfolio -> Collections" and "Portfolio -> Pages" and see what pages and collections you now have in your portfolio.
Expected result: You should have a collection called "D" with pages "A", "B", and "C" in it.
Actual result: You have an empty collection called "D", and three orphan pages called "A", "B", and "C"
Changed in mahara: | |
status: | Fix Committed → Fix Released |
Confirmed in versions from 1.8 to 15.10dev. Since the Leap2a code is rather complex, it may not be feasible to backport the fix to 1.9 and 1.10. We'll have to make a judgement call on that once we have a fix in place.