-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Incorrectly handled "Add User" for with multisite setup #179
Comments
@vasyltech @aamplugin Here is a screenshot of the issue: |
This appears to be caused by the file: As you can see below, this file modifies the add-user page, but does not consider 'multi-site' installs, and the two forms that multisite presents on that admin page. Here is the markup of the page that is affected - you can see that:
2 the new role selection is being added to the upper form only, not the lower one
Here is the PHP from AAM that affects this: Hope this helps! :)
|
@terrance-orletsky-d7 thank you so much for the information. I'm analyzing your feedback and the fix is going to be included in the next AAM release. |
The side effect for the reported bug is also 3 PHP errors:
|
Thanks for addressing this so quickly, @aamplugin - much appreciated! |
Thanks for the quick fix, @aamplugin @vasyltech - that all appears to work well now... I noticed another issue now, with editing the multiple roles, but not sure if it is related, so I posted in another ticket Cheers! |
GIVEN
AAM is installed,
Premium/ complete package,
and the WP site is a multisite subdomain installation:
WHEN
An Admin user tries to add a new user to a site
THEN
The 'Role' dropdown is missing from the lower form,
and the user is added with no role
EXPECTED BEHAVIOUR:
THEN
The 'Role' dropdown (or multiselect) is available,
and the Admin is able to select a role(s) for the new user being added
and the user is added with that/those role(s)
Incidentally, in the upper form, there are two ways to select (multiselect, and a dropdown), so my guess is that the dropdown was meant to be replaced in the second form as well, but it was not replaced properly
The text was updated successfully, but these errors were encountered: