Details
-
Bug
-
Resolution: Fixed
-
High
-
5.1.0beta1
-
Server OS: Debian
PHP: 5.3.22
Database: MySQL 5.1.61
Browser: Firefox 19
Description
With public API we do the following steps:
1 - Create a new user with data: - First Name: "Test" - Last Name : "User" - Username : "test" - Password : "user" - Email : "test@user.test" - UserGroup : "Editor" 2 - Assign "Test User" to "Administrator users" group 3 - Verify that it was successfully assigned 4 - Unassign "Test User" from "Editor" group 5 - Verify that it was successful unassigned 6 - On admin2 verify that user belongs only to "Administrator users" group
This works fine.
However if we do the following steps:
1 - Create a new user with data: - First Name: "Test" - Last Name : "User" - Username : "test" - Password : "user" - Email : "test@user.test" - UserGroup : "Editor" 2 - Unassign "Test User" from "Editor" group 3 - Verify that it was successful unassigned 4 - Assign "Test User" to "Administrator users" group 5 - Verify that a "NotFoundException" was raised
The content of the user is not in ezcontentobject, but there is data in ezuser:
Access to the database (mysql -u <username> -p <database>)
Run the following commands:
- SELECT * FROM ezcontentobject;
- Verify that "Test User" is not present
- SELECT * FROM ezuser;
- Verify that data related to the "Test User" is still present
So the problem is:
- if it is supposed to leave the user in the database it should be possible to used/access it, like reassign it (right?)
- if it is NOT supposed to leave the user in the database should the reference for it on the "ezuser" table stay( ? )
Attachments
Issue Links
- relates to
-
EZP-20747 unAssignUserFromUserGroup should throw BadState when 1 group left
- Closed