jpedroza2k

I found the issue:
This posting is the solution.

Specifically, for those in the same mess:

Then you have to find in wp-includes/capabilities.php the line:

$this->cap_key = $wpdb->prefix . ‘capabilities’;

and replace it with

if (defined (‘CUSTOM_CAPABILITIES_PREFIX’)) {
$this->cap_key = CUSTOM_CAPABILITIES_PREFIX . ‘capabilities’;
}
else { $this->cap_key = $wpdb->prefix . ‘capabilities’;
}

That’ s all! Good luck!

The way this works, is that it checks if there is a custom prefix and if so appends it to the cap_key property. If not, it uses the default.

Hope this helps.

It’s looking increasing like the database that’s running 2 sit4s may have been damaged during the upgrade. You mentioned one authentication for two sites? Could you elaborate on that? Perhaps it’s the authentication that’s gone pear-shaped.

What we have is three blogs, each has its own table prefix, wp_, ag_, ai_. We also have the following in the config:

define('CUSTOM_USER_TABLE', 'wp_users');
define('CUSTOM_USER_META_TABLE', 'wp_usermeta');
define('CUSTOM_CAPABILITIES_PREFIX', 'wp_');

This causes the authentication for all three sites to use the same authentication database. The only blog that is functional on the back end is the one that uses wp_ for the table prefix (the only one that doesn’t have the custom code for the user_table, etc.

I’m having the same issues at 7efitspa.com

Are you running multiple blogs from one authentication and separate prefixes, or is it a single blog?

Have all machines using the site had their caches flushed and cookies cleared?

Yes, and we have even tried it on different devices and browsers.

Did you reset the plugins using Phpmyadmin?

Yes, I didn’t use phpMyAdmin, I used the cli, but same results.

There are no errors in the logs for any of the sites either.

Nothing in there at all. It seems to be localized to the wordpress environment. I even enabled debugging on the site in wp-config.php and there were two template warnings, no errors. Even fixing the issues with the warnings didn’t help.

Sadly, no. The update was run by an over zealous client and the only other copy was a weekly archive last Friday. They made major changes in content that they don’t want to have to redo if possible.

switching to the Twenty Eleven theme by renaming your current theme’s folder inside wp-content/themes and adding “-old” to the end of the folder name using FTP or whatever file management application your host provides.

I tried this, but the same error still shows. Also, the live site showed a white screen.

– resetting the plugins folder by FTP or phpMyAdmin.

I did this on all three sites, so that none of them had any plugins loaded.

– re-uploading all files & folders – except the wp-content folder – from a fresh download of WordPress.

Same error

– running the upgrade manually via wp-admin/upgrade.php

Shows “No update required”

edit: fixed typo

I forgot to mention, I have tried disabling all the plugins across all three sites as well, and no luck there either. There are no errors in the logs for any of the sites either.