Tarski 3.1 is now available for download. It includes sub-menu support in the navbar, together with JavaScript-enhanced dropdowns to display them. For a full list of changes please consult the changelog.
Please note that WordPress 3.2 is required for this release.
You can also get this version as a Git tag.
We strongly recommend following the upgrade guide. Always back up your files and database before running a WordPress or Tarski upgrade. Please ensure that you upgrade WordPress before installing the new version of Tarski.
Sub-menu dropdowns
This was definitely the most requested feature I’ve had in a while. I have some usability objections to dropdown menus, and played around with an alternative in the RC, but in the end I’ve gone for a more traditional approach. Mouse over the links in this site’s navbar for a demo of the new functionality.
Please note that they don’t work wonderfully well in Internet Explorer 6. If you want to use Tarski with dropdown sub-menus and you absolutely have to support IE6, I’m happy to commit any patches you provide.
Other changes
Apart from that, most of the changes in this version–although they are substantial–are under the hood, and involve cleaning up the code, removing deprecated functionality, and replacing Tarski-specific code with calls to new WordPress APIs. I’m always happy to be able to remove code without removing functionality, and I always feel that it’s a vindication when WordPress core implements some feature that Tarski has had for a while.
I should note that I’ve replaced all of Tarski’s JavaScript with new jQuery-powered code, and consequently those parts of Tarski now require jQuery. Given how widespread its use is now, and that WordPress itself depends on it, I don’t feel this is too onerous a dependency.
Finally, a small apology for taking so long to release this version. I’ve been really busy this summer and although the code’s been ready to go for ages, I couldn’t find time to run a final set of tests until today. As usual, if you spot any bugs please post them in the comments.