I released Unwakeable 1.5 last night. This means Unwakeable is 100% compatible with WordPress 2.5! The previous version of Unwakeable, 1.2.1, didn’t play so nicely with WordPress 2.5.
Unwakeable 1.5 was built from the ground up using K2 r687 as a starting point. I decided to start fresh for Unwakeable 1.5 and scrapped pretty much all the code from 1.2.1. Unwakeable still has all the features it had in previous versions.
Advanced navigation and live search now work in Unwakeable. Unwakeable also comes with the K2 Sidebar Manager, a superior alternative to WordPress widets. You can enable the K2 Sidebar Manager or you can use WordPress widgets, either one will work. Or, if you don’t like sidebar managers, you can continue to modify the contents of sidebar.php to get the sidebar setup you desire.
You can download Unwakeable 1.5 from the official Unwakeable page. Please let me know of any bugs or problems you run into.
Popularity: 1% [?]
K2 Release Candidate 6 has been released. This release of K2 is fully compatible with WordPress 2.5.
I will be using K2 release candidate 6 as a base for Unwakeable 1.5. You can expect to see the release of Unwakeable 1.5 later on this week. You can download it from the official Unwakeable page.
Head on over to the K2 release candidate 6 announcement post for more details on the latest K2.
Popularity: 3% [?]
WordPress 2.5 was released on March 29th. The current version of Unwakeable (version 1.2.1) doesn’t play so well with WordPress 2.5. The only thing that’s really broken is the dashboard, which is a pretty big thing to have broken.
It seems there’s a known issue with K2 themes and the WordPress 2.5 dashboard, as explained in the K2 support forums. There’s supposedly a fix for this issue, but I could not get it to work fully. The fix works fine as long as you have K2 sidebar modules disabled from the theme options page.
Unwakeable 1.2.1 is so far broken and outdated I’m not even going to make an attempt at fixing it for WordPress 2.5. Instead, I’m working on Unwakeable 1.5, which is based off K2 Release Candidate 5. Unwakeable 1.5 is almost finished and should be up for download within a week, if not sooner.
Popularity: 8% [?]
K2 release candidate 3 was released a little over four months ago. Today, as I was going through all my feeds, I saw there were some commits to the K2 SVN. The log for one of the commits stated that the version for K2 has been bumped up to release candidate 5. Here’s a piece from the commit:
Author: Heilemann
Date: Mon Feb 25 22:57:53 2008
New Revision: 636
Modified:
trunk/style.css
Log:
Upped version to RC5. Preparing release.
This is rather exciting for me, especially the “preparing release” portion of that. I’m hoping “preparing release” means they’re getting ready to drop K2 1.0 as opposed to getting ready to release a download for K2 release candidate 5. As you probably know, Unwakeable is based on K2. Once K2 1.0 is out, I’ll start building Unwakeable 2.0.
Popularity: 12% [?]
WordPress version 2.3.3 has been released. This release, like the previous one, addresses an urgent security vulnerability that was found in the WordPress XML-RPC implementation. The flaw could allow any valid user on your blog to edit posts made by other users on your blog.
WordPress 2.3.3 also fixes some other minor bugs. If you don’t care about those minor bug fixes and just want to patch your blog against the XML-RPC vulnerability, you can download a fixed copy of xmlrpc.php and copy it to your WordPress installation directory, replacing the existing xmlrpc.php file.
You’re probably better off just downloading WordPress 2.3.3 and doing the full upgrade.
Popularity: 10% [?]
The WordPress folks have released WordPress 2.3.2, describing it as an urgent security release. This latest version fixes a bug that can be exploited to display your draft posts. Some changes have also been made to prevent certain error messages from giving away more information about your database than they need to. I would strongly advise that WordPress users install 2.3.2 ASAP.
WordPress 2.3.2 includes a new feature to allow you to customize the error page that’s displayed when WordPress can’t connect to your database. You can see the full list of changes between 2.3.1 and 2.3.2, you can also see which bugs are fixed in WordPress 2.3.2.
Head over to the 2.3.2 announcement post on the Dev Blog for the full story on WordPress 2.3.2. If you don’t care about any of that, you can just head straight to the download.
Popularity: 14% [?]
