Unwakeable: The Future And WordPress 2.3

I’ve waited far too long to post an update on Unwakeable 2.0 and it’s status, so here it is, almost. First, I’d like to address the issues with the current Unwakeable release (version 1.2.1) and WordPress 2.3. There’s a few issues, although most of them are fairly minor.

1. Tags: Unwakeable 1.2.1 does not support the new tagging system in WordPress 2.3. If you’re using the new tagging system, your tags will not be displayed. Ultimate Tag Warrior still works just fine with Unwakeable 1.2.1 and WordPress 2.3.

2. Prototype: Livesearch (and probably rolling archives) don’t work with WordPress 2.3. I really have no idea why, it’s probably a combination of a few things. One major contributor is probably the fact that WordPress 2.3 likes jQuery instead of Prototype, and Unwakeable relies heavily on Prototype for it’s ajax effects, such as livesearch, rolling archives, and live commenting. I only use livesearch, so I can’t say for certain if rolling archives and live commenting were truly broken. All I know is Firefox CPU usage skyrockets when loading this site when livesearch is enabled.

3. Archives Page: The archives page is slightly broken, it displays an error similar to this at the top:

WordPress database error: [Table ‘tlongren_wordpress.wp_categories’ doesn’t exist]

That happens because Unwakeable 1.2.1 doesn’t know about the new taxonomy schema in WordPress 2.3. WordPress 2.3 does away with three tables, categories, post2cat, and link2cat. Those tables are replaced by three new tables that, when combined, offer much greater flexibility in handling post categories and blogroll categories. I think this new schema handles tags as well.

4.Tag Archives: This may be unique to this site, I haven’t tested, but whenever you try to visit a tag archive (my unwakeable tag archive for example), a 404 is received. Obviously, it should display all the posts with the given tag. Can anyone using Unwakeable 1.2.x confirm this is also broken on their WordPress 2.3 site?

5. Unknowns: There’s probably lots of broken things I’m not aware of. K2 Sidebar Modules may very well be one of them. I really doubt they work 100% because they make some use of categories. If you’ve got anything I’ve missed, please let me know about it so I can make sure it’s working in Unwakeable 2.0. One thing that DOES work that I entirely expected to be broken are the category archives. I was ready for all sorts of errors when trying to view a category archive, like the Unwakeable category archive, but they display exactly as they did with WordPress 2.2.x. Please let me know if you’re aware of any other incompatibilities between Unwakeable 1.2.x and WordPress 2.3.

Now that all that ugly broken stuff is behind us, let’s move on to Unwakeable 2.0 and where it sits currently and where it’s headed. This will probably take a while, so get comfortable. Anyway, about a month ago, I was days away from releasing Unwakeable 2.0 to the public. I had everything exactly as I wanted it and realized it would not work entirely with WordPress 2.3, as I explained above. WordPress 2.3 was still a couple months from being released at that time.

At that point, I stopped everything and took a fair amount of time to think the situation over. I even contemplated abandoning Unwakeable altogether, mostly due to my lack of free time. Anyway, I basically had two options (aside from ceasing development of Unwakeable), either fix the current Unwakeable code or re-build Unwakeable 2.0 from a more recent revision of K2. I knew the latest revisions of K2 were mostly (if not fully) compatible with WordPress 2.3.

I immediately upgraded this site to WordPress 2.3 upon it’s official release only to find that livesearch (and probably rolling archives) were horribly broken, as I described before. Luckily, K2 has been using jQuery since revision 382, Prototype is no longer required by K2. After I realized K2 was now making use of jQuery, I knew the best option for me would be to base Unwakeable 2.0 off a newer version of K2. That leads right to the current reason Unwakeable 2.0 has yet to be released, and that’s the current status of K2.

K2 release candidate 3 dropped earlier today, almost exactly a week after release candidate 2 became available. I’ve noticed a significant increase in the number of commits to K2 svn in the last month or so, indicating lots of work being done on K2. Because of this, I’m waiting for the final stable release of K2 to use as a starting point for Unwakeable 2.0. I should be able to release Unwakeable 2.0 in a matter of days following the stable release of K2.

I think Unwakeable 2.0 will be one of the most robust WordPress themes around once it’s released. K2 alone sports some great features, Unwakeable 2.0 will add to that feature-set. The combination of features should make Unwakeable irresistible to many bloggers.

Unwakeable 2.0 includes a number of style related options that can be set right from the options page. These will let you set various colors Unwakeable should use in the header and menu. The list of customizable style settings will only grow in future versions Unwakeable, assuming I get enough suggestions from Unwakeable users. I’m starting out with a fairly basic set of colors and options to configure, mostly items in the header such as the menu color and the menu color when the mouse cursor is hovering over it.

You can see the items that can be customized/styled in the image below, just click the thumbnail for the full size image. That screenshot was taken from my most recent test version of Unwakeable 2.0, still based off of the old K2. The final 2.0 release will be roughly the same. Have a look below:

