One Reason To Upgrade To WordPress 2.2
In my feedback post after upgrading to WP 2.2, Prudence, a fellow blogger, asked if it’s worth the trouble to upgrade. Though I replied “if it’s not broken, why fix”, this post I found at digg could be one good reason.
With no upgrade path for WordPress 2.1 blogs, users are being forced to upgrade to WordPress 2.2 sooner than expected due to a new attack that leaves your site vulnerable if you have your Admin user as user # 1 and your table prefix as WP_. But upgrade scripts exist that will allow you to perform this upgrade while backing up your site.
10 Responses to “One Reason To Upgrade To WordPress 2.2”
-
WordPress 2.2…
One Good Reason Why You Should Upgrade
With no upgrade path for WordPress 2.1 blogs, users are being forced to upgrade to WordPress 2.2 sooner than expected due to a new attack that leaves your site vulnerable if you have your Admin user as user # 1 an… -
[...] One Good Reason Why You Should Upgrade With no upgrade path for WordPress 2.1 blogs, users are being forced to upgrade to WordPress 2.2 sooner than expected due to a new attack that leaves your site vulnerable if you have your Admin user as user # 1 and your table prefix as WP_. [...]
Leave a Reply
Twitter
Tumblr
Facebook
LinkedIn
YouTube
I didn’t hesitate to go ahead and upgrade my WordPress installation right after version 2.2 was released. Having your WordPress up-to-date can save you headaches most if not all the time.
Btw, how did the blog tweaking go? Also, mind exchanging links? I’ve already added you to my blogroll a long time ago. Hehe
On Blog tweaking– am trying to figure if t’was a bug or one of the plugins are casing it. Any changes I effect to my sidebar, widgets and templates, it took 30 mins before you can see the changes. Do you have similar experience?
Your blog is now up in my grazr blogroll. Got to figure out first how to update it since I have not tweaked the babe for a long time
I see..do you happen to use the WP-Cache plugin? If not, try to delete your browser’s cache after you do the changes or tweaks and see if it fixes that. Other than that, I’m not sure what can cause it but I’m assuming it could also be with your DNS server.
Yes. I deactivated the plug in already. Will check if that fixes the problem.
Likewise, I have an issue on the “top commenter” plug in. It’s not suppose to show and count my comments but it does, deactivated it for a while because it appears that I am promoting my self. Any work around? Thanks.
So you were using the WP-Cache plugin? Most likely that would fix the problem. Anyways, are you talking about the “show_top_commentators” plugin? I also have that in my blog and I have no problems filtering myself. Here’s what you do, open the plugin file with your text editor and look for $ns_options = array, then under that you’ll find filter_users. If that field is empty, try filling it with “Administrator, admin, author_nickname” and see if that fixes it. Also, for the author_nickname, use whatever name you use under your admin user account. Hope this helps.
OK. Will do as you said. Thanks a big
Hi Jaypee,
(1) Disabling the WP Cache did not address the problem
(2) Tweaking the show_top_commentators plugin have successfully filtered my own comments!
Thanks
You’re most welcome!