WordPress.org

Ready to get started?Download WordPress

Forums

You do not have sufficient permissions to access this page (5 posts)

  1. gayanpathirage
    Member
    Posted 2 years ago #

    Hi All,

    If you see the above error when you try to login to the admin interface, it may due to your recent change to table prefix.

    Normal WordPress table prefix is wp_ but you can change this to something else at a later stage.(e.g. You want to have two WordPress sites in same database)

    Lets say if we change our table prefix to site1_ from wp_. (this you can do by changing wp-config.php and renaming tables accordingly)

    Then you must do this (Still in 3.3.2 version);

    1. Goto site1_usermeta table and update all occurrences of following to start with your new table prefix

      • wp_capabilities -- to --- > site1_capabilities
      • wp_user_level -- to ---- > site1_user_level
      • wp_autosave_draft_ids -- to ---- > site1_autosave_draft_ids
    2. Goto site1__options table and update all occurrences of following to start with your new table prefix
      • wp_user_roles -- to ---- > site1_user_roles

    Then the issue should be solved! You should be able to login to the admin interface.

    But I don't still understand the logic to use database prefix for such parameters. May be WordPress developer could address this.

    Previous links that help me to solve this are;
    Post by Svenjick
    Beconfused Article

  2. marv51
    Member
    Posted 2 years ago #

    Hi, your post is very confusing to me. Why would anybody change the database prefix on an existing installation?
    But maybe this page is useful to you: http://codex.wordpress.org/Creating_Tables_with_Plugins
    I don't think a security update would change anything related to the database structure.

  3. gayanpathirage
    Member
    Posted 2 years ago #

    Like you said, need for table prefix change is very rare or one could think of it at the time of installation. However it is needed in some migrations and that is why WordPress developers have thought about it and include that as an option in wp-config.php

    e.g. Scenario

    You already have a site with table prefix wp_. Later date you want to download and improve the site locally and upload that to the same host to get feedback from your visitors.

    Since the original tables are with wp_ your new version table names should start with a different prefix to reside in same database without colliding with your existing site data. So you may choose site1_ as your table prefix. Then you can import the new tables in to same host db while having exiting site and new site files in two different folders.

  4. WPYoda
    Member
    Posted 1 year ago #

    Thanks, that fixed it. I had to put 3 blogs into one database so I had to change the prefix and like you had, it broke my blogs. Here's my SQL version of your post:

    update site1_usermeta set meta_key = 'site1_capabilities' where meta_key = 'wp_capabilities';

    update site1_usermeta set meta_key = 'site1_user_level' where meta_key = 'wp_user_level';

    update site1_usermeta set meta_key = 'site1_autosave_draft_ids' where meta_key = 'wp_autosave_draft_ids';

    update site1_options set option_name = 'site1_user_roles' where option_name = 'wp_user_roles';

  5. GustavoZ77
    Member
    Posted 1 year ago #

    Hello!!

    i have this problem and i dont kwon hot to fix it
    some body could helpme please?

    "You do not have sufficient permissions to access this page."

Topic Closed

This topic has been closed to new replies.

About this Topic