The forum will be there for you to get connected with each other, to get and offer support and to simply talk about all kinds of Kirby-related topics. I hope it will become a great place, where we all can discuss and exchange ideas, where you can hunt me down for bugs and which will hopefully become some kind of Kirby-community-brain.

Forum Threads

General
Pretty much anything that won't fit into the other threads.

Issue Tracker
Found a bug? Submit it here!

Extensions
Got an idea for a plugin, or you've created a new snippet? Tell us about it!

The Panel
Especially while the Panel is still in beta, this is the place to submit your feature requests, issues or anything else, which is related to the Kirby Panel.

Job Board
You are looking for someone to help you with a Kirby project?
You are a developer, who's looking for work? Get connected here.

Anything missing?

Do you feel like a thread is missing? Anything else you want to discuss in the forum? Please let me know: bastian@getkirby.com

How can I join?

Anybody, who's got a Twitter account can login to the Kirby Forum The good thing: you don't need another account and I don't have to store your passwords on the Kirby server.

Built with Kirby

The Forum is entirely built on Kirby – no forum software involved.

It's a simple plugin, which will be available for all Kirby users soon. It uses regular Kirby content folders for threads, the same plugin, templates and snippets system and a MySQL database for topics, users and posts. You can add it to any existing Kirby page or build a dedicated forum site with it. Stay tuned for updates!

Get started

As you will see, the forum is still pretty empty. So please don't be shy and start your first topics.

It's also still a very early version of the forum extension, so please let me know if you run into any bugs.

Can't wait to hear what you think about it and to read your first posts.

Cheers, Bastian

It's bascially the entire Kirby API on two DIN A4 pages.

I hope you like it and it will help you to get stuff done faster with Kirby.

Download

You can download the latest version from Github

How to update

Updating is easy. Download the latest version and replace the old panel folder with the new panel folder. If you have modified the .htaccess inside the panel folder, make sure to not replace that one.

Docs

Check out the Panel docs and please let me know if something is not understandable or missing.

What's new

Edit file metadata

You can finally add and edit any kind of metadata for files.

The cool thing: you can setup the form for metadata in the same way, you can setup the content forms in your blueprints:

fields:

  title: 

    label: Title

    type:  text

  text: 

    label: Text

    type:  textarea

    size:  huge

    

filefields:

  title: 

    label: Title

    type:  text

  caption:

    label: Caption

    type:  textarea

Just add a second field definition – called filefields – below the standard field definition. There's only one limitation. You can only use text fields and textareas. Buttons, required fields, field validation and different field sizes are not available yet.

This will still give you some great flexibility to come up with file metadata just the way you need it.

iOS Drag & Drop Sorting

The genius @robrainfall has sent me the link to a great plugin for jQuery UI, which makes it possible to have drag & drop support for sortable lists on iOS devices (iPad, iPhone, iPod) This has been the missing puzzle piece to offer full support for the Panel on the iPad. You can now sit on your couche and update your Kirby-powered website from your iPad!

New Checkbox and Multicheckbox fields

With the great support from Luzi Humm there's now a breand new checkbox field, which you can add to your Panel forms. Blueprint setup for this is super easy:

mycheckboxfield: 

  label:   My super awesome checkbox

  type:    checkbox

  default: on

This inspired me to create a new Multicheckbox field, which you can use to provide multiple selections – for example for categories:

categories: 

  label:   Categories

  type:    multicheckbox

  default: design, photography

  options:

    design: Design

    photography: Photography

    architecture: Architecture

I think both new field types will come in handy in many situations and I'm happy they are here now. If you are still missing an essential field type, please let me know.

Multiple Templates

In your blueprints you can set, which templates subpages should/must have. So far you had the option to either let the user decide or to define a single template, which will be used for all subpages. Now it is possible to define a set of templates, which will give you way more flexibility:

# blog blueprint



title: Blog



pages: 



  template: 

    - blogarticle

    - blogfeed



  sort:  flip

  limit: 10



fields: 

  …

You can add any number of templates to the list and the Panel will automatically create a selectbox out of it:

Feedback

I think it has been very important to add those new features and I'm very happy that they are finally here. I'm excited as always about your feedback.

The final launch of the Panel is drawing nearer. YAY!

<title><?php echo html($site->title() . ' – ' . $page->title()) ?></title>

…or…

<title><?php echo html($page->title() . ' | ' . $site->title()) ?></title>

…just however you prefer.

But what if you want to have a very descriptive title for your homepage or just the site title, without adding an extra template for it?

Kirby has the built-in $page->isHomepage() function, which makes it fairly simple to change your title only on the homepage:

<?php if($page->isHomepage()): ?>

<title>Welcome to my fantastic, awesome, little website</title>

<?php else: ?>

<title><?php echo html($site->title() . ' – ' . $page->title()) ?></title>

<?php endif ?>

…or maybe just…

<?php if($page->isHomepage()): ?>

<title><?php echo html($site->title()) ?></title>

<?php else: ?>

<title><?php echo html($site->title() . ' – ' . $page->title()) ?></title>

<?php endif ?>

You can get the latest version on Github:
https://github.com/bastianallgeier/kirbycms/tree/multilanguage

It works exactly like the default version of Kirby and has only a few adjustments. So if you want to use it for an existing project, all you need to do is to replace the old kirby folder with the new kirby folder from the download.

Otherwise just get started with the Multi-Language version as you would with the regular version. If you need more help, please refer to the docs

What is it all about?

With the Multi-Language version of Kirby, you can easily creat multilingual sites without any effort. It's as easy as adding another text file for each language to your content folders:

How to activate multi-language support?

Go to site/config/config.php and activated multi-language support like this:

c::set('lang.support', true);

c::set('lang.default', 'en');

c::set('lang.available', array('en', 'de'));

c::set('lang.detect', true);

If you are updating from an old version of Kirby, add those lines to your config, because they won't be there yet.

lang.support

As soon as lang.support is set to true, Kirby will automatically start to generate language-specific URLs like:

http://yourdomain.com/en/blog/article-xyz

http://yourdomain.com/fr/blog/article-xyz

http://yourdomain.com/de/blog/article-xyz

lang.default

With lang.default you define the default language code, which will be used if no language has been selected yet. It will also be used as a fallback when there's no translation available for content in a different language. This means that you can safely use all the content variables, even if you haven't translated all of them. If there's no translation you will get back the version from your default language.

lang.available

Set lang.available to define all available translations. Those language codes correspond with the language codes you will use as appendix to your content filenames.

lang.detect

When lang.detect is set to true, Kirby will try to detect the user's language from the user agent string and will try to redirect them to the best matching version of your site.

Multi-Language Content Files

To translate your content, all you need to do is to duplicate your content text files and add the language code as appendix (before the file extension). For example if your content text file for a blog article is called article.txt, duplicate it and create translations like this:

article.de.txt 

article.it.txt 

article.fr.txt

You can decide if you want to add a language code to the original file as well. Otherwise it will be considered as English if your default language is set to en or whatever you set your default language to.

Creating those translation files is optional. You won't break anything if they are not there. You will just not get a translation :)

site.txt

The site.txt can be translated in the same way:

site.de.txt

site.it.txt

site.fr.txt

Static Language Variables

If you need site-wide translatable variables, you can either put them into site.txt and its translations, or you can do the following.

Add a new languages folder to your site folder. Add additional PHP files for each language. For example:

site/languages/en.php

site/languages/de.php

site/languages/it.php

site/languages/fr.php

Define your site-wide translatable variables in those files like this:

<?php



l::set('next', 'weiter');

l::set('back', 'zurück');

l::set('ok', 'ok');

l::set('cancel', 'abbrechen');



?>

You can now use them in your templates, snippets and plugins like this:

<?php echo l::get('next') ?>

The Panel

The Panel already has support for the multi-language version, so you don't need to update that if you run Panel 0.6 As soon as you switch on language support a select box should appear in the Panel sidebar.

Missing stuff

The preview should be pretty stable, but there are a few missing things, which I need to add in the next weeks.

If you are using additional content files to add captions or other meta info to your images for example, there's no way yet to translate those.

I haven't found a good way yet to translate URLs. As you know all URLs in Kirby are built by the structure in your content folder. This means that you can't translate:

http://yourdomain.com/en/about-us

…to…

http://yourdomain.com/en/ueber-uns

…for example.

This might be a minor issue in many projects, but in some you might really need that. What you can do so far is to use mod_rewrite to rewrite those URLs manually. But that's not very comfortable of course. If you are a developer and you got a suggestion how to solve this best, I'd really appreciate your help. I want to get this right without bloating the system.

Do you like it?

It's really important to hear what you think about it and if there are ways to improve multi-language support.

It's been a while since the last release, because I put a lot of time into the Kirby Panel But I'm happy to announce that the new version has a few great new features – and of course some bug fixes.

New Features

Markdown Extra

It's been a very popular request to have support for things like tables, footnotes and other features of the famous Markdown Extra class by Michel Fortin. So far Kirby used the standard PHP Markdown class, which offers great support for all common Markdown features. It was possible to replace that class in the Kirby core, but it was more of a hack and whenever you wanted to update to a newer Kirby version, the Markdown Extra class would be replaced by the regular class again.

With the latest version, all you need to do, to get Markdown Extra support, is to switch it on in site/config/config.php

c::set('markdown.extra', true);

files::filterBy()

You were able to filter pages by fields for quite a while. For example to filter pages by tags:

$filtered = $page->children()->filterBy('tags', 'design', ',');

Now it's also possible to use that on files:

// get all jpgs

$filtered = $page->files()->filterBy('extension', 'jpg');



// get all files with a particular name

$filtered = $page->files()->filterBy('name', 'somename');

404 Error headers

So far, error pages were served with a regular 200 HTTP status code, which is of course not correct. Now a proper 404 code will be sent for error pages.

For more information about changes, take a look at the Changelog

How to update?

Download the latest version and extract the ZIP. Remove the old kirby system folder from your site and replace it with the new one from the latest version.

Also make sure to empty your cache folder if you have caching enabled

You can use the plugin to provide handy links for your visitors to save the current page or article with Instapaper or Pocket.

Installation

Download the readlater.php and put it in site/plugins Create the plugins folder if it is not there yet.

Usage

Once, the plugin is installed, you can instantly use it in your templates like this:

<article>

  <h1><?php echo html($page->title()) ?></h1>

  <?php echo kirbytext($page->text()) ?>



  <div class="readlater">

    <?php echo readlater($page->title(), 'instapaper') ?>

    <?php echo readlater($page->title(), 'pocket') ?>

  </div>



</article>

This will create two links:

<a class="readlater instapaper" href="http://www.instapaper.com/hello2?url=http%3A%2F%2Fgetkirby.com%2Fblog%2Freadlater&title=Read+Later+Plugin">

  Add to Instapaper</a>

<a class="readlater pocket" href="https://getpocket.com/save?url=http%3A%2F%2Fgetkirby.com%2Fblog%2Freadlater&title=Read+Later+Plugin">

  Save to Pocket</a>

…and you are free to style them with CSS and add them to your templates wherever you want.

Customization

If you don't want to use the default link texts (Add to Instapaper & Save to Pocket) you can use your own link texts:

<?php echo readlater($page->title(), 'instapaper', 'Put this on Instapaper') ?>

<?php echo readlater($page->title(), 'pocket', 'Put it in my Pocket') ?>

Options

You can also change the CSS selector, target and rel attribute for each link:

<?php echo readlater($page->title(), 'pocket', 'Read later', array(

  'class'  => 'mycustomclass',

  'target' => '_blank',

  'rel'    => 'somerelattribute'

)); ?>

Get involved

It would be great to have support for Readability or other sharing/read later services. The plugin is very easy to extend, so just get involved and fork the plugin on Github.

Please understand that not all suggestions from testers are in this next release. You guys had a bunch of awesome ideas, but the entire process of testing and coming up with the first version of the panel is taking longer than expected and I try to get it done finally.

Download

You can download the latest version from Github

How to update

I always try to make updating as simple as possible. What you need to do, is to replace the old panel folder with the new panel folder. If you have modified the .htaccess inside the panel folder, make sure to not replace that one.

Docs

For all Panel testers, I've setup the first version of the Panel docs. Please let me know if something is not understandable or missing.

What's new

A lot of fixes, new features and translations have gone into this new release.

Format Buttons

For all textareas, you can now activate the new format buttons in blueprints.

To activate them, add buttons: true to the textarea field definition in your blueprints. Here's an example, how to configure a textarea with buttons in a blueprint:

fields:

  text: 

    label:   Text

    type:    textarea

    size:    large

    buttons: true

You can even list individual buttons if you don't want to provide access to all of them:

fields:

  text: 

    label: Text

    type:  textarea

    size:  large

    buttons: 

      - h1

      - h2

      - bold

      - italic

