Improve UX (features depending on ACL)

Created on 5 December 2014, almost 10 years ago
Updated 30 April 2023, over 1 year ago

Problem/Motivation

This issue basically boils down to the following two feature requests.

Feature request #1

When an ACL is created the creator is automatically added to ACLs. He/she can be removed from it by self or by an admin. However, users could accidentally remove themselves and then lose access to their own node. There should be a way to prevent users from removing themselves.

Feature request #2

When I click “Add user” it adds the user immediately making it appear as though that's all I had to do. However, changes are lost if one forgets to click the “Commit updates”-button. There should be a way to warn a user that forgets this with something like “You have unsaved changes”.

The problem

The fundamental problem with both these feature requests is that this module is only a front end to the ACL module, and this part of the user interface is handled by ACL.

Current status: Postponed until somebody signs up and commits to resolve the issue.

Proposed resolution

This probably needs to be resolved by patching the ACL module. To get such patches committed, one also needs cooperation from the maintainer of the ACL module.

This section to be filled in with description of the proposed solution by the person that signs up for working on this issue.

Remaining tasks

To be filled in with details about reviews needed, tests to be written or run, documentation to be written, etc. when somebody signs up for working on this issue.

Postponing until someone is willing to take on the task of working on this.

User interface changes

(Description of new or changed features/functionality in the user interface, modules added or removed, changes to URL paths, changes to user interface text.)

API changes

(Description of API changes/additions that would affect module, install profile, and theme developers, including examples of before/after code if appropriate.)

Data model changes

(Description of satabase or configuration data changes that would make stored data on an existing site incompatible with the site's updated codebase, including changes to hook_schema(), configuration schema or keys, or the expected format of stored data, etc.)

Original report by abarpetia

Hello,
Is it possible to restrict users to only manage view or update or delete permissions? Currently, Flexi Access only have one permission which is "Access Flexi Access" is there any chances to have more permission like "only manage View permission" OR "only manage Update permission" OR "only manage Delete permission".

Feature request
Status

Closed: outdated

Version

1.0

Component

User interface

Created by

🇦🇺Australia abarpetia

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