idreia

Just to report back the problem. And it is a bit on the embarrassing side…

My test system is running MS Vista 64, and my production system is Linux. So guess what, on Vista (and Windows in general) MySQL is case insensitive to table names…and on Linux it is case sensitive. So when I added my new code, for some reason, I camelCased the table name…which meant that it failed on Linux.

Mystery solved. Just a classic SNAFU from a careless programmer.

No, not sure what I would look for in the config file. This is a working WP site, it is just this one table is not found in the database. And as I have said, the table does exist and is read successfully at other times.

I wonder, the failure is happening during the dashboard display of a widget that calls wpdb to access the table…since WordPress is able to read the database table at other times this leads me to think it has something to do with the environment setup during a dashboard load.

Does anyone know of any restrictions for dashboard widgets when it comes to calling $wpdb->get_row?

I have been looking at this all afternoon and still cannot see why the code works on one machine and fails on the other. The database name is valid, the table exists, all other tables are working… So why all of a sudden would WordPress report the table does not exist?

I have turned on debug in WordPress and do not see anything unusual…

This makes me think that the table became corrupted somehow…

Any other ideas on things I might try?

In all other cases this is a functioning WordPress site. It is just this table that seems to be missing–even though it is created and has data within.