It sounds like your role is not actually super_admin. If it should be, maybe the related data had become corrupted. Super admin status is not managed like other roles. In order to be super admin, your user name must appear in the main site’s meta data (often wp_sitemeta, YMMV), keyed under “site_admins”. You can verify this via the phpMyAdmin app, usually accessed through your hosting account or cPanel.
If your user name is not in the meta value, do not attempt to add it with phpMyAdmin unless you are very familiar with serialized data format. It’s be better to note what user IS super admin and log on as them. If you have access to phpMyAdmin, you can change any other user’s password to one that you know by using the MD5 function when editing that user’s record. This of course would lock out that user until you tell them what their new password is.
Thanks for that BCworks. I checked in MySQL Admin and the the user in “wp_sitemeta” is correct.
I did try logging in as another superuser and got the same hanging loop with no message, just the icon in the status bar going round and round. If it was the superuser issue I would imagine a “don’t have permission to access that page” message.
Thanks
I would imagine a “don’t have permission to access that page” message.
Good point. I didn’t think this one through enough 🙂
Have you tried going directly to other network admin resources like /wp-admin/network/settings.php, etc.? I’m curious if it’s a /network/index.php issue or something more broad ranging.
Other things to try: Check error logs, both browser console and server PHP.
Check the network tab of your browser’s developer tools. It’s possible the request is getting stuck in an infinite redirect loop.
Without a better clue about the cause of the problem makes it difficult to suggest a solution. It’s possible it’s not even due to WP at all. Try temporarily placing a wp_die('Reached WP'); line in wp-config.php. If you get the message in response, we at least know WP was actually reached. This same method could be used in other core files to narrow down where the problem is occurring. For example, place it at the start of /network/index.php to see if the problem is before or after that point. Continue in this manner until you zero in on where the problem actually occurs.
That process obviously could get rather tedious. Also requires some knowledge of the WP loading sequence. As a blind “shot in the dark”, you could refresh all of your installation’s core files from a fresh download on the assumption a file somewhere had become corrupted. Do so by performing a manual update, even if it’s to the same version. There’s a chance this will fix the problem without needing to determine the root cause.
