Title: Database Table Prefix Change Causing Issues
Last modified: August 21, 2016

---

# Database Table Prefix Change Causing Issues

 *  [mygeek911](https://wordpress.org/support/users/mygeek911/)
 * (@mygeek911)
 * [12 years, 1 month ago](https://wordpress.org/support/topic/database-table-prefix-change-causing-issues/)
 * We changed the database tables’ prefix as a security measure, but now the plugin
   is throwing PHP errors because it is still using the old table prefix.
 * `[17-Apr-2014 14:41:24 UTC] WordPress database error Table 'database_name.wp_usermeta'
   doesn't exist for query SELECT meta_value FROM wp_usermeta WHERE user_id=127 &&
   meta_key='wp_s2member_custom_fields' made by require('wp-blog-header.php'), require_once('
   wp-includes/template-loader.php'), include('/themes/egesto/author.php')`
 * As you can see, it is using wp_ still for the prefix. How can we update S2Member
   so that it looks for the correct table prefix? Thanks.
 * [https://wordpress.org/plugins/s2member/](https://wordpress.org/plugins/s2member/)

The topic ‘Database Table Prefix Change Causing Issues’ is closed to new replies.

 * ![](https://ps.w.org/s2member/assets/icon-256x256.png?rev=980067)
 * [s2Member – Excellent for All Kinds of Memberships, Content Restriction Paywalls & Member Access Subscriptions](https://wordpress.org/plugins/s2member/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/s2member/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/s2member/)
 * [Active Topics](https://wordpress.org/support/plugin/s2member/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/s2member/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/s2member/reviews/)

## Tags

 * [PHP errors](https://wordpress.org/support/topic-tag/php-errors/)
 * [table-prefix](https://wordpress.org/support/topic-tag/table-prefix/)

 * 0 replies
 * 1 participant
 * Last reply from: [mygeek911](https://wordpress.org/support/users/mygeek911/)
 * Last activity: [12 years, 1 month ago](https://wordpress.org/support/topic/database-table-prefix-change-causing-issues/)
 * Status: not resolved