Input validation

It's now possible to specify required fields and also do some input validation. This is again setup in your blueprints together with field definitions.

Required fields

fields:

  text: 

    label:    Text

    type:     textarea

    size:     large

    required: true

Validation

If you want to make sure that the content of a field is validated before a page can be saved, you can use the new validate option for fields.

fields:

  email: 

    label:    Email Address

    type:     text

    validate: email

You can use the predefined validation methods: email, date, url or you can define your own:

fields:

  somefield: 

    label:  Some Label

    type:   text

    validate: 

      minlength: 10

      maxlength: 30

      match:     /[a-z0-9]+/i

minlengt, maxlength and match are all optional, so you can combine them however you want.

Running the panel without mod_rewrite

The requirement for mod_rewrite for the Panel has led to quite some problems, so you can now switch off mod_rewrite support for the Panel in the Panel config (site/panel/config/config.php)

c::set('panel.rewrite', false);

All Panel URLs will be constructed like this afterwards:

http://yourdomain.com/panel/index.php/some/path

IE 8 ready!

The Panel interface will now work 100% on Internet Explorer 8. This will be the oldest supported version of Internet Explorer for Panel Version 1. Depending on the feedback, I might add support for Internet Explorer 7 later. The Panel has also been tested on IE9, latest versions of Opera, Firefox, Safari and Chrome (Win and Mac). If you find any browser-related issues, please let me know.

The Panel works also great on the iPad, except for sorting pages. I plan to add support for MobileSafari on the iPhone + Webkit on Android and sorting without drag and drop later.

Bug Fixes

There are tons of bug fixes in this release. Please check the changelog.mdown for more info.

Translations

I'm totally overwhelmed by the fantastic support with translations. The Panel is still in Alpha and yet it is available in nine languages!!

A huge "Thank You!!" to: Riccardo Mori, Loubna Aggoun, Dávid Bóta, Nils Hendriks, Seitenwerk, Ciuciu and Parlak for their help.

Please check the Translations page for more info. Also, please contact me, if you want to get involved: bastian@getkirby.com

To change the Panel translation for a certain account, open the account file in site/panel/accounts and change the language code like this:

username: bastian

password: supersecret

language: de

Available codes are

de = German

en = English

es = Spanish

fr = French

hu = Hungarian

it = Italian

nl = Dutch

ro = Rumanian

tr = Turkish

Next Steps

It's all about finalizing the latest features now and about fixing the last bugs. So please help me with bug-hunting! Install the latest version and let me know if you find something, which is not working as expected: bastian@getkirby.com

You can also use the Github Issue Tracker

Dev Branch

I'm going to release all future updates until the next release in the dev branch, so please make sure to check changes there from time to time to get the latest version.

Get Involved

If you are a developer, you are welcome to get involved in the development directly. Just heck the hell out of the latest version and let me know about it :)

Thank you!

This is all off to a fantastic start and it wouldn't be possible without your help – thank you!!

Cheers, Bastian

PHP is sometimes so messed up, that you necessarily start to write your own wrappers and helpers, to make your daily work with PHP easier. The Toolkit is a collection of classes and functions, which I came up with in the last years and which have become a core element of my work.

It's a 1-file, open-source library, which can be easily included in any existing project. Since it is already included in the Kirby CMS core, you can start using all its classes and functions right away. If you want to use it for any other project, you can download the source from Github.

Philosophy

The code of the library is quite unorthodox. It uses static methods all over the place to create short memorizable method names and group methods. Either you like it or you don't. But the good thing is, that you don't have to use it, if you don't like it :)

Here are some of the principles the library follows.

• keep it simple stupid
• help to write less code
• make things easier to memorize
• provide better consistency
• provide built-in utf-8 support
• keep it focused on core tasks

Toolkit Tidbits

Handling Requests

PHP has the famous $_GET and $_POST variables, which contain the submitted values from POST and GET request – for example from forms. Working with them and checking for submitted values can be quite painful:

$value = (isset($_POST['key'])) ? trim($_POST['key']) : 'default value';

I think we've all seen this kind of code.

With Kirby, you can save a lot of that hassle by simply using the get() function, which works for POST and GET requests and is way more comfortable to use.

$value = get('key', 'default value');

If you don't pass a default value, false will be returned if nothing could be found for the passed key:

