• Resolved jpedroza2k

    (@jpedroza2k)


    I ran the update on three of my sites that use the same database, but with different prefixes. They do, however, share a common authentication table. The two that have the different prefix are giving me the error:

    You do not have sufficient permissions to access this page.

    This is after I login, and on every page in the dashboard. I have verified my permissions are set, and I can log into the one that is the default authentication table, just not the other two.

    Is anyone else seeing this? I have searched the forums and Google, but no love so far.

Viewing 3 replies - 16 through 18 (of 18 total)
  • here is what I’ve tried thus far:

      clean install via ftp
      disabled all plugins (changed name of plugins folder, also via php admin)
      changed name of theme folder (won’t adopt twentyeleven theme either)
    Thread Starter jpedroza2k

    (@jpedroza2k)

    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.

    Thread Starter jpedroza2k

    (@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.

Viewing 3 replies - 16 through 18 (of 18 total)
  • The topic ‘You do not have sufficient permissions after update to 3.4.2’ is closed to new replies.