Well that took longer than first anticipated. Originally we meant to make 1.1 ‘merely’ an update for translations, but somewhere along the line it grew into something considerably bigger. In fact, had we not already settled on 1.1, I think calling this a 1.5 release would probably be more in tune with the changes within.
- Updated inline documentation throughout.
- Complete simplification and re-cajiggering of HTML structure and class and ID names. This is likely to screw up your existing child themes. Beware.
- Permalinks for Rolling Archives and livesearch (finally).
- Rolling Archives now caches 5 pages to either side of its position for faster navigation.
- Configuration of amount of widget containers (thus sidebars) is now automatic, depending on whether they are active or not.
- Added ‘Below Page Header’, ‘After Posts’ and ‘Page Footer’ widget areas.
- WP media manager’s horrible embedded CSS is now removed by K2.
- Cleaned up the options page.
- Support for WordPress 3.0: Multi-sites, the menu system and custom backgrounds.
- Removed various deprecated functions.
- Removed our styles sub-system entirely. Use child-themes instead.
- Single attachments, shown with image.php, have been updated.
- Option to disable K2′s styling (style.css), for more control and much nicer child theme CSS.
- Automatically resizes the smallest of the large YouTube embeds (560px wide) to 500px width (to cancel, remove/overwrite k2_resize_embeds() in your child theme).
- Added support for using k2-loop-category-<slug>.php
- Added option to use the page name when page is selected for home.
- Removed asides functionality (use semantic class, CSS and plugins instead).
- Added styling for the visual editor in the admin.
- Added comments pagination.
- Moved ping- and trackbacks inline with comments.
- Check to see if a version of jQuery later than the one we ship with (1.4.2) has been registered and don’t overwrite it. This really ought to be native to WP.
- A plethora of bug fixes and compatibility tweaks.
Go get it and let us know if it breaks. Meanwhile we’re on the brink of locking localization strings for the translators (the .pot has been updated, and we will do our utmost to not change any strings between now and 1.1, so you should be safe).
Did I mention K2 now supports twenty different languages!?
Important: This release contains significant changes to… well, everything. Backup your database, just to be on the safe side. We haven’t seen any wonky behavior, but on the other hand we won’t be held responsible if it kills you kitten either, so…