Download & Extend

Allow configuration of TAC permissions on term/vocab create/edit

Project:Taxonomy Access Control
Version:7.x-1.x-dev
Component:User interface
Category:feature request
Priority:normal
Assigned:xjm
Status:active
Issue tags:TAC UX

Issue Summary

Right now, newly created categories are not automatically included in the permissions for each role. It seems that for my site this should automatically happen with a prescribed default applied (something safe and restrictive). If this does not happen, it appears that Taxonomy Access does not do its job with these new categories. Can there be a more robust overall settings page that sets the appropriate behavior for newly added vocabularies and their terms? I think this would apply to the 5.x and 6.x branches of this module. Thank you for considering this feature.

Comments

#1

Another thought: any way this can tie into the process of adding a taxonomy term or vocabulary? Are there hooks that will allow this? So when I add a term with the core taxonomy module, it allows me to fill in the related checkboxes for View, Update, Delete, Create, and List, then select "apply taxonomy permissions to: all roles, all roles except anonymous, all roles except anonymous and authenticated, role-x, role-y, etc." where x and y are specific names of roles? This might be a great way to keep taxonomy permissions updated with any new categories that are added to the site.

#2

Title:Automatically add defaults to newly created category» Proposed Overhaul to Taxonomy Access User Interface (UI)

Proposal:

Fix process when new taxonomies are added to a site: use hooks so that when I add a term with the core taxonomy module, it allows me to fill in the related check-boxes for View, Update, Delete, Create, and List, then select "apply taxonomy permissions to: all roles, all roles except anonymous, all roles except anonymous and authenticated, role-x, role-y, etc." where x and y are specific names of roles.

I'll add more suggestions soon.

#3

These all sound like great suggestions. Tracking.

#4

#5

#51197: Separate permissions into "Simple Permissions" and "Moderation Permissions" also has some suggestions about improvements to the admin interface, although much of the discussion is outdated.

#6

Title:Proposed Overhaul to Taxonomy Access User Interface (UI)» Allow configuration of TAC permissions on term/vocab create/edit

#7

Version:6.x-1.x-dev» 7.x-1.x-dev

Bumping to 7.x.

#8

Assigned to:Anonymous» xjm

#9

Tagging.

#10

We're getting ready to implement this for Drupal Gardens, and I'm trying to think how it should look. We've been talking about implementing a checkbox grid like on the permissions page, but that doesn't really work for TAC because checkboxes are binary and allow/ignore/deny is ternary. I guess maybe it should look like the bottom of this mockup, without the "Term:" dropdown or the Add button?

#11

Ideally, there will be API to render the grant rows/tables. On term and vocab pages, the table would presumably include a row for each role (as opposed to each term).

The current grant table is built by taxonomy_access_admin_build_row(), taxonomy_access_admin_form(), and theme_taxonomy_access_admin_form(), which should be refactored a bit.

#12

With the simplified UI, if we assume only one term can be assigned per node, and all roles are enabled, I think we can just mimic the core permissions UI with checkboxes.

#13

This is a straight TAC issue - the simplified UI we're building on top of TAC isn't really relevant to this issue. I think in general for TAC the magic marker mockup makes sense.

#14

So if we put this UI on all the term pages, does the current TAC admin ui go away?

Also, shoudl the permissions be there by default, or is there a button to enable a term for access control?

#15

xjm mentioned in IRC the other day that she wants to make it so that vocabularies get enabled and disabled. That is, enabled vocabularies would be vocabularies with an entry in {taxonomy_access_default}, and defaults would become required rather than optional. (See the "Enabling a vocabulary" section in the mockups at http://xjm.drupalgardens.com/blog/tac-mockups). With that in mind, I would say the permissions should appear on the term page of any term belonging to an enabled vocabulary.

#16

A simplified TAC UI was recently released on Drupal Gardens. Is this UI under consideration to come back to the public TAC module?

#17

The simplified UI is available at http://drupal.org/sandbox/pwolanin/1363014. Hopefully it can be incorporated into TAC itself in some way; we tried to write it in such a way that that would be possible.

#18

Yep, the plan is to make the Simple TAC UI available as part of the main project. A patch for the improved interface in #1314606: Redesign role configuration page will also be available for testing this weekend.

Edit: Realized I failed to actually link the issue.