Thread Starter
raphk
(@raphk)
Turns out that all this (and more — blank line in RSS feed, zillions of rss_gibberish keys in the wp_options table, spam inserted into footer and header and index.php) was all because of the goro injection attack or the wordpress.net.in injection attack.
After many hassles, I am up and running at version 2.5.
Thread Starter
raphk
(@raphk)
A friend suggested forcing a database upgrade:
http://codex.wordpress.org/FAQ_Installation#How_do_you_force_a_database_upgrade.3F
…which I didn’t see the point of, given that said upgrade is exactly what was failing each time. But it did make me go look at the value of the db_version field in the wp_options table. Which was “1” instead of what it should be.
I changed it manually to 4773, and the upgrade link succeeded, and now it’s at 5183 (which is correct since we are currently running 2.2.3).
I will now try going to 2.3.3, and won’t mark this resolved until it makes it all the way there. 🙂
