1.2.3 Release

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: , , , , , , , , , , ,


  1. Helen’s avatar

    Ben, could you tell us which files changed? Or is the answer “pretty much all of them did”.

  2. Ben Eastaugh’s avatar

    I’ll try and keep better track for next time of which files change so I can post a definitive list, but for now I’d say update everything in the Tarski root directory, but don’t worry about the stuff in subdirectories like headers, images and JavaScript files.

    Here’s a list, from memory (i.e. knowing what we were tinkering with). It includes all the .php files because we changed the code for every include and @include to work around the problems people were experiencing on some server setups.

    • style.css
    • print.css
    • 404.php
    • archives.php
    • comments.php
    • footer.php
    • functions.php
    • header.php
    • index.php
    • links.php
    • loop.php
    • searchform.php
    • sidebar.php
    • tags.php
    • da_DK.mo
    • fr_FR.mo
  3. Mishkin’s avatar

    Just upgraded to WP 2.1.1 and Tarski 1.2.3 and everything’s working just fine.

    Good job as always!

  4. Helen’s avatar

    Thanks Ben. I upgraded and it’s working great.

  5. Jordan Liggitt’s avatar

    I’m using this release with WP 2.1.2, and the archives and tags pages are display 404 errors for anonymous users. I was able to fix it by changing post_status on those two pages from “static” to “publish”. I had to do that through the database… the pages didn’t show up in the admin interface until I did that. It seems like WordPress isn’t using the “static” designator any more.

  6. Ben Eastaugh’s avatar

    Did you actually create the pages using this release, or the previous one? We changed the database call for this release so it ought to have fixed it; if it hasn’t, we’ll have to tweak it again.

  7. Jordan Liggitt’s avatar

    I just downloaded the 1.2.3 version of the Tarski theme on February 25th… brand new WP install, theme install, database, everything.

  8. Jordan Liggitt’s avatar

    Yeah… just checked… functions.php, line 227, is still creating pages with ‘static’ status instead of ‘published’

  9. Ben Eastaugh’s avatar

    Is that in WordPress 2.1.x or 2.0.x? Either way, it looks like we’ll have to take another look at the code. Thanks for bringing it up.

  10. Chris Sternal-Johnson’s avatar

    Thanks, Jordan, that’s very helpful to know.

  11. David’s avatar

    Tried to sign up at the forum but no luck so far, so I’ll post it here in short:
    I love the Tarski theme. Thanks a bunch for making it available!
    Though I’m having some problems with the new version.

    When using the sidebar widgets and putting in ‘Recent posts’ the comments at my site go bananas. Things actually get stored with wrong IDs in the database.

    UTW behaves weird. Some posts seem to ‘lose’ their tags after a while.

    Just thought I’d let you know.

  12. Ben Eastaugh’s avatar

    Yes, it’s a known issue. We’re still not sure what’s causing it; it’s very strange.

Comments are now closed.