This is scheduled to be the last release in the 1.9 branch, unless there are high priority bugs found that need to be fixed. What this means is that the development effort will be refocused on the 2.0 release, which hopefully won’t take quite as long as 1.9.5 did.
The main focus for the 2.0 release is a new plugin model that promises to be a major improvement over the current one and a custom MembershipProvider using the .NET 2.0 membership APIs. Of course, we are always looking at refactoring and code cleanup to help improve the stability and maintainability of the code base as well.
The new features included in this release are:
- Content Tagging and Tag Cloud - for more details, refer to this post.
- Identicon Support - Uses the Identicon Handler project on CodePlex.
- MyBrand Feedburner Support - Updated our FeedBurner implementation to support custom feedburner URLs
- Upgrade to LightBox 2.0 - If you referenced the default lightbox skin in your custom skin, please reference this post by Simone to understand how to update the skin.
- Author CSS Class - The CSS class of “author” is added to comments left by the owner of a blog (must be logged in when leaving comment for this to work). This allows custom skin authors to highlight comments by authors.
- Credits Page - In the Admin section, we give credit where credit is due, displaying a list of the open source products we make use of in building Subtext.
- Implemented ASP.NET AJAX - We replaced MagicAjax panel with ASP.NET Ajax libraries. Keep in mind that this requires a bit of new Web.config configuration sections. So be careful when merging your Web.config changes.
A partial list of bug fixes is here:
- Metaweblog API getRecentPosts method does not send categories
- Host Admin edits wrong blog host when not on page 1
- Recent Posts control wrong URL
- FeedBurner doesn’t allow the / character, though it should
- Comments allow unclosed tags
- Fixed up CSS issues for several Skins
- MultiBlog Caching Issue - Posts from one show in another - This bug bears special mention as it was a real pain to track down the root cause.
- Fixed issues with case sensitive databases
- …and others…
Now I just need to wait for GeeksWithBlogs to upgrade…