|
David Dadekian
|
February 6, 2015 at 11:04 am
The subject line says it, my site eatdrinkri.com is dead. I’ve tried to repair database both via WordPress and phpMyAdmin and I keep getting the error table wp_options doesn’t exist.
|
|
Josh
|
February 6, 2015 at 11:28 am
Hi David,
When it says the wp_options table doesn’t exist usually that means either there is a corrupt database table or it’s been dropped. Do you have a backup of your database that you can restore to?
|
|
David Dadekian
|
February 6, 2015 at 11:32 am
It looks like it’s been dropped, as odd as that may be. I have a backup from Sunday, but that was prior to doing EE update. Will that work?
|
|
Josh
|
February 6, 2015 at 12:29 pm
Hi David,
That will work, although any new posts, comments, events, and registrations since Sunday will not be in that database. However, you could export the options table from the backup and try importing in.
|
|
David Dadekian
|
February 6, 2015 at 12:39 pm
So I restored the backup with a different name, changed the name in the wp-config.php file and I get the following error message “Parse error: syntax error, unexpected ‘DB_USER’ (T_STRING) in /home/sounds9/public_html/eatdrinkri.com/wp-config.php on line 22”
I exported the options table from the db backup and tried to import it into the database that says the wp_options table is missing and the current database will not allow it. It doesn’t show up in the list of tables when I create it. It consistently gives me the error “Table ‘sounds9_eatdrinkriv3.wp_options’ doesn’t exist” regardless of whether I try to create a new table or import.
|
|
Josh
|
February 6, 2015 at 3:57 pm
Hi David,
I might be able to help you with the parse error. Can you double check that there isn’t anything extra or missing like a closing parenthesis, quote, or semi-colon? It should look like this:
/** MySQL database username */
define('DB_USER', 'your_username_here');
/** MySQL database password */
define('DB_PASSWORD', 'your_password_here');
/** MySQL hostname */
define('DB_HOST', 'your_hostname_here');
|
|
David Dadekian
|
February 6, 2015 at 7:26 pm
Thank you. I figured it out. For some reason my text editor, even though it’s supposed to be plain text, kept changing the single quote after my username into a styled apostrophe. Once I had that I was able to connect and copy the wp_options table back into my current database. Any idea why wp_options got corrupted like that?
|
|
Sidney Harrell
|
February 7, 2015 at 8:11 pm
I haven’t seen that, or heard from any of the other dev, testing, or support staff, and we’re all in constant contact. That’s something that definitely stands out and would be noticed. And from our dev-testing cycle, I’ve probably updated my testing sites 200 times to 4.6 before it was released, and I’m not unusual among the staff. Bugs still fight their way through, though, so we always recommend a db backup before performing any plugin update, whether it be our plugin, or even your theme. I would go further and recommend daily, automated db backups with a service. I think it’s basically free, or a couple dollars a month, and the load that it takes off your mind is definitely worth it.
|
|
David Dadekian
|
February 8, 2015 at 9:06 am
I had a backup, which is why I was able to restore just that table. I do a weekly backups with WP Backup as well.
This morning I awoke to a crashed MySQL server and the errors show a TON of transients from Event Espresso. I realize this is a different problem, but in the past there was a database “cleaning” tool Josh had given me to help with this problem. Is this still available. I don’t know if this was a problem in migration or what. Is there a way to do a clean install of EE 4.6 without losing all my previous event data?
|
|
Sidney Harrell
|
February 9, 2015 at 10:14 am
I think this is the one that you are looking for: https://gist.github.com/sidharrell/72762edc047fee9e4bed
That may actually explain what happened to your wp-options table, if your wp-options table is flooded with transients from bot attacks. Out of curiosity, have you had any success identifying the country of origin and blocking it with .htaccess?
|
