After however months it’s been since our last release, Tarski 1.2 is finally here. Here’s the changelog, which gives details on the various fixes, tweaks and new features.
Since most people won’t want to trudge through the changelog, here’s a brief list of some of the major things we’ve added, many of them after user requests.
There are now links to next and previous entries in individual archive pages, so people can navigate from entry to entry. There’s also pagination support for posts and pages, so you can make multiple-page posts and pages.
Also included is the pagination of index pages (like category and date archives, the front page, and so on). This is completely optional: you can enable or disable it at will from the Tarski Options page.
There’s some under-the-hood stuff, like better trackback and language support (so that people can do translations: more on this later). We’ve also added more theme hooks, and done default styling for a number of additional HTML elements.
Styling & Markup
Two things in this release: firstly, we’ve added insert classes (see the contents listing on the Docs & Help page for an example) to let you add things like updates and menus without having to write your own CSS. I’ll probably write up a brief tutorial some time in the next few days.
Secondly, and more majorly, Tarski’s positioning markup has been substantially rewritten. This will most likely break some people’s custom styles, which is why I hesitated so long over making the changes, but I’m convinced that they will not only make it easier for people to write custom styles but that it will also make working with those styles a much more enjoyable experience.
The new code is more streamlined, more global, and better laid-out. I hope you’ll take advantage of the many improvements in 1.2, break your old styles, and rewrite them under the new system.
Experienced CSS coders will be able to evaluate the changes just by looking at the code, but here’s the executive summary, culled from the roadmap‘s notes on this change:
CSS Rewrite Notes
The plan is to replace the numerous, purpose-written
classes andids with a simpler, standardised system. The two basic building-blocks currently being worked on include acontentclass—for areas like blog entries, text widgets, the ‘about’ text, and so on—and a couple of positioning classes, probablyprimaryandsecondary, for the creation of floated columns.A fairly thorough pruning and re-organisation of the main
style.cssfile will probably be carried out at the same time. New documentation may be added to help people writing alternate styles to easily manipulate our styling system.
Localisation
We were going to wait, so we could include translations in this version, but we decided just to get 1.2 out there and release new versions as and when translations arrive. You can download the from our localisation page.
Please post translation submissions on the forum, it makes it a lot easier for us if support and modification stuff goes through there. Alternatively, if you’re feeling shy, you could email me with your work.
In Closing
Many, many thanks to our beta testers and the various problems they reported. Tarski 1.2 is undoubtedly a more polished release due to their hard work.
That’s all for now, ladies and gentlemen; we hope you enjoy using Tarski 1.2.
As always, post any bugs (and there will be some, despite the devoted efforts of our testers) on the forum.
Tags: 1.2, bugs, changelog, customisability, download, features, release, theme hooks
-
Trackback from ionfish on December 6, 2006 at 12:44 am
-
Pingback from Diario a Borbo · [Theme] Tarski 1.2 on December 6, 2006 at 9:57 am
-
Great work Ben and Chris!
I’ll get going on the swedish translation right away..
-
Pingback from gorgmorg · Tarskiert auf 1.2 on December 6, 2006 at 4:11 pm
-
Very nice! There just one thing that’s driving me potty: Where does
(more…)come from? I can’t find it anywhere in the code, but I want to have it replaced. -
I couldn’t find that string anywhere in Tarski, what’s the context is which you’re coming across it?
By the way, we did look into the Intypo issue and we’re fairly sure we’ve found the underlying cause, but not a solution (yet). Essentially Intypo replaces the English typography in the bits of text that go through WP‘s filters: post content, extracts generated from post content (not put in by the user), titles, and so on. Nothing else seems to get caught, whether it’s run through
wptexturize()or just generated by_e(). -
Perhaps the typography issue is something to be targeted in the WP core rather than by a mere plugin. Oh well, Western culture doesn’t depend on it.
This “more” thing appears where the <!–more–> tag has been inserted. In Tarski 1.1.3 and any other theme there is usually something like “Read on” given as clear text. That can be easily replaced by a localised wording. I did so with Taski 1.2 again, but to my astonishment “(more…)” appears instead of “Weiterlesen” or “Read the rest of this entry”. It seem to be coming out of the blue.
-
I’ve fixed up your code. :)
Figured out the problem, the aside loop has the “‘Read the rest of this entry »” text, the non-aside loop doesn’t. I’ll fix it and re-upload the 1.2 file.
-
Ben, ever thought about teaching major companies something about service? Some shares would rocket with your attitude.
-
Andreas, the new file should be up now. Can you check and see if that fixed it properly? Cheers!
-
Everything is just perfect now. Thanks a lot, Chris.
-
Hi there – I have just installed v1.2 and wondered if I could ask a quick question – probably really easy for someone there to solve but as an amateur I don’t have a clue!
On the navigation links that now appear above a single post, I’d really like to be able to right justify the one that takes you on to the next post (and leave the one for the previous post left justified), and get rid of the little blog in between! How would I go about doing this?
Thanks in advance for any help you can offer.
-
It’s a bit complicated—I did actually consider doing it that way, but the way I ended up going with is a lot simpler and degrades more nicely under stress (bumped-up text sizes, long titles, big disparities in title length).
If you post your request on the forum (I’ll forget about it otherwise), I’ll have a go at talking you through it.
Just to let anyone else who might be interested know, I posted a guide on how to do this.
-
I’m using UTW but since upgrading to 1.2 I’m not getting any tags on the frontpage, only at individual posts. Must be something somewhere in the loop, but where?
-
Yeah, that was an intentional change on my part; thought we had enough stuff on the index pages already. If you want to put it back, just add this line of code between lines
164and165ofloop.php:< ?php if(function_exists(UTW_ShowTagsForCurrentPost)) { echo ''; _e('Tags:', 'tarski'); echo ' '; UTW_ShowTagsForCurrentPost('commalist'); echo ''; } ?>
-
Thanx for helping me out.
-
A few issues.
When I changed over, the Site Admin link is part of the Navigation Bar. I want to get rid of that and just go to Site Admin directly. I can’t find an option to turn it off, nor the spot in the code that puts it there.
For some reason, I can’t get the constants to work with sidebar. I put it in li tags just in case it needed it, but no luck.
Finally, I can’t seem to edit widgets, such as text blocks… I click it and nothing happens.
I just came off using Canvas and back to the regular Tarski with the new update. -
Can you repost this on the forum please?
-
Wonderful theme … great job!
-
Upgraded with ease from the Beta and have no issues. Beautiful job guys.
Thanks
-
I couldn’t get the poEdit thing running, so I hard coded the German translation into the template files. There is just one thing I did not translate: “No comments” is just left blank.
Das Programm poEdit für die Anfertigung einer Sprachdatei läuft bei mir nicht. Deshalb habe ich die Ãœbersetzung direkt in die Template-Dateien geschrieben. Nur eine Sache habe ich nicht übernommen: Anstelle von “No comments” steht einfach nichts.
-
Fiddling the .pot-file I created a German .po-file. Just hope it works
-
Yeah, you just need to open up the POT file in a text editor really, that’s all there is to it. Thanks for that Andreas, I’ll check it out tonight.
Comments are now closed.
24 comments