Tarski 2.6 brings support for new WordPress features, improves the API, and makes the theme far more amenable to customisation via child themes. A detailed list of changes is available in the changelog. Please note that WordPress 2.9 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.
Better child themes
Child themes can now support their own custom headers and stylesheets. Simply create your child theme and add your new header images to the
headers/ directory in the child theme, rather than in your version of Tarski. The same applies to custom stylesheets. This makes Tarski child themes far more powerful, and allows you to keep all your Tarski customisations in a child theme rather than having to worry about backing up files stored in your Tarski directory as well.
Post thumbnails & image captions
Tarski now supports the post thumbnails added in WordPress 2.9, as well as properly styling the captions added to images in WordPress 2.6.
More customisable navbar
For those of you using the Tarski API to modify the navbar, a couple of enhancements have been added. Firstly, the ‘Home’ and page links are now added to the navbar via the
tarski_navbar filter, making it much easier to remove them if need be. Secondly, page and external links added to the navbar now have more meaningful array keys when they are passed to that filter, making them easier to manipulate programmatically.
Now in HTML5
HTML5 is the future of HTML, and using the HTML5
DOCTYPE in Tarski will make it easier to incorporate powerful new features in the future. There was a discussion of where this will lead in the comments on the 2.6 release candidates post.
As usual, there are many more tweaks, bug fixes and new features in Tarski 2.6 than I can go into here. Hope you enjoy the new version.
Please post bug reports, suggestions etc. on the forum.
Comments are now closed.