mahara-contributors team mailing list archive
-
mahara-contributors team
-
Mailing list archive
-
Message #27831
[Bug 1474628] A change has been merged
Reviewed: https://reviews.mahara.org/4960
Committed: https://git.nzoss.org.nz/mahara/mahara/commit/7b0d6aa82a5e92bc5349d991d8af4a9a70700b76
Submitter: Robert Lyon (robertl@xxxxxxxxxxxxxxx)
Branch: master
commit 7b0d6aa82a5e92bc5349d991d8af4a9a70700b76
Author: Aaron Wells <aaronw@xxxxxxxxxxxxxxx>
Date: Wed Jul 15 15:21:19 2015 +1200
Incorrect check for the presence of collections in export (Bug 1474628)
It appears this code is meant to check for whether $views is set to
self::EXPORT_ALL_VIEWS (a constant that equals -1).
But even if you're exporting all your views, you still want to group
them together into collections.
Change-Id: Ic4f8c94ae3b2da1916806baddd6897dc6bb3ef2a
--
You received this bug notification because you are a member of Mahara
Contributors, which is subscribed to Mahara.
Matching subscriptions: Subscription for all Mahara Contributors -- please ask on #mahara-dev or mahara.org forum before editing or unsubscribing it!
https://bugs.launchpad.net/bugs/1474628
Title:
Leap2a: Collections being exported as individual pages
Status in Mahara:
Fix Committed
Status in Mahara 15.04 series:
In Progress
Status in Mahara 15.10 series:
Fix Committed
Bug description:
As reported here:
https://bugs.launchpad.net/mahara/+bug/1464477/comments/2
The patch https://reviews.mahara.org/3624, in Mahara 15.04, caused a
regression where Leap2a fails to export collections. Instead, the
collections are exported as individual pages.
To manage notifications about this bug go to:
https://bugs.launchpad.net/mahara/+bug/1474628/+subscriptions
References