Title: Upgrading doesn't drop correct table
Last modified: August 30, 2016

---

# Upgrading doesn't drop correct table

 *  [Beholder1984](https://wordpress.org/support/users/beholder1984/)
 * (@beholder1984)
 * [10 years, 9 months ago](https://wordpress.org/support/topic/upgrading-doesnt-drop-correct-table/)
 * When upgrading to the newest version I found out there is an issue with the dropping
   of the “old” table. The WP prefix is added twice which in my case resolved in
   trying to delete the wp_wp_fblb table which does not exist.
 * $table_name = $wpdb->prefix . ‘fblb’;
    $charset_collate = $wpdb->get_charset_collate();
   $wpdb->query(“DROP TABLE IF EXISTS {$wpdb->prefix}$table_name”);
 * [https://wordpress.org/plugins/wp-like-button/](https://wordpress.org/plugins/wp-like-button/)

Viewing 1 replies (of 1 total)

 *  Plugin Author [CRUDLab](https://wordpress.org/support/users/amirk27/)
 * (@amirk27)
 * [10 years, 4 months ago](https://wordpress.org/support/topic/upgrading-doesnt-drop-correct-table/#post-6420339)
 * Hi,
 * Thank you so much for pointing out this issue. We will add this fix in upcoming
   version.
 * Thanks!
    CRUDLab Support

Viewing 1 replies (of 1 total)

The topic ‘Upgrading doesn't drop correct table’ is closed to new replies.

 * ![](https://s.w.org/plugins/geopattern-icon/wp-like-button_d09e60.svg)
 * [WP Like Button](https://wordpress.org/plugins/wp-like-button/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/wp-like-button/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/wp-like-button/)
 * [Active Topics](https://wordpress.org/support/plugin/wp-like-button/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/wp-like-button/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/wp-like-button/reviews/)

 * 1 reply
 * 2 participants
 * Last reply from: [CRUDLab](https://wordpress.org/support/users/amirk27/)
 * Last activity: [10 years, 4 months ago](https://wordpress.org/support/topic/upgrading-doesnt-drop-correct-table/#post-6420339)
 * Status: not resolved