Use CAPTCHA permission instead of own permission

Created on 5 October 2022, over 2 years ago
Updated 26 October 2023, over 1 year ago

Problem/Motivation

@Grevil pointed out, that having a custom permission "administer friendlycaptcha" doesn't have many benefits, but also some drawbacks. As the friendlycaptcha settings page is placed in the CAPTCHA settings tabs, it might be confusing for users who have the "administer CAPTCHA settings" permission, but not the "administer friendlycaptcha" permission.
And even more vice-versa!

Same for status messages pointing out that the library is not configured correctly, etc.

The only reason for the separate permission might be to protect the API credentials from users having "administer CAPTCHA settings" permission, but is that relevant enough?

Would be nice to discuss this with @webflo. What do you think?

Steps to reproduce

Proposed resolution

Remove the "administer friendlycaptcha" permission and use "administer CAPTCHA settings" instead

Remaining tasks

User interface changes

API changes

Data model changes

📌 Task
Status

Fixed

Version

1.0

Component

Code

Created by

🇩🇪Germany Anybody Porta Westfalica

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

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

Production build 0.71.5 2024