-
Notifications
You must be signed in to change notification settings - Fork 17
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
Cannot add super-admin #7
Comments
I see in the latest vvv-2.0 it is grabbing the nightly build, I already tried changing the version to --stable 1.2 and still got same result. |
Hi @jimboobrien, Thanks for the report. Just to make sure |
Also, if you use triple backticks |
Thank you for the tip. Here is the output when I run the command
|
So I have found that when I vagrant up there are two entries in the database for site_admins in the sitemeta table. Once the empty key has been removed the wp super-admin list command and the add command work as expected. Therefore, might need to check on the wp multisite-install does not create a new site_admins key and instead updates the existing key. Hope this helps.
|
Hi @jimboobrien, I wrote some test cases around this scenario in #8 and wasn't able to reproduce against a stock WordPress install. It seems like this behavior may be specific to your environment — somehow an invalid entry ended up in the first If you can track down steps to reproduce the issue in a fresh WordPress install, I'd be happy to look at this further. |
Hello,
I'm setting up a VVV environment on vagrant, and I'm running into issues with not being able to add my user as a super admin to see network screens in the wp admin screens.
I have used the following line to create a multisite-install using wp cli:
When I vagrant ssh into the virtual machine and try to run the command to add a user as a super admin I get this error:
Here is my wp --info w/ version
Here it shows the users, and their privileges:
Here is line 107 in Super_Admin_Command.php
Please let me know if this is a fix you can provide, or if I need to change something in my env, or if this is something wrong with the new version of vvv(2.0).
Thanks for your time,
The text was updated successfully, but these errors were encountered: