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.
** Changed in: mahara
Assignee: (unassigned) => Stacey Walker (stacey)
--
You received this bug notification because you are a member of Mahara
Core, which is subscribed to Mahara.
https://bugs.launchpad.net/bugs/825311
Title:
export doesn't distinguish a 'collections' export from a 'views'
export
Status in Mahara ePortfolio:
Triaged
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. :)
To manage notifications about this bug go to:
https://bugs.launchpad.net/mahara/+bug/825311/+subscriptions
_______________________________________________
Mailing list: https://launchpad.net/~mahara-core
Post to : [email protected]
Unsubscribe : https://launchpad.net/~mahara-core
More help : https://help.launchpad.net/ListHelp
