You are currently browsing articles tagged compatibility.

Tarski 3.2.0 adds the option to display a post’s featured image in the header. It also improves Tarski’s compatibility with recent versions of WordPress and PHP. A full list of changes can be found in the changelog.

Please note that WordPress 3.5 is required for this release.

Download Tarski 3.2.0

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.

Featured images in the header

Featured images let you customise how a post or page appears. Tarski now allows you to swap out the usual header image above the site title for a post or page’s featured image. This post shows the feature in action: it uses the ‘Splatter’ header image that comes with Tarski instead of the usual site header.

Other stuff

Apart from that, this is mostly a maintenance release. It cleans up a few bits of code and improves Tarski’s compatibility with recent versions of PHP and WordPress. Translators will be happy to hear that the theme POT file is now available with the source code.

Let me know in the comments if you run into any bugs. Hope you enjoy the new release.

Tags: , , , , , , ,

Tarski 2.2 improves Tarski’s compatibility with WordPress 2.6, tidies up various parts of the hooks API, improves performance, and adds a much cleverer navbar link selector. Details are in the changelog as per usual.

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.

Tags: , , , , , , ,

Advance notice: the next version of Tarski will require WordPress 2.1.x; I’ve outlined some of the reasons here.

April 1, 2007 by Benedict Eastaugh | 1 comment

Bugs bother us, so when they’re brought to our attention, we do our best to fix them. Tarski 1.2.3 is mostly a bug-fixing release, but I’m happy to say it comes with some new features too, albeit not of our making: two new translations, into French by Matthieu Mauduit and into Danish by Henrik Buchwald. Many thanks to both of them for their hard work.

The changelog is briefer than usual, but I like to think this is a good thing: there were fewer things to fix. A couple of them could have been classified as ‘tweaks’, specifically the Internet Explorer issues, but since they broke the proper display of some elements in that browser it seemed more accurate to call them bugs.

If we receive more translations before the next major version comes out, we’d be happy to release another iteration of the 1.2.x branch. All the details, as ever, are on the localisation page. It’s great that Tarski is now available in five languages (other than English), but we’d very much like to add to that. Various feature additions and amendments are planned to improve matters still further on this front, but if you have any suggestions don’t hesitate to post them on the forum.

Thanks again to everyone who’s helped us out with Tarski, particularly those who’ve contributed translations and brought bugs to our attention, and I hope you enjoy using Tarski 1.2.3.

Bugs and suggestions should be posted on the forum.

Tags: , , , , , , , , , , ,

So, 2.1 is finally out. Unfortunately we don’t have our companion 1.2.2 release ready yet (I’m away from home currently so it’s a bit tricky getting it all together), but it ought to be out in the next few days and should be fully compatible with WordPress 2.1 and the 2.0.x branch.

Ok, it’s out.

January 23, 2007 by Benedict Eastaugh | 24 comments

Tick Different is based on Tarski. Gorgeous colours combine into a dark, rich style—reminds me of expensive chocolate.

WordPress 2.0.5 will be out fairly soon, and as soon as the release version arrives we’ll be testing it to ensure Tarski’s compatibility.

October 27, 2006 by Benedict Eastaugh | 10 comments