View Issue Details

IDProjectCategoryView StatusLast Update
0002254Composrcore_permission_managementpublic2016-12-08 00:35
ReporterChris GrahamAssigned To 
SeverityFeature-request 
Status non-assignedResolutionopen 
Product Version 
Fixed in Version 
Summary0002254: Redesign category ownership
DescriptionWe have category ownership for:
 - Galleries (personal galleries)
 - News categories (blogs)

News categories works via a nc_owner field. If nc_owner is set, it's a blog.

Galleries has both a g_owner field, and a concept of personal gallery based on the name of the gallery. I think really we only need g_owner.


It's currently possible to say the owner of an entry or category has edit/delete access specifically against that category, but it would be nice to have wider control, and this is not feasible via that same approach of specific privileges. For example, we can't define a privilege like "edit other people's content under a category you own" because this would be an enormous proliferation of privileges. And, we can't hard-code it either because that's too much of an assumption.

The best approach would be to have some way of defining what privileges the owner of a category has under their categories, on a module-by-module basis. So for example, when a personal gallery is auto-created, the system would copy through a template set of privileges against the specific member who owns that gallery, from the ones that have been pre-defined.
Additional InformationThis is a bit complex. Maybe initially the best approach is not to have any UI, just a development framework for it. For example, a Development non-bundled addon that provides a hook-based example of copying through some member privileges for new member galleries.

The number of hours set against this task is therefore fairly meaningless, as it could be chipped away at.
TagsNo tags attached.
Time estimation (hours)30
Sponsorship open

Activities

There are no notes attached to this issue.

Issue History

Date Modified Username Field Change