Collections shared with groups not identified as such
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Mahara |
Fix Released
|
Wishlist
|
Unassigned | ||
Bug Description
Currently in 1.3 and 1.4dev collections can have access permissions set to share with groups. However when you go to view the group all the views within the collection are displayed in the Dashboards 'Group Views' as separate views and not as the collection that was shared.
With the new 1.4 change to the blocktype for choosing group owned or shared views independently when editing the dashboard a third option for shared collections could be added. This might also help occasionally with Bug# 702173 by limiting the view list a bit.
The issue of collections not able to be "submitted" (views only, Bug# 617376) would mean that this would probably be done by querying whether or not views shared with the group belong to collections and separating them out into each list within the blocktype code.
Unless the bigger issue of collection submission is sorted out first.
| Changed in mahara: | |
| status: | New → Confirmed |
| Changed in mahara: | |
| milestone: | 1.4.0 → none |
| tags: |
added: collections groups removed: collection group |
| Robert Lyon (robertl-9) wrote | #1 |
| Changed in mahara: | |
| milestone: | none → 1.10.0 |
| status: | Confirmed → Fix Committed |
| Changed in mahara: | |
| status: | Fix Committed → Fix Released |
This has been fixed for the 1.10 release