WordPress 3.1 was released couple of days ago with much fanfare and as usual its loaded with improved features, new features and fixes that were reported in previous releases. Matt, Founder of WordPress himself has proclaimed this release as the best release of the World renowned content management system.

There’s a bucket of candy for developers as well, including our new Post Formats support which makes it easy for themes to create portable tumblelogs with different styling for different types of posts, new CMS capabilities like archive pages for custom content types, a new Network Admin, an overhaul of the import and export system, and the ability to perform advanced taxonomy and custom fields queries. With the 3.1 release, WordPress is more of a CMS than ever before. The only limit to what you can build is your imagination.

Believe me or not, this new release will mean a lot to developers than publishers for couple of reasons -

  • Awesome new features – WordCast Team has written a fantastic blog post on WordPress 3.1 and have explained the new features nicely. Check it out to know more about WordPress 3.1. These new features will allow developers to extend and communicate with WordPress to develop rich content sites easily!
  • Support requests – Well, This is something for developers and WordPress users alike. As you have noticed that WordPress 3.1 has got loads of changes in the way Posts are handled; a reason why loads of users are facing problems with broken plugins and themes as soon as they upgrade to WordPress 3.1. Developers should release the fixes as soon as possible by referring to the changes they’ve made. Thankfully! WordPress team has always been awesome with the documentation, so as a developer you should not have much problems.

How do I check if my theme/plugin will work with WordPress 3.1?

Normally, you don’t get issues of broken themes & plugins with WordPress upgrades. With major releases, it makes sense that we don’t upgrade on production/live environment and rather create a test environment and then check if everything works fine or not. Our clients faced issues after the upgrade, although they were quick fixes, their site was down and was giving errors while we were fixing the bug.

I would suggest that one should clone their blog on a test location and then follow the upgrade procedure or try to upgrade it automatically through WordPress auto upgrade feature.

3 Comment

Featured Designs

Parent Society

Parent Society

Marijuana Maps

Marijuana Maps

Cake Journal

Cake Journal

CopyKat Recipes

CopyKat Recipes

Jessica Denay

Jessica Denay

Keith Ferrazzi

Keith Ferrazzi

Rennaissance Yoga

Rennaissance Yoga

Brink Zone

Brink Zone

Illustrious Author

Illustrious Author

Boca Care

Boca Care

KingsCast

Kingscast

Notecook

Note Cook

My Business Musings

My Business Musings

3 Responses so far | Have Your Say!

  1. Yeah, I have had quite a few small annoyances since I upgraded to WP 3.1. The major one where jquery slider stopped working, which you guys fixed for me! I still have some issues like image alignment not working properly. I just wish WP guys educate the developers and publishers about the changes they are making before releasing the final version.

  2. Still i don’t have upgrade my wordpress because still i am busy to read its review. But I feel that I must be upgrade now. Thanks to update.