Title: raphk's Replies | WordPress.org --- # raphk [ ](https://wordpress.org/support/users/raphk/) * [Profile](https://wordpress.org/support/users/raphk/) * [Topics Started](https://wordpress.org/support/users/raphk/topics/) * [Replies Created](https://wordpress.org/support/users/raphk/replies/) * [Reviews Written](https://wordpress.org/support/users/raphk/reviews/) * [Topics Replied To](https://wordpress.org/support/users/raphk/replied-to/) * [Engagements](https://wordpress.org/support/users/raphk/engagements/) * [Favorites](https://wordpress.org/support/users/raphk/favorites/) Search replies: ## Forum Replies Created Viewing 2 replies - 1 through 2 (of 2 total) * Forum: [Installing WordPress](https://wordpress.org/support/forum/installation/) In reply to: [2.3 upgrade fails to complete](https://wordpress.org/support/topic/23-upgrade-fails-to-complete/) * Thread Starter [raphk](https://wordpress.org/support/users/raphk/) * (@raphk) * [18 years, 2 months ago](https://wordpress.org/support/topic/23-upgrade-fails-to-complete/#post-717531) * 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. * Forum: [Installing WordPress](https://wordpress.org/support/forum/installation/) In reply to: [2.3 upgrade fails to complete](https://wordpress.org/support/topic/23-upgrade-fails-to-complete/) * Thread Starter [raphk](https://wordpress.org/support/users/raphk/) * (@raphk) * [18 years, 2 months ago](https://wordpress.org/support/topic/23-upgrade-fails-to-complete/#post-717328) * A friend suggested forcing a database upgrade: * [http://codex.wordpress.org/FAQ_Installation#How_do_you_force_a_database_upgrade.3F](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. 🙂 Viewing 2 replies - 1 through 2 (of 2 total)