
The situation:
I was able to upgrade from Wordpress 2.3 to Wordpress 2.5.1 couple of days ago.
The problem:
Everything went well until I found out that my hosting provider is blocking the IP address of my workstation everytime I am writing a new post. I informed my hosting provider about the problem and they were generous enough to unblock my IP address. However, I noticed that my IP is getting blocked everytime I am accessing post-new.php page and it will take me 5 to 10 minutes before my IP address gets unblocked after closing the post-new.php page. It was a bit different scenario compared to the total block I exprerienced previously.
The solution:
Downgrade Wordpress to 2.3.3 version, unfortunately, Wordpress seems to have no information about this. In this regard, I created a simple steps on how to downgrade your Wordpress installation in less technical ways below:
1. Do not delete your upgraded wordpress database.
2. Backup is not necessary, you don’t even need to restore your Wordpress database from your backup.
3. Delete all upgraded Wordpress files except wp-content folder, the files inside it and wp-config.php (temporarily renaming the files instead of deleting them is also a good practice e.g. index.php to index.php2)
4. Upload all the files extracted from Wordpress 2.3.3 ZIP file downloaded from Wordpress website.
5. Take note that Wordpress 2.5 has a new password hashing system, therefore you cannot login yet from your downgraded WP website. To solve this problem, go to http://your.blog.com/wp-login.php?action=lostpassword to reset your password.
6. Login to http://your.blog.com/wp-login.php after resetting your password and follow the last instruction.
YOUR WORDPRESS INSTALLATION HAS BEEN DOWNGRADED! HAPPY BLOGGING!
NOTE: I was in an infinite ping from the computer I am using to my website when I was writing this post and my IP address did not get blocked anymore. I don’t know what’s inside Wordpress 2.5.1’s post-new.php which is causing my hosting provider to block my IP address everytime I am accessing it, but downgrading to 2.3.3 has solved my problem.
Popularity: 5% [?]
| 2.5 |



