$value = get('key');

get() will also take care of trimming and of stripping slashes if necessary.

Redirection

If you want to create a simple redirect, you normally need to send a location header and if you want to do it correctly, you should also send a http status header:

header('HTTP/1.1 301 Moved Permanently');

header('Location: http://mywebsite.com');

With Kirby you can just write…

go('http://mywebsite.com');

Working with arrays

a::show

If you are debugging, you often need to inspect the content of an array or object. There's var_dump or print_r, but their output isn't really nice. a::show() helps you by producing nice, readable output of any array or object:

$array = array('design', 'tags', 'typography');



a::show($array);



/* output:



Array

(

    [0] => design

    [1] => tags

    [2] => typography

)



*/

a::get

How often do you find yourself writing something like this?

$value = (isset($array['key'])) ? $array['key'] : 'default value';

Instead a::get will try to find a value for a key in an array for you and return either that value or your default value if nothing has been found.

$value = a::get($array, 'key', 'default value');

If you don't pass a default value and nothing could be found for that key,
false will be returned.

a::first and a::last

Do you remeber, which was the function name for that array function that returns the first element of an array or that function that returns the last element? array_pop, array_push, array_shift, array_unshift? Maybe it's just me, but those function names kill me.

With Kirby you can do:

$array = array('design', 'tags', 'typography');



echo a::first($array);

// output: design



echo a::last($array);

// output: typography

This also works with associative arrays of course.

a::sort

Sorting a multi-dimensional array is a nightmare – not anymore!

$array = array(

  array('username' => 'homer'),

  array('username' => 'marge'),

  array('username' => 'bart'),

  array('username' => 'lisa'),

  array('username' => 'maggie')

);

  

$sorted = a::sort($array, 'username', 'asc');



a::show($sorted);



/* output:



Array

(

    [0] => Array

        (

            [username] => bart

        )



    [1] => Array

        (

            [username] => homer

        )



    [2] => Array

        (

            [username] => lisa

        )



    [3] => Array

        (

            [username] => maggie

        )



    [4] => Array

        (

            [username] => marge

        )



)



*/

Working with strings

str::lower and str::upper

Converting a string to lowercase or uppercase shouldn't be hard, right? Unfortunately PHP's native strtolower and strtoupper functions are not able to handle UTF-8 encoded strings correctly. That's why Kirby has its own lowercase and uppercase functions:

$sometext = 'This is a übercool Example of üppercase and Løwercase';



echo str::lower($sometext);

// output: this is a übercool example of üppercase and løwercase



echo str::upper($sometext);

// output: THIS IS A ÜBERCOOL EXAMPLE OF ÜPPERCASE AND LØWERCASE

str::length

The same problem with UTF-8 exsits for strlen – PHP's native function to count the number of characters in a string. With an UTF-8 encoded string the result wil be wrong. So Kirby has…

$sometext = 'This is a übercool lengthy string';



echo str::length($sometext);

// output: 33

str::short

To shorten a text is one of the tasks you need all the time. Think of a list of blog articles, with a short excerpt and a "read more" button, or to make sure that user generated content does not break your templates or stuff like that. When shortening strings you most probably want to append an ellipsis to show that it has been shortened, but only if the string is really too long. str::short does exactly that for you…

$sometext = 'This is a übercool lengthy string';



echo str::short($sometext, 10);

// output: This is a…

str::split

Splitting strings by a particular character is easy, right? Yep, it is, but it can be even easier. Take a look at the following string.

$tags = ', design, tags, typography, fun, , ';

You could use explode(',', $tags) to get all tags, but it wouldn't work well because of spaces and additional commas. str::split will help you to get some nice results without all the mess:

$string = ', design, tags, typography, fun, , ';

$tags   = str::split($string);



a::show($tags);



/*



Array

(

    [0] => design

    [1] => tags

    [2] => typography

    [3] => fun

)



*/

Of course it's possible to change the splitting character(s):

$string = '/ design / tags / typography / fun / / ';

$tags   = str::split($string, '/');

…and you can even specify the minimum length of included string:

$string = '/ design / tags / typography / fun / / ';

$tags   = str::split($string, '/', 4);



a::show($tags);



/* output:



Array

(

    [0] => design

    [1] => tags

    [2] => typography

)



*/

Config

c::set and c::get

