Details
-
Type:
Sub-task
-
Status:
Closed
-
Priority:
Minor
-
Resolution: Fixed
-
Affects Version/s: 6.1.1 CE GA2, 6.1.20 EE GA2
-
Fix Version/s: 6.1.X EE, 6.2.0 CE M3
-
Component/s: WCM, WCM > Sites Administration
-
Labels:None
-
Branch Version/s:6.1.x
-
Backported to Branch:Committed
-
Epic/Theme:
-
Similar Issues:
Description
The sites memberships management UI works in such a way that when adding new members the administrator is shown a list of available users (paginated) with those that are already members with a checkbox already added. Because of this, when he checks it for new users and save, all users with the checkbox (previous members and new ones) are sent to the server. The server makes no distinction and makes them all members.
Previously, this was not an issue, but now that an action is done on the backend (assigning the new default roles/teams), it should only be done to the new members.

PASSED Manual Testing using the following steps:
1. Create a new site
2. Create a new site role
3. Create a new team in the new site
4. Create a new user
Go to "Site settings"
5. Add the role as the default role for the site
6. Add the team as the default team for the site
Go to "Site membership"
7. Click on "Add members" - "User"
8. Choose the new user and click on "Save"
Go to "Site membership"
9. Click on "View teams"
10. Click on "Assign members" in your team
-> you should see your user as a member of the team
Go to "Users and Organizations" (in the "Portal" section of the control panel)
11. Click on the new user - roles section
-> you should see that the user has the site role assigned
Fixed on:
Tomcat 7.0 + MySQL 5. Portal 6.2.x GIT ID: af7a102a3b5ab5df9640a083c480406a49d6b07a.