K2 Release Candidate 7 Released

This release fixes the bugs with SBM/Archives Page and WordPress 2.6. Subversion & nightly users: this release is revision 718. A list of bug fixes is here.

If you're using the K2 Sidebar Manager, you will need to turn it off in K2 Options before upgrading to K2 1.0-RC7. After you have upgraded to K2 1.0-RC7, copy k2-disable-widgets.php (found at k2/app/includes/) to your plugins folder and activate it. This applies to all versions of WordPress that K2 supports.

Download: K2 Release Candidate 7

Continue reading 'K2 Release Candidate 7 Released'

K2 Release Candidate 6 Released

K2 is now fully compatible with WordPress 2.5. It is still compatible with WordPress 2.2 and 2.3. Subversion & nightly users: this release is revision 678.

New features:

Download: K2 Release Candidate 6.

WordPress 2.5 Support Soon

The revision currently in subversion should support WordPress 2.5, so if you're in need of a new K2 for the latest WordPress release, go grab the latest nightly.

Meanwhile, Steve is hard at work at putting together a new release, which is right around the corner.

K2 Release Candidate 3 Released

Still some bugs to take care of, but Release Candidate 3 should cover your most immediate needs.

We cannot fix what we don't know about, and we won't know about it if you don't file a bug. And we do want to fix as much as possible. So, if you have a problem, first check the list of current bugs, if there isn't already a similar issue, file a new one.

Fixed Positioning for Rolling Archives

As per revision 513, once you've started digging into the archives on a site using rolling archives, and you scroll down, the rolling archives navigation strip attaches itself to the top of the page (try it here). This should remove the frustration of skimming through the archive pages and constantly having to go back to the top when you wanted to flip to the next page.

It might be interesting for those of you who plan to style to know just how this works. Well, it's quite simple; when you scroll, a piece of javascript checks if the top of the '#dynamic-content' container--which is where the content of your blog is kept--is being scrolled out of view. If it is, the class 'fixraposition' is added to BODY. The rest is CSS in css/rollingarchives.css.

I haven't tested this in IE yet, but in all likelihood it doesn't work. But then, what does?