After updating database prefix

  • Hi,
    I have successfully updated the database prefix manually. After updating, could successfully login to cpanel, admin and other authors account. The site seemed to be working as expected.
    However, after updating, I came across cache issues on my website. I rechecked the wp_options table to verify that all entries starting with wp_ prefix are updated (20 entries). While I was going through, I could see a couple of duplicated entries (now a total of 22 entries) that show the previous prefix (wp_force_deactivated_plugins and wp_cloudflare_page_cache_install). These two entries are also available with the new updated prefix.
    Few days ago, I noticed the cache issue on my website. Though after updating the database prefix, I cleared the Cloudflare cache too. Some changes that I made especially in the sidebars and in the Customizer tool are not visible at once, when viewing my website on different browser/devices. However, the changes made are visible when I’m logged into my admin account.
    So, it seems the issue is related to the duplicated “wp_cloudflare_page_cache_install” entry. The cache was working correctly before updating the database prefix.
    Since I’m not an expert of MySQL.
    So should I restore back using the backup that I made using UpdraftPlus before updating the prefix.
    Or is there any other solution?

Viewing 3 replies - 1 through 3 (of 3 total)
  • Moderator bcworkz

    (@bcworkz)

    Did you also clear your browser’s cache? You’ve no other server side caching besides Cloudflare? Admin views of the front end are often not cached, so the correct view only when logged in does confirm it’s a caching issue of some sort.

    While you could restore from backup, attempting the same prefix change procedure again will most likely result in the same problem.

    If you think the duplicate “wp_cloudflare_page_cache_install” entry is an issue, try deleting the old one with the old prefix. Before doing that you should export the table as a backup. Better safe than sorry.

    Thread Starter formanite22

    (@formanite22)

    Hi @bcworkz,
    Thanks for your response.
    There is no other server side caching besides Cloudflare.
    I optimized the database using the WP_Optimize plugin. I also cleared the Cloudflare cache. But the duplicate entries and the cache issue persist.
    I’m not expert of SQL. So what is safe option to resolve this issue.
    Delete the duplicated entries OR restore from the backup?

    Moderator bcworkz

    (@bcworkz)

    As long as you have a good backup you can take reasonable risks in safety. Removing duplicate entries that involve the old prefix is a reasonable risk. Restoring from backup would not accomplish your ultimate goal of changing prefixes so it’s only useful if everything else results in failure.

    One thing to watch out for is sometimes “wp_” appears in records that are unrelated to the current prefix. You should not attempt to remove or change these. Such records likely do not have duplicates so removing only duplicates should be fairly safe.

    Regardless of how safe I say something is, make another full backup before making changes, just in case ??

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘After updating database prefix’ is closed to new replies.