Last March 10th, I was busy migrating JaypeeOnline to MediaTemple and at the same time, I was waiting for WordPress 2.5 to be released. I was hoping it would be made available just in time for me to install and use it when I move to my new web host. Later it was announced that the scheduled release was postponed. I wasn’t disappointed because I know that the developers wanted to make sure that all the bugs are fixed and issues are addressed before it was released. We all want a stable and more secure version of WordPress, don’t we? There’s no definite date yet, but the developers are doing their best to have WordPress 2.5 available by next week.

Another good thing about the delay is that it gives us WordPress users, theme and plugin authors more time to prepare. Here are the changes in WordPress 2.5 that could affect the performance and functionality of some plugins:

  • Admin Menu Changes
  • Admin Screens
  • Activation Global Scope
  • Hook Changed: restrict_manage_posts
  • TinyMCE Upgrade to Version 3

For a more detailed description on these changes, check out this document on Migrating Plugins and Themes to WordPress 2.5. Also, if you want to check whether the plugins you’re currently using are compatible with WordPress 2.5 or not, go over and take a look at the Plugin Compatibility list.

So far, only one of the plugins I’m currently using has a conflict but unfortunately it’s one of my favorite plugins – the Tiger Style Admin. With too many admin changes in WordPress 2.5, this plugin won’t work any more. Too bad because I really like this plugin and I know many of you guys do too. Also, the Tiger Style Admin fix I posted last month becomes useless. I do hope the author would update it or someone would create a new admin theme just like it for the new version of WordPress.

If you can’t wait to get your hands on WordPress 2.5 or can’t wait to see how the new interface looks like, you can try and see it for yourself on this demo blog provided by Chris Johnston. Btw, the version of WordPress used for this demo blog is a beta version so some of the stuff you see could be different in the final version.

Lastly, to help you prepare and make your blog ready for WordPress 2.5, make sure you go over and read this WordPress Upgrade Preparation Checklist by Lorelle VanFossen.

Is your blog ready for WordPress 2.5? Have you updated your themes and plugins? Do you have any plugins currently installed that have issues or conflicts with WordPress 2.5? I’d like to hear your thoughts and opinion.

JaypeeOnline is supported by its audience. When you click on the advertisements or purchase through links on our site, we may earn an affiliate commission. Learn more

Share:

administrator

Owner and editor of JaypeeOnline. Self-proclaimed geek. New media writer and consultant. WordPress advocate. Loves blogging, gadgets, video games and sports. You can follow him on Facebook or Twitter.

12 Comments

  • JP Habaradas, March 18, 2008 @ 4:25 AM Reply

    @mr nice ash – How come? Is it because of the plugins you’re using? If that’s the case you don’t have to install 2.5 as soon as it’s released. You can work on your blog first and make it ready for this new version. If you need any help, let me know. ;)

  • mr nice ash, March 18, 2008 @ 4:20 AM Reply

    my blog is totally not ready for this. and that makes me not ready too… :(

    <em>mr nice ash's last blog post..Windows XP on Asus Eee now faster</em>

  • JP Habaradas, March 17, 2008 @ 6:15 PM Reply

    @jhay – Me too! I was hoping for it to be released last March 10th but it’s all good. I’ll also do the same and try it out first on my sandbox. :D

  • jhay, March 17, 2008 @ 6:12 PM Reply

    Can’t wait for WP 2.5 to come out. I won’t immediately upgrade but would play around with it in my demo blog. :lol:

    jhay’s last blog post..Frustrated with the Brother printer

  • JP Habaradas, March 15, 2008 @ 4:50 AM Reply

    @POYTSPOT – You mean you won’t install any newer versions of WordPress? Or you’re just talking about version 2.5? It isn’t advisable to use an old version of WordPress because it can be vulnerable to exploits.

    Thanks for stopping by! :)

  • POYTSPOT, March 15, 2008 @ 4:48 AM Reply

    Im sticking with wordpress 2.3 :mrgreen:

    POYTSPOT’s last blog post..Google Ad Manager: New way of advertising

  • JP Habaradas, March 14, 2008 @ 9:40 PM Reply

    @Joie – That’s a good idea. Actually, I also do the same thing and have a sandbox for testing purposes. That way, you would be able to check whether your theme and plugins work with the newer version of WordPress. :)

  • joie, March 14, 2008 @ 9:37 PM Reply

    I might install wordpress 2.5 in a subdirectory of my site with all the plugins that im using first before i will migrate. I had learn my lessons before.. :evil:
    thanks Jheppy for the post..

    joie’s last blog post..Pregnancy and Preparation

  • JP Habaradas, March 14, 2008 @ 3:05 PM Reply

    @trench – Haha, true! I still get worried sometimes but like what you do, I make sure I have multiple backups and deactivate all the plugins before I do the installation upgrade. :D

  • trench, March 14, 2008 @ 3:03 PM Reply

    Always scary but just back up, deactivate all plugins, and dive in! I do it all the time! LOL

    <em>trench's last blog post..Noooo! Kaba Modern in the bottom TWO!</em>

  • JP Habaradas, March 14, 2008 @ 9:15 AM Reply

    @sylv3rblade – Based on what I’ve seen from the beta version, the GUI of the dashboard has definitely changed but the design is not really exceptional. I hope the final release would be much better. If not then, I’ll just use an admin theme.

    A dummy installation is always good but some people don’t have the luxury to do that. Some don’t know how, while some simply don’t have the time. :D

  • sylv3rblade, March 14, 2008 @ 9:13 AM Reply

    I like the changes admin side but like before.. a dummy installation for me to test things around would be the thing for me though.

    sylv3rblade’s last blog post..Google search is drunk

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.