Unwakeable 2.0 Customization OptionsI’d like to hear from actual Unwakeable users on what they’d like to be able to customize, I know lots of you go to great lengths to customize Unwakeable. My ultimate goal with Unwakeable is to give you, the user, the ability to style and customize as much as you want/need to right from the options page. Storing styling options in the WordPress database will save your styling settings when upgrading to new versions of Unwakeable. This will prevent the need to edit PHP code or modify the CSS code to get the color scheme and overall style desired.

Now, you may be asking yourself, “What’s the point when custom style sheets can be used?”. Custom style sheets, or schemas as they’re called in K2 and Unwakeable, allow users to create a CSS file to modify their blogs appearance. Styles are intended to allow you to keep the same color scheme and general style across many versions of K2 or Unwakeable, without the need to modify any of the CSS. You’d simply tell K2 or Unwakeable to use your custom style sheet, no matter what the theme version, to get your desired color scheme. This is a good solution for maintaining the same style when upgrading to a new version of K2 or Unwakeable. It prevents you from having to edit the themes core files, which may change from version to version. However, there’s a usability problem with using custom style sheets to maintain the same style. The problem is, many users do not know enough CSS to get the look they want, either that or they don’t care to spend the time creating a custom style sheet.

Unwakeable will give you an extremely easy to use, straight-forward interface for manipulating your blogs appearance. I am going to focus heavily on adding customizable style settings to the options page throughout the 2.x versions of Unwakeable. If you use a custom style sheet, fear not, K2 styles should still work in Unwakeable 2.0. Those of you currently using a custom style sheet should probably stick with the custom style sheet, it will give you much greater flexibility than the fairly simple options Unwakeable provides an interface for. It’d be impossible for me to add options that allow you to style every single piece of Unwakeable that can be taken care of with a custom style sheet.

So, all you Unwakeable users out there, please leave comments at this post or on the official Unwakeable page with what you’d like to be able to style or customize. It can be anything from customizing colors in a certain area of Unwakeable to choosing fonts to use for post titles or post content.

I can’t guarantee I’ll add your request to Unwakeable 2.0, but if I think others will benefit from it, I will do my best to get it into Unwakeable 2.0. I may push Unwakeable 2.0 out with it’s current feature set as soon as I’ve got everything built into a stable K2 version. If I do that, I’ll work on adding your requests to version 2.1, which shouldn’t be all that far behind the release of 2.0. If that ends up being the case, I’d suggest everyone who makes lots of style mods wait for 2.1 to come out, so all (hopefully) of your customizations will be saved, making future upgrades a breeze.

There’s a few other features that you’ll notice in Unwakeable 2.0, some of which I discussed in this post in August. One feature I think a lot of users will really appreciate is the option to use flexible page widths. Flexible page width can only be used when one sidebar is in use. If you’ve got two sidebars, the width basically takes up the entire width of the browser window, so two sidebars with flexible page width enabled would make the page wider than the browser window, causing visitors to have to scroll horizontally on your site to see some things on either sidebar. That may not be the case for people running @ super high screen resolutions, but when I run at 1600×1200, there’s barely enough room to fit everything on the screen without a horizontal scroll bar appearing.

One final thing, would anyone like to volunteer to test Unwakeable 2.0 in the near future? Things often work perfectly for me but seem to break under different environments. If nobody wants to volunteer, I’ll probably just release a public beta or something after I’ve got all the current features moved over to a stable K2 release.

As always, questions, comments, and constructive criticism are welcome and appreciated.


Well, now what?

Work with Me

I'm available for hire and always taking new clients, big and small. Got a project or an idea you'd like to discuss? Startup plan but no developer to make it happen? Just get in touch, I'd love to see if I can help you out!

Leave some Feedback

Got a question or some updated information releavant to this post? Please, leave a comment! The comments are a great way to get help, I read them all and reply to nearly every comment. Let's talk. πŸ˜€

Longren.io is proudly hosted by DigitalOcean


9 thoughts on “Unwakeable: The Future And WordPress 2.3

  1. Sounds good Tyler, I’ve pretty much come to a similar decision in the last couple of weeks after looking through some of the code in Redoable 1.x I really don’t want to go back there, and figure it is probably more beneficial to just use a later version of K2 as the base, especially considering the progress that they have made on it in the last year. Plus, by the time K2 1.0 is finally available I might have enough free time to put in proper work for Redoable 2

  2. Right on Dean. K2 has made some pretty drastic improvements in the last few months. I can’t ignore those improvements and can’t replicate them by myself in Unwakeable.

    It just makes more sense to start with K2 1.0 and start building from there.

  3. Well, I find unwakeable so good that I’m compelled to write down this big thanks Tyler for further developing it!

    Take it slowly if you want, but don’t stop. Ever.

  4. Can I sign up as a beta-tester πŸ™‚
    I really like your theme and would like to use it on my site.
    I am currently running WordPress 2.3 and K2 Release Candidate 3, so I have some experience with the K2 theme.

    Best Wishes

  5. Hi,

    Would love to be at beta tester.
    I am preatty good at CSS+xhtml
    I know PHP and some js.

    I have about 50+ blogs running K2, mostly the 3CK2 mod and this one isn’t being updated anymore.

    I don a lot of work for the danish WordPress community and love the gettext πŸ™‚
    Anyway I will make a danish translation

  6. Pingback: T. Longren

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.