Download Tarski 2.3

WordPress 2.6 introduced better support for a secure connection to the administrative area, which Ryan Boren covered pretty thoroughly in this article. Tarski 2.3 adds full support for this functionality, so you should now be able to save your Tarski options when using the admin area over SSL. However, due to the use of a number of new functions, WordPress 2.6 is a requirement.

A couple of minor security improvements have also been made. The Tarski options page can now only be accessed by users with the edit_themes capability. WordPress’ role system wraps around a capability-based user model, and it’s more secure to tie functionality to those capabilities than to roles which are more malleable.

As well as fixing a bug in the Links template, a number of tweaks have been made to improve Tarski’s performance and reliability. A long-standing problem with the upgrade process, where widget sidebar settings might be lost, has now been fixed. Tarski is also more reliant on WordPress’ own APIs, which should allow it to take advantage of performance and stability improvements made in the WordPress core.

In addition to this, the new navbar selector introduced in Tarski 2.2 is now fully compatible with Internet Explorer 6 and 7. There weren’t any reports of problems, presumably because Tarski users are more discriminating than the median internet citizen, but good cross-browser compatibility is a worthy goal nonetheless.

Thank you to everyone who tested the release candidates; I can only assume from the lack of responses that everything worked perfectly. Enjoy the new release.

Please post bugs and suggestions on the forum.

The usual caveats about pre-release software apply: don’t use it on a production site, run it locally or on a development server with a copy of your production database. If you have Subversion, you can get it from our svn trunk.

Please post any bugs or feedback on the forum.

In my view, the best part of this release is a vastly improved navbar selector. It’s a major improvement over the old implementation for a few reasons, firstly because it actually shows you the structure of your pages: they’re not just a big long list, but a properly indented tree that allows you to see just where in the overall structure of your site a given page fits.

Secondly, some people have a lot of pages. Until now, if that was the case, the navbar selector would utterly overwhelm the options page. Now it doesn’t have to: each sub-list is collapsible, so you can reduce the list to just what you need to see at any one time. I’ve found it a great help . Which lists are collapsed and which aren’t is saved in the database, so if you collapse a load of menus you won’t find them expanding out again next time you visit the Tarski options page.

Performance improvements have been gleaned by only loading Tarski’s library of administrative functionality when you’re actually using the WordPress admin page, not for every visitor hitting your front page. In addition to this, paginating archive and search pages is now the default, and the code that removes pagination and shows all the results for a given year, tag or search query has been reimplemented in a more optimised way that generally reduces the number of database queries required to generate the page by a significant number.

Additionally, changes in the WordPress core in version 2.6 has allowed me to deprecate a large chunk of Tarski code in favour of simpler and more elegant WordPress API calls. This makes the Tarski codebase more maintainable and also helps with performance. Removing a few unnecessary Tarski API hooks also helps with this.

Lastly, I’ve tidied up Tarski’s gallery and image support a bit so it fits in better with the gallery functionality added in WordPress 2.5 and updated in 2.6. Galleries should now be styled a little more nicely, and individual image pages are cleaner. Hope you enjoy the new version.

Support requests should go in the forum as usual.

Always back up your files and database before running a WordPress or Tarski upgrade.

It appears that options are now being automatically unserialised, which means that when Tarski attempts to unserialise the already-unserialised tarski_options object, an error gets thrown which breaks a bunch of stuff. All of which means, upgrade now, or you might potentially lose your Tarski options.

Tarski 2.2 is still in production, and will add some nice functionality as well as some performance improvements and a fair bit of tidying. I’ve backported a couple of bug-fixes from 2.2 to 2.1.4, so you don’t have to wait for them.

Issues with this release should be posted on the forum.