Permissions are a bit inconsistently named, for instance:
- payment.rules.administer
Used for the configuration of Rules events, actions, and conditions.
- payment.administer
To configure Payment (field) configuration.
- payment.update.any
To update any payment method.

We should convert these to a more consistent naming format. Proposition:
MODULE_NAMESPACE.LOCAL_NAMESPACE.OPERATION.DETAILS
Where MODULE_NAMESPACE will always be "payment", LOCAL_NAMESPACE can be the entity type, or a third party module, OPERATION is, well, the operation ("create", "administer", etc), and DETAILS can be a further specification, such as "own" or "any".
Examples:
- payment.payment.delete.own (to delete own Payment entities)
- payment.global.configure (to administer Payment module's global configuration)
- payment.rules.administer (to administer Payment module's Rules configuration)
- payment.payment_method.create.PaymentMethodBasicController (to create payment methods using the PaymentMethodBasicController controller)
- payment.payment_method.configure (to generally configure payment methods, like "administer", but does not grant access to perform operations on individual payment methods)

Comments

xano’s picture

Assigned: Unassigned » xano
Status: Active » Needs review
StatusFileSize
new13.53 KB
xano’s picture

StatusFileSize
new28.56 KB

Status: Needs review » Needs work

The last submitted patch, payment_1572846_01.patch, failed testing.

xano’s picture

Status: Needs work » Needs review
StatusFileSize
new29.09 KB
xano’s picture

Status: Needs review » Fixed

Committed to 7.x-1.x.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

xano’s picture

Assigned: xano » Unassigned
xano’s picture

Issue summary: View changes

bluh