We’re migrating the Tarski site to a new server, so things may be intermittently broken. Please don’t panic, normality will be restored before too long.
Putting out a new release of Tarski involves a fair few elements: tagging a new release in Subversion, creating a zip file and moving that to the downloads directory, updating the changelog, writing a release post, and finally updating the version feed so that existing users get notified about the new version.
All this is an increasingly automated process: I still have to publish the release post and update the changelog manually, but pretty much everything else can be done with a couple of tweaks to a config file and one shell command:
rake tarski:update (actually you can just do
tarski:update is the default task).
You can now download my toolset from GitHub. Obviously to do so you’ll need Git, as well as Ruby and Rake to run it. If you have any questions, suggestions or bug reports, please let me know in the comments.
Just a quick note to say that I’ve finally got the Writing Plugins for Tarski documentation page in a usable state.
I’m very happy to have just uploaded Adam Klimowski’s translation of Tarski into Polish—the language of this theme’s namesake, Alfred Tarski. You can download it from our translations repository. Many thanks to Adam for that, as well as everyone else who’s provided a translation, all of whom are credited on the localisation page.
WordPress 2.4 has been cancelled, and we’ll be going straight to 2.5 in early March. Tarski 2.1 is being written for compatibility with that next version, and hence will be delayed until then too. Keep track of our plans for the release on the roadmap page (which has just moved from the ‘Help’ section to the ‘About’ section).
The major feature of Tarski 2.1 thus far is the move to entirely widgetised footers and sidebars. I’m in the midst of writing and testing an upgrade script to convert people’s current options to the new widget-based ones. If you have any comments or suggestions about that, please post on the forum. Patches, bug reports etc. should be posted on the issue tracker ticket for the changes.
I’ve updated the website with a link to the Tarski Subversion repository, specifically to the latest stable branch (which is what you should be using; 2.0.5 is the latest release from that branch). Hopefully more people will try using
svn to keep their WordPress and Tarski installations updated; it’s a little more work initially, but it makes maintenance far, far easier, as well as allowing you to take advantage of the latest security fixes, general bug fixes, and other improvements with the minimum of effort. There are a bunch of tutorials out there on this subject (for example, this one). If people are interested I can write up a quick tutorial on how I keep things up to date on this site.
Tarski 2.0.5 was initially slated as a pure bugfix release, but as with most things, it grew in the making. Details are in the changelog.
However, the most major features are the bugs fixed. To begin with, the navbar now reorders correctly, and no longer needs to save that order when pages are saved; more efficient and better-written code makes it all happen dynamically.
A problem with Tarski’s options saving and updating code was exposed by the new multiple authors checking instituted in 2.0.3, with the result that the save-and-restore no longer worked properly: restoring one’s options after deleting them would merely save the defaults to the database. The underlying issues have now been fixed.
On the new features front is one I know I’ll appreciate as I continue to improve Tarski: the code behind the version check is now a lot smarter. It used to just check whether the version grabbed from the stylesheet and the one in the database—now it can tell whether any given version is newer or older than the installed version, which lets us do things like show a notice on the Dashboard notifying the user that they’re using a development version.
Lastly, I appropriated some WordPress widget code to rewrite the recent articles section, with the result that it’s now added via an action hook,
th_fmain, and can consequently be removed by a plugin as well as through the Options page. The recent articles’ excerpts also have WordPress’ excerpt filters applied to them too, so any plugin which adds or removes those filters will now work as expected on Tarski’s excerpts.
Enjoy the new version; all being well, it’ll be the last before Tarski 2.1, but I wouldn’t bet my life on it.
Please post bugs and suggestions on the forum.
I’ve moved a couple of little plugins and templates onto our Subversion repository; you can find them in the extras directory. Hopefully this will make me more inclined to keep them updated—as they stand, they’ve been tested on the latest version of Tarski, but of course if you have any problems with them just post on the forum.
I wrote some
.htaccess redirects, so all the old links should be redirecting (if you find any broken ones, please let me know). Tarski 2.0.5 should be out early next week, with the usual bug fixes and enhancements.
There are a few more tweaks and bug fixes in Tarski 2.0.3, all of which are detailed in the changelog.
The update notifier has been the subject of a few improvements, including adding support for PHP’s own
file_get_contents function for people whose servers don’t have
libcurl installed. Its error handling has also been made more robust, so when required PHP components aren’t available it will let users know what the issue is and how to resolve it.
If you want to use images as links but don’t like borders, the new
imagelink2 image class will let you do that simply and easily.
There are a few text changes in this version, so if people could provide updated translations (shouldn’t take long) that would be wonderful.
Bugs and suggestions to the forum please.
Thus far Tarski’s wonderful translators have posted new translations for the following languages:
- Bahasa Indonesian
- Brazilian Portuguese
If you’ve done a previous translation for Tarski, I’d be very grateful if you could update it for the new version. If you haven’t, and you’re able to translate Tarski into a language missing from the list, why not have a go? All translations, both new and updated, should be posted on the forum. Cheers!