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 seems to be working as expected. No obvious issues observed on the website. So far so good.
    After updating, I rechecked the wp_options table just 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.
    When I tried to update one of these entries with the wp_ prefix. I got an error message stating #1062 – Duplicate entry.
    Should I just ignore this? or what could be the solution for this?
    The Usermeta table is updated correctly.

    • This topic was modified 10 months, 3 weeks ago by formanite22.
Viewing 3 replies - 1 through 3 (of 3 total)
  • Alor Web

    (@jerrymayalor555)

    Hi @formanite22,

    Since your website is working perfectly fine after all the updates you have made to your database, I think you can ignore that issue.

    Thanks.

    Thread Starter formanite22

    (@formanite22)

    Hi @jerry

    Thanks for confirming!

    Thread Starter formanite22

    (@formanite22)

    Hi there,
    I have been using the WP-Optimize plugin to clean the database for a while. After updating the database prefix, I used the plugin, but the duplicated entries are still there.
    Yesterday, 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 for making changes in the database.
    So should I restore back using the backup?
    I made a backup using UpdraftPlus before updating the prefix.
    Or is there any other solution?

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