If you need some app-wide configuration variables you can either use constants or you can go for Kirby's config variables. They are accessible everywhere and can be set and overwritten everywhere as well.

c::set('myconfigvar', 'this is my awesome config value');



function foo() {

  

  echo c::get('myconfigvar');

  // result: 'this is my awesome config value'

  

}

If you want to check, which config variables have been defined so far, do this:

a::show(c::get());

// output: your entire config

Session

s::start

If you want to avoid errors because you start a session twice accidentally, use s::start() instead of session_start()

session_start();



s::start();

// no problem :)

s::set and s::get

Sometimes it's really cool to just have to write less:

// start a session

s::start();



s::set('myvar', 'my value');



// later…

echo s::get('myvar');

// result: my value

s::get can also be used with a default value, so if the session variable has not been found, the default value will be returned:

echo s::get('myvar', 'my default value');

Cookies

cookie::set and cookie::get

To make setting and getting values from cookies easier, you can use:

cookie::set('mycookie', 'my cookie value');



// later…

cookie::get('mycookie');

// result: my cookie value

… again, you can define a default value if the cookie could not be found:

echo cookie::get('mycookie', 'my default value');

cookie::remove

To remove a cookie, use

cookie::remove('mycookie');

Files

f::write

f::write offers a fool-proof way of creating files. You can even pass an array and that will automatically be converted to json before.

$content = 'This is some nice content for my file';

$file    = '/some/path/to/my/file.txt';



f::write($file, $content);

f::read

Reading a file is very simple with PHP file_get_contents, but with f::read() you get a more consistent and shorter function and you can even use the second argument to instantly parse the result:

$file = '/some/path/to/my/file.txt';



echo f::read($file);

// result: content of file.text



$file = '/some/path/to/my/file.json';



echo f::read($file, 'json');

// result: the parsed json string as array

Directories

dir::read

Sometimes it's great to be able to get all files in a directory. Kirby CMS is entirely based on that. With dir::read you will get an array with filenames in a passed directory:

$files = dir::read('/path/to/my/dir');



a::show($files);

// result: an array with all filenames

dir::make and dir::remove

dir::make will create a directory if it does not exist yet and
with dir::remove you can delete an entire directory with all its contents.

dir::make('/path/to/my/new/dir');



dir::remove('/path/to/my/new/dir');

Validation

v::email

Check for a valid email address…

$email = 'bastian@getkirby.com';



if(v::email($email)) {

  echo 'this is a valid email address';  

}

v::url

Check for a valid URL…

$url = 'http://someurl.com';



if(v::url($url)) {

  echo 'this is a valid url';  

}

v::date

Check any parsable date…

$date = '11.04.2012';



if(v::date($date)) {

  echo 'this is a valid date';  

}

More…

The Kirby Toolkit has way more features. Please read the docs to learn more about them.
There's also a tutorial how to use the built-in database class.

If you like the Toolkit, but you want to add your own features, feel free to fork it on Github.

The Plugin makes it easy to display the estimated time to read any text in Kirby.

Installation

The installation is as simple as ever. Download the readingtime.php and put it in site/plugins Create the plugins folder if it is not there yet.

Usage

Once, the plugin is installed, you can instantly use it in your templates like this:

<article>

  <h1><?php echo html($page->title()) ?></h1>

  <div class="readingtime">

    Estimated Reading Time: 

    <?php echo readingtime($page->text()) ?>

  </div>

  <?php echo kirbytext($page->text()) ?>

</article>

Example Output

Estimated Reading Time: 11 minutes, 31 seconds

Localization

If you need to translate the output to a different language, you can directly do that by passing the following paramaters.

<?php 



echo readingtime($page->text(), array(

  'minute'  => 'Minute',

  'minutes' => 'Minuten',

  'second'  => 'Sekunde',

  'seconds' => 'Sekunden'

)); 



?>

You can even change the entire format of the result string:

<?php 



echo readingtime($page->text(), array(

  'minute'  => 'Minute',

  'minutes' => 'Minuten',

  'second'  => 'Sekunde',

  'seconds' => 'Sekunden',

  'format'  => '{minutesCount} {minutesLabel} – {secondsCount} {secondsLabel}'

)); 



?>

This makes the plugin very flexible and you gain full control of the generated HTML.

I think it's a fantastic plugin and a great addition to any blog. Thanks to Roy for his help.