Contrib.social

Enhance (or add) access control in plugins where required config fields support tokens

Open on Drupal.org →
Created on 22 July 2023, over 1 year ago
Updated 5 June 2024, 6 months ago

Problem/Motivation

Plugin config forms are inconsistent WRT to config fields being required or not. And for those that support tokens, it is not always verified, if the given value (with or without a token) provides a proper value.

Example: read/write state or cache plugins.

Proposed resolution

Go through the plugins and add the required flag where needed and then also add the validation of values in the access method, returning access denied if a derived value is not valid. E.g. for the read/write state plugins, the key needs to be a non-empty string.

For all these cases we should then also have tests.

📌 Task
Status

Fixed

Version

2.0

Component

Code

Created by

🇩🇪Germany jurgenhaas Gottmadingen

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

contrib.social Blog FAQ Discussions
Production build 0.71.5 2024