mahara-contributors team mailing list archive
-
mahara-contributors team
-
Mailing list archive
-
Message #02729
[Bug 723225] [NEW] Collections shared with groups not identified as such
Public bug reported:
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.
** Affects: mahara
Importance: Wishlist
Status: New
** Tags: collection group
--
You received this bug notification because you are a member of Mahara
Contributors, which is subscribed to Mahara.
https://bugs.launchpad.net/bugs/723225
Title:
Collections shared with groups not identified as such
Status in Mahara ePortfolio:
New
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.
Follow ups
References