Hi thanks for the clarification. I agree the problem was in the prefix, or lack thereof, of my database's wordpress tables.
I originally installed wordpress in Jan 2008 and have propagated the database all the way from 32-bit feisty to 64-bit lucid and, recently, precise. So sometime in the past 4 years the default 'wp_' prefix was set but didn't get applied to my mysql instance.
The fix that worked for me was to include $table_prefix=''; in my /etc/wordpress/config-default:
Hi thanks for the clarification. I agree the problem was in the prefix, or lack thereof, of my database's wordpress tables.
I originally installed wordpress in Jan 2008 and have propagated the database all the way from 32-bit feisty to 64-bit lucid and, recently, precise. So sometime in the past 4 years the default 'wp_' prefix was set but didn't get applied to my mysql instance.
The fix that worked for me was to include $table_prefix=''; in my /etc/wordpress/ config- default:
<?php
define('DB_NAME', 'wordpress'); 'DB_PASSWORD' , '***my* password* here*** *');
define('DB_USER', 'wordpress');
define(
define('DB_HOST', 'localhost');
$table_prefix = '';
?>
Incidentally only some of the wordpress tables have the wp_ prefix on my system.
mysql> use wordpress
Reading table information for completion of table and column names
You can turn off this feature to get a quicker startup with -A
Database changed ------- ------- --+ ------- ------- --+ list_config | list_future | ------- ------- --+
mysql> show tables
-> ;
+------
| Tables_in_wordpress |
+------
| commentmeta |
| comments |
| links |
| options |
| postmeta |
| posts |
| term_relationships |
| term_taxonomy |
| terms |
| usermeta |
| users |
| wp_email_list |
| wp_email_
| wp_email_
+------