Today, I had some issues moving a local WP installation to the live server.
After some experimenting, I discovered that the issue had to do with case-sensitivity of the table_prefix as defined in the wp-config.php.
The local configuration:
- wp-config defined $table_prefix = “VYN_”, using capitals.
- The database contained tables with the prefix “vyn_”, using lower case.
- Worked fine, no issues here.
- Export of database used “vyn_” as lower case table prefix.
Migration to production:
- Importing database tables resulted in tables with the prefix “vyn_”, using lower case.
- Using wp-config with $table_prefix = “VYN_”, using upper case resulted in a redirect to the installation page to enter database configuration etc.
- Using wp-config with $table_prefix = “vyn_”, using lower case resulted in a messed up site and not possible to login using whatever user I defined locally.
The solution that worked was to manually update the database contents replacing “VYN_” with “vyn_” for all table references used.
Together with wp-config defining $table_prefix = “vyn_”, I’ve got it working at last…
Two reasons for this post:
- First I would like to help others possibly having the same issue.
- Second, it would be nice if this could be resolved in a next version of WordPress… (If this is the wrong location, please help with a suggestion for a better place.)
- The topic ‘Case-sensitive WP_Table_prefix’ is closed to new replies.