Hello! I absolutely love the Taxonomy Access module and the ways in which it can be used universally and easily to do access control across a site. I'm using it extensively for the membership management of my site. However, I am using it with other modules and add-ons (AMember for paid memberships, Userpoints to allow users who participate more to gain various levels of access to the site, etc.), and I am finding it very difficult to get all this working smoothly given that TA applies DENY after ALLOW.
An example: role1 is setup with limited access, role2 with increased access, then role3 with full (paid) access. A user registers and then works their way up to role2 through Userpoints. But now, Userpoints will have to remove them from role1 and add to role2, otherwise the DENY permissions in role1 would take presidence. Then, the role2 user decides to pay for access, and now AMember has to drop them from any other groups with DENY permissions before adding them to role3. You can see how this problem adds complexity and would require a lot of modifications to other modules.
I'm not sure why TA uses this order (or what deep logic would be affected by changing it around), but I really need to have the more permissive permissions have the highest priority so roles can be stacked. I am new to Drupal and my PHP skills are not very advanced, so I was rather lost while looking at the module code. I'm hoping someone can offer advice on changing the permission order around.
DDEV is the official local development tool of Drupal. And like Drupal, DDEV depends on the support of the open source community.
