Member Roles options need documentation including 'Security Lock'

Offen
  • Stimmt etwas nicht?
#827 1 Kommentar 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
2/5
Geschätzter Aufwand
1-3 Stunden
Anfängerfreundlichkeit
35/100
Issue-Typ
Dokumentation
Klarheit
Größtenteils klar
Aktivitätsstatus
Veraltet
Tech-Stack
php
Bereich
documentation

Rechercherichtung

Update the Member Roles section at control-panel/member-manager.html#member-roles, as identified in the issue. Read the current section alongside the CP description and the reported Security Lock behavior. Document the role options, including Security Lock, and make the new information searchable; done when the section explains the behavior that caused the pending-member approval error.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

Description of the problem
A client reported an issue with pending members, and they were seeing an error as follows when they attempted to approve pending users.
image

The member role had 'security lock' enabled, I think it was on by default after a recent upgrade from EE5.x to EE7.4.1

I tested this and verified that as a super admin, I was unable to approve pending members in with a locked member role. This seems to be contrary to the description in the CP interface which says:

Only Super Admins can add or remove members from this role.

Error Messages
Unable to activate [email]. The member role [member role] is locked.

Additional context
URL of CP screen that is confusing:
/contentzsystem/index.php?/cp/members/roles/edit/5

There is a big gap between the documentation in this section vs. what the UI has. It would be really helpful to add these items and ensure they are searchable. I could not find any references to 'security lock' in the documentation.

I would assume this updated documentation should go here:
https://docs.expressionengine.com/latest/control-panel/member-manager.html#member-roles

Vorherrschende Sprache
CSS
Sterne
22
Forks
79
Ø Merge
2 T. 1 Std.
Gemergte PRs (30 T.)
6

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus ExpressionEngine/ExpressionEngine-User-Guide

Alle Issues in ExpressionEngine/ExpressionEngine-User-Guide

Ähnliche Issues

Weitere Issues zu Documentation

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.