1.7 Release

When WordPress 2.1 was released, we made the mistake of not having a compatible version of Tarski ready. WordPress 2.3—which will be out pretty soon—includes a number of changes which will be significant for Tarski users, and consequently we were determined not to make the same mistake twice. Tarski 1.7 remains backwards-compatible with the WordPress 2.1/2.2 branch, but it’s decidedly forward-looking. You can mull over the details on the changelog.

Perhaps the biggest change is the removal of our Ultimate Tag Warrior support in favour of the new ‘core’ WordPress tags system. Unless you’re running the 2.3 release candidate, this means your tags will disappear until you upgrade your WordPress installation and import your UTW tags. Tarski’s new tags page template, which you can see in action on our tags page, uses the new WP tag cloud.

While the overall goal of 1.7 was to make Tarski compatible with the new version of WordPress, we also took it as an opportunity to polish our code a bit and add a few helpful new features. As you can see by casting an eye up to the navbar, the ‘Home’ link can now be renamed. People have been asking for this for a while now, and I decided it was time to give in. You can change that on the Tarski Options page; look for the ‘Navigation Options’ header.

Speaking of the navbar, we’ve fixed an annoying issue where one had to re-save one’s Tarski options to get the navbar to reorder. It now reorders automatically whenever you save a page (since that’s when you change the Page Order value). The navbar output has also been added to the hooks system, which means two things: firstly, the constants.php file is now fully replaced (at least as far as it’s going to be), and that you can now add links to the navbar using a plugin. I hope to use this functionality to add a more elegant, user-friendly way to include external links.

The update notifier improvements in the last release have received a boost too, as the version check is now cacheable. To enable the cache, you need to make sure permissions on library/cache/ in your Tarski directory are set to 777. More details are available on the Update Notifier page.

For those who prefer to use a header image as their website title, and hide the actual title, I’ve improved the code so the alt attribute description is the site title when the title isn’t displayed, and the image itself links home (when you’re not on the front page, of course). A pinch of CSS means things should display as before, but the way things work is a bit more closely aligned with the expected behaviour (i.e., the site title links to the home page).

Category and author archives have had their first improvement in a long while: if there’s a description associated with them, they’re now displayed instead of the boring “This is a category archive for…” or “You are currently browsing so-and-so’s articles…”. So if you view my posts, you get a brief sentence about me instead of generic filler text. In addition to this, the document body now has an id which is set depending on which page you’re viewing, so you could make a particular author or category archive display in a certain way just by adding some extra code to your custom style. We’ve also assigned HTML classes to certain elements of the post metadata, so you can style those more easily.

As I detailed in my article on Tarski Plugin Integration, the support for specific plugins is now gone, so if you want to carry on using those plugins with Tarski I strongly recommend giving it a read.

Many thanks to everyone who helped me track down and fix the various bugs in Tarski 1.6; hopefully 1.7 won’t have the same problems. Enjoy the new version.

Please post bugs, suggestions and new translations on the forum.

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


  1. Detective’s avatar


    I really like this theme, i use it in my two websites :) It has a beautiful design and a beautiful code. Thanks for all your efforts.

  2. Ben Eastaugh’s avatar

    Thanks for the kind words, Eduardo.

    I’ve noticed a couple of small issues, mostly related to cross-version compatibility, so I’ll probably be bringing out a small patch in a day or so, once I’ve had the chance to review the code more thoroughly.

  3. Ben Eastaugh’s avatar

    Tarski 1.7.1 is out now, and it fixes the issues brought up in this forum thread, as well as another WordPress 2.3 compatibility issue.

    The files which changed between 1.7 and 1.7.1 were as follows:

    • library/options-page.php
    • searchform.php
    • loop.php
    • style.css

    Many thanks to the users who brought the bugs to my attention.

  4. Koen Colpaert’s avatar

    Hi there,

    First of all, thanks for this great theme. I use it on my website with some small modifications. I have 1 question: If I’m not planning on upgrading to WordPress 2.3 but want to remain in WordPress 2.2.1, will the UTW-plugin still work when I upgrade to Tarski 1.7.1 (currently on 1.6.2)?
    This is not a big issue since I value the theme more than the plugin ;-)

  5. Ben Eastaugh’s avatar

    I addressed this more fully in my article on Tarski plugin integration, but the short answer is no.

  6. Mohamed’s avatar

    hello Ben I want to ask you something ,
    the wordpress 2.3 is going to be released in the 24th of September .
    when do you think you can the release the compatible version or the 1.7.1 would be just fine considering that the 2.3 beta 3 would be almost the same as the final release .

    also another question , I’m probable one of the first people to use this , i have download and translated back in march of 2006 . but i always had problem with switching the word direction (from right to left) … that always result a problem with the feed icon and mixing it with words , in 1.1.1 the problem appears in firefox , now in 1.7.1 appears in IE

    regards :)

  7. Ben Eastaugh’s avatar

    1.7.1 will be fully compatible with WordPress 2.3.

    To switch the word direction you need to follow these instructions and set $text_direction = 'rtl'; in your language PHP file.

  8. dinsan’s avatar

    Thanks for the theme…… most well managed themes that I have ever seen.. changed to it very recently.. any way to add random image header for this ?

  9. Ben Eastaugh’s avatar

    Yes, a plugin could do that fairly easily. Various ways of doing it were mooted in this forum thread, although as that discussion predates our current theme hooks system, you’d need to integrate those ideas into a plugin along the lines of the one I described here (replacing the Flash stuff with a script that rotated between images).

  10. dinsan’s avatar

    anyway to get this as a plugin ?
    coz I tried the plugin available and also code .. but it doesnt seem to working since we already have something different on the codes about the header.. a few extra options

  11. Ben Eastaugh’s avatar

    There isn’t one available as far as I’m aware; you’d have to write it yourself.

  12. dinsan’s avatar

    thats going tobe real tough even if I have try ;) coz I have never done that… hmm let me see.. I want to update it to 2.3 first and then I will try updating the code :) thanks for the support

  13. Ben Eastaugh’s avatar

    1.7.2 is now out with a couple more bug fixes.

  14. dinsan’s avatar

    upgraded !! thank you so much Ben !! I have started suggesting this theme to my friends ;) good job keep up the good work.. ( and try to add the random image header option tooo :P )

  15. ???????’s avatar

    Tarski 1.7 remains backwards-compatible with the WordPress 2.1/2.2 branch

    So u mean that if I don’t want to upgrade my wp from 2.2.3 to 2.3 temporarily, I just update my Tarski to 1.7.2 it won’t break my UTW and everything else?

  16. Ben Eastaugh’s avatar

    It won’t break UTW, but it won’t display the tags either as 1.7 removes the support for specific plugins. I detailed this quite comprehensively in my article on Tarski plugin integration.

Comments are now closed.