Tarski 1.2.2 contains numerous bug fixes and tweaks to improve both Tarski’s stability and its flexibility.
The changelog has all the gory details, but here’s a brief run-down of the changes. Firstly, our wonderful translation team has expanded the scope of the Swedish, Dutch and German translations currently available to cover the Tarski Options page and a few other bits of text which were missed or omitted (by me, not them) during the initial localisation work.
As always we discovered our own needs exceeded what the software was capable of, so we’ve added several more theme hooks to allow the insertion of text or objects (adverts, for example) at the end of posts and pages, as well as the ability for you to write custom 404 error messages. Instead of just linking back to your front page you could link visitors to your archives or tag page, or include a search field.
This release should also be compatible with WordPress 2.1: we’ve updated various things like links listings and the navbar code to make them work with the new functions and database schema present in 2.1. If you find any incompatibilities between this release and WordPress 2.1, or that we’ve broken anything in WP 2.0.x, please let us know so we can get a patch out quickly!
Lastly, we’ve fixed a number of bugs and tidied up the code in various places. A number of little scripts have been made into functions and can now be found in functions.php, which leaves the markup skeleton a lot tidier and easier to read and amend.
Many thanks to all our contributors, especially our tireless translation team, and I hope you enjoy using Tarski 1.2.2.
Please post any bugs or suggestions on the forum.
Tags: 1.2.2, 404 errors, bugs, changelog, community, customisability, functions, futureproofing, localisation, theme hooks, translations, WordPress
-
[...] Subscribe to feed « Tarski Links Widget Updated • 1.2.2 Release » [...]
-
Awesome. Thanks.
-
[...] Hmmm. Do I go have some wild monkey lovin’ with my beautiful wife, or do I update my theme to the latest release? [...]
-
[...] Desde el blog desarrollo de Tarski anunciarón la versión 1.2.2 contiene varios arreglos para mejorar la estabilidad y flexibilidad de Tarski. [...]
-
Ben (Eastaugh) what are you finding with wordpress 2.1 and your recommended plug-ins?
I read that Brian’s latest comments didn’t work right with the beta version of 2.1 and also that there’s an issue with UTW, that when a moderated comment is approved, that wipes out the tags on the post and they have to be set all over again.
(Sorry if I should have asked this on the forum - it’s not exactly a suggestion or support request)
-
There are definitely UTW problems with 2.1, as evinced by Donncha’s post on the subject (and my own testing), and I’ve heard of the BLC problem too.
My advice would be to check the sites for all your plugins before upgrading to 2.1, and make sure they’re compatible. If they aren’t, and you want to upgrade your WordPress installation straight away, then I’d recommend temporarily disabling those plugins until new versions are released.
This blog hasn’t been updated to WordPress 2.1 yet, and won’t be until I can verify the plugins we’re using have been updated to make them properly compatible with 2.1 and not liable to break things unexpectedly. UTW has always been somewhat temperamental so conservatism is definitely the best course.
-
[...] För de som använder Wordpress så har Tarski nu släppts i version 1.2.2 som är kompatibel med Wordpress 2.1. Den svenska översättning (som också finns att ladda hem på denna sida) följer med som standard. get_calendar(); [...]
-
I downloaded and upgraded to the 1.2.2 and it works just fine.
No troubles at all.Nice one guys!
-
Oh good. That’s nice to hear. :)
-
Thanks for the advice, Ben.
I should have said - I downloaded 1.2.2. this morning and upgraded my blog to it and it went very smoothly.
There are a few things I’d changed here and there - I made those coding changes again and added my extra files (alternate stylesheet, template for a links page which is based on your links widget) and everything is working.
-
Actually I see that the version of BLC I use (1.5.8) is listed as working - it’s 1.5.10 that might be problematic.
And Donncha gives code that fixes UTW on the page you linked to (maybe that was added after you last read it)
Sorry to get off on this - it was because my next question after upgrading to a Tarski 1.2.2. - a WP 2.1. compatible theme - was, are my plug-ins compatible enough to try the upgrade to 2.1 yet?
-
Well, the short answer is “It depends which ones you’re using.”
Basically just check out the sites for the plugins you’re using and see if they have any information. I can’t give you much advice past that, I’m afraid.
-
the Codex has a running list of plugins that have already been checked, with version numbers and links. Kinda handy.
BTW, my Tarski seems great, the only tweak I have now is in the loop for some formatting I do to my tags and related posts. Everything else is in a custom stylesheet, the constants.php file, or the Tarski control panel, which makes it really easy to upgrade versions. Thanks for all your hard work!
-
Double Updates…
This site has had a double update to it.
#1: WordPress 2.1 has been released. Some new features have been added and other security updates as well.
#2: The Tarski theme has also been updated. This one also has some new features as well and is updated t… -
[...] been a long time since Tarski, i’ve been overusing K2. but hey why not? i’m downloading Tarski 1.2.2 as i speak (type ok fine…). maybe it’s because of my minor style for Tarski? heh, [...]
-
FYI, just saw this:
WordPress Theme Designers: If you have updated your WordPress Theme so it is WordPress 2.1 ready, please add your Theme to the list. If you know you will not update your WordPress Theme for the latest version of WordPress, nor future versions, please add your WordPress Theme to the list of non-compatible WordPress Themes. If you have updated your WordPress Theme and find it on the incompatible section of the list, move it up to the compatible section.
-
Yeah, I was meaning to do that earlier, only I can’t login to my Codex account for some reason (the lost password dialogue doesn’t seem to send anything to any of my active email accounts). Gonna have to make a new one, I suppose.
-
[...] 将我的Tarski Themeå‡çº§åˆ°1.2.2了。 [...]
-
fixed-ish…
Ok, everything here on the blog should be mostly fixed. Thanks to Alex, who has done the dilligent nit-picking that I require every time I upgrade or change things. Doing the upgrade has reminded me that I don’t redesign my blog on a whim becau…
-
I’ve been using the Tarski theme for several months now, and I was very pleased at how quickly you updated it to address problems introduced with WordPress 2.1.
I do have one small problem: I use Firefox at home, but the standard browser where I work is Internet Explorer 6. Just yesterday I noticed that ordered lists with more than nine items don’t display properly in IE. Here’s an example of what I mean. Once the the list hits item number ten, the leading digit is lopped off. Of course, Firefox has no problem, but in IE the numbers go 8, 9, 0, 1, 2… and so on.
I just disabled my custom CSS to ensure that it wasn’t something I’d done, but the list still rendered improperly in IE. I could probably tweak the padding in CSS to fix it, but I’m not sure how to do so without causing an unintended indent in Firefox.
-
How bizarre. Thanks for letting us know about the issue, I’ll try and address it for the next release (I can reproduce it myself, which is a good start.).
-
hi ! I got a strange bug using this theme. All the comment posted are shown only on the first post. I tried to post comment on a different theme and it works. The problems appears only on the Tarski theme. I donwloaded the latest version from here.
You can try to post here to see what I mean.
Note : this bugs happened on two differents blog using both the tarski theme, on two diferrent host.
Any clue ?
Thanks !
-
Please post support requests on the forum. My initial hunch would be that you’re using the widgets plugin and the ‘Recent Posts’ widget which has some conflicts with Tarski for reasons we’ve not yet been able to pin down (the issue is documented on our widgets help page).
Comments are now closed.
23 comments