Feb 162010
 

Today When I log in to WordPress, I saw a familiar wording on the top of Dashboard.

“WordPress 2.9.2 is available! Please update now.”


Without delay, I quickly browse to WordPress.Org to find out whether I need to upgrade to version 2.9.2. Here’s the words quoted by WordPress website.

Thomas Mackenzie alerted us to a problem where logged in users can peek at trashed posts belonging to other authors. If you have untrusted users signed up on your blog and sensitive posts in the trash, you should upgrade to 2.9.2. As always, you can visit the Tools->Upgrade menu to upgrade.

That also means that I do not need to upgrade my WordPress version 2.9.1 to 2.9.2 because I’m the only author for my own blog. Therefore, I will stay on my current version until next bigger upgrade.

However, if you have multiple authors in your blog, I will advise you to upgrade to the latest WordPress 2.9.2 because some untrusted registered users may exploit sensitive posts in your trash.

  5 Responses to “Should I Upgrade To WordPress 2.9.2 Now”

  1. I always upgrade to the latest version as I believe that stick with the updates is more secure for my website =)
    .-= MonsterBuzz!´s last blog ..Microsoft Windows Phone 7 Series Officially Unveiled =-.

  2. WordPress update are always handy but this update is useful for only those who have their registration open.
    I will wait for latest WordPress 3.0 which have WordPress MU capability.

  3. @MonsterBuzz: That’s a smart move to update to the newest version of WordPress to patch the security hole.

    @Theme Premium: I have the same opinion with you. I will wait for the bigger updates such as WordPress 3.0 because currently I’m the only author for this blog.

  4. No upgrade from me too.
    .-= Jayce´s last blog ..Download Swype v3.9 for HTC HD2 =-.

  5. Thanks for the info. I am getting the same update message but i gueess i do not need to upgrade.

 Leave a Reply

(required)

(required)

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>

By continuing to use the site, you agree to the use of cookies. more information

The cookie settings on this website are set to "allow cookies" to give you the best browsing experience possible. If you continue to use this website without changing your cookie settings or you click "Accept" below then you are consenting to this.

Close