It’s that time again! It is time to upgrade your wordpress. What are we updating to this time? At the surface, nothing seems to be different. It is usually like that with minor 1 release. So what was changed? Actually a whole bunch of stuff. Nothing too major and no security releases. But what this does is finally let all the people who were afraid to download the new version now be able to do with confidence. So do it already!
Lets do the rundown of the bugs and features.
New Features
Database Upgrade
The database got an upgrade. It of course, tells you nowhere what it did. I am still trying to find it.
Child Themes Can UN-Register Menus.
If you are piggybacking off of any theme or framework, you can now un-register that menu position, and then of course, register your own! You can do this in the functions.php file of your child theme.
Tenty-Ten Enhancements
They seem more like preferences, but I’m not arguing. They first allow attachment images to be centered. No problem. No big change there.
The next is the theme description. Instead of just saying the default theme, they decided to bloat it with a bunch of garble. It is now as follows:
The 2010 default theme for WordPress is stylish, customizable, simple, and readable — make it yours with a custom menu, header image, and background. Twenty Ten supports six widgetized areas (two in the sidebar, four in the footer) and featured images (thumbnails for gallery posts and custom header images for posts and pages). It includes stylesheets for print and the admin Visual Editor, special styles for posts in the “Asides” and “Gallery” categories, and has an optional one-column page template that removes the sidebar.
No big deal, seeing as most people don’t really read that stuff anyway.
The next is stylesheet cleanup. That I am all for because it removes unnecessary code and allows for faster load time. You’ve got my thumbs up here.
Disabling Table Upgrades
When you are upgrading your wordpress, if necessary, it also upgrades your database that holds all of your information. That isn’t really a big deal, right?
What if you run MU? What if you have thousands of users and thousands of posts? Then it becomes a problem. It is resource intensive and can sometimes mess up your database. This really isn’t an option for everyone, but it is an option with the bigger blogs out there. The tech guys are breathing a sigh of relief right now.
Bugs
50 misc. bugs were squashed in this release, some minor, some major omg bbq.
Export Errors
One of the biggest errors was the exporting error. If you paid attention during upgrade, you will see that they threw out all of their built in exporting options and replaced them with plugins instead. People just didn’t use it enough. Well something kinda went wrong in that world, and when you exported, it threw a bunch of code junk your way. Well, they fixed it. Not really a whole lot more to say to what.
IPad
If you were making comments on your IPad, well, you weren’t. The safari browser on it didn’t recognize a visual editor in your commenting as a field to type in, so you were up a creek. They fixed this with the not well documented, but very cool, $is_iphone variable and you were commenting away in no time!
Misc. Others
They covered other things in the patch including visual UI fixes, typos, tag fixes, Class problems and dead code. All in all, a good release, but mostly maintenance. No real security issues dealt with here. Which is good.
Until next time!
Resources:
Notes:
- any release that looks like x.x.1 ↩
