export doesn't distinguish a 'collections' export from a 'views' export
Bug #825311 reported by
Stacey Walker
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mahara |
Fix Released
|
Wishlist
|
Stacey Walker |
Bug Description
Would be good if export distinguished whether a user was downloading collections or pages.
Currently, when you export a few pages as HTML you get collection information included and displayed on the index page as a standard format. This might be confusing to the user if they weren't expecting collection information as well.
I noticed this issue while trying to implement a PDF export a little better as I need the difference clear when creating a table of contents for combined page/collection exporting. :)
Changed in mahara: | |
importance: | Undecided → Wishlist |
status: | New → Incomplete |
status: | Incomplete → Triaged |
tags: | added: collections export |
Changed in mahara: | |
milestone: | none → 1.6.0 |
Changed in mahara: | |
milestone: | 1.6.0 → 1.7.0 |
Changed in mahara: | |
milestone: | 1.7.0 → 1.8.0 |
Changed in mahara: | |
milestone: | 1.8rc1 → 1.8.0 |
Changed in mahara: | |
milestone: | 1.8.0 → 1.9.0 |
To post a comment you must log in.
I can also confirm that this is the same for leap2a exports.
Say I have a collection with 5 pages in it, but upon export I choose to only export one page in my leap2a package. When I import that later the collection information is recreated as well so I have a replica of the collection with the single page in it.
I think that if a user is wanting/expecting to export a single page that's all they should get and the collection information can be obtained by exporting a collection itself. Otherwise it seems slightly (not completely, but slightly) redundant having the two options at export.