Bug #7861
manage: entity field is disabled and readonly, but considered when looking for required field
Début:
16 juillet 2015
Echéance:
% réalisé:
100%
Temps estimé:
Patch proposed:
Non
Planning:
Description
In the management interface I had a user that was not attached to an entity, I was trying to change one of the attributes but couldn't submit the form as there was no entity, and the entiy field was marked disabled and readonly, so I couldn't even select the default entity.
Révisions associées
manager: improve test on user creations (#7861)
Historique
Mis à jour par Frédéric Péters il y a presque 9 ans
Worse, for an user that had entity set to the default entity, the form would not validate either, as the entity was not submitted (because the select was disabled).
Mis à jour par Benjamin Dauvergne il y a presque 9 ans
- Assigné à mis à Benjamin Dauvergne
I think the rules for adding/editing an user should be:
| User status \ Number of entities | 1 | many |
| superuser | Can add/edit an user with or without an entity (entity field not required) | |
| administrator of users in 1 entity | New/Edited user is automatically in the only visible entity, entity field is read-only | |
| administrator of users in many entities | Cannot happen | administrator must select one entity in the one he administrates |
I'll define test cases following these rules.
Mis à jour par Benjamin Dauvergne il y a plus de 8 ans
- Statut changé de Nouveau à Résolu (à déployer)
- % réalisé changé de 0 à 100
Appliqué par commit authentic2|7cd1455acfba0b5ae02638c0699351b238f2dd69.
Mis à jour par Benjamin Dauvergne il y a environ 8 ans
- Statut changé de Résolu (à déployer) à Solution déployée
Mis à jour par Benjamin Dauvergne il y a plus de 6 ans
- Statut changé de Solution déployée à Fermé
manager: remove disabledness of the entity field in user creation form for superusers (fixes #7861)
It also fixes usability problems for administrator of one or many entities.