This does not directly affect the first search, but the search field is then filled with “my search string/lang-pref/en”, which is confusing for the visitor.

A quick solution is to filter the search query and remove the said string:

/* Clean the search URL */
function polyglot_clean_search_URL () {
return preg_replace('@/lang-pref/[a-z]{2}/@i','',get_search_query());
}
add_filter('the_search_query', 'polyglot_clean_search_URL', 1);

You can either add this code to your theme’s functions.php, or to the plugin’s file, at the end.

All current plugins that integrate Slimbox (that I know of – this one, for example) actually require the editor to add the rel="lightbox" attribute. But since the editors of this site have no HTML knowledge whatsoever and will be editing in “visual” mode, this hinders deployment.

So I came up with a modification to the actual javascript of Slimbox, to make it identify all links to images and lightboxify them

Here’s the actual code modification (starting at line 22 – on Slimbox version 1.41):

$each(document.links, function(el) {
if (el.href && el.href.test(/.(jpg|jpeg|png|gif|bmp)$/i)) {
el.onclick = this.click.pass(el, this);
el.rel = 'lightbox';
this.anchors.push(el);
}
}, this);

$each(document.links, function(el){
if (el.rel && el.rel.test(/^lightbox/i)){
el.onclick = this.click.pass(el, this);
this.anchors.push(el);
}
}, this);

This replaces the detection of links that have “lightbox” in the rel attribute with a detection of all links that lead to images.

Although it suits my intended purpose, there are several drawbacks to this method that I can think of:

• if there already is a rel attribute, it overwrites it
• it won’t take advantage of the “gallery” feature

As mentioned in the title, this is a “quick & dirty” fix, but might help some.

If I get around, I’ll be writing a WordPress plugin with options to lightboxify all images, make a gallery of all images in a post / page (by filtering the_content() and adding a rel="lightbox[$post->ID]" to image links). Maybe even make a TinyMCE plugin that would add a button to lightboxify a certain image – right from the visual editor.

Soon enough, I’ll build him a website as well

It’s not much, but it pays for the hosting plan of this website – which means that this site is self-sustained.

I’ve grown to about 12.000 visitors with around 30.000 page views a month.

And this, for a blog with less than 30 posts. This is a wake up call for me: I will put more time in this site, from the little I have left, after my day job and my freelance projects.

I have so many ideas, like, for instance, the long awaited MOOdalBox 2 (lots of people have asked me when it would come out, I’ve made and broken so many promises on this subject ).

To sum it up, I feel the need to thank all my visitors for spending a moment here and for supporting me on every occasion. Thanks guys

Unfortunately, this is a JavaScript only method – so it’s easily bypassed. I’ll have a version that uses more server-side scripting ready some time soon (for a project I’m working on), but this is cool and can easily enough be used just as a warning.

Here’s a screenshot I made (after already refreshing several times – note the date of the request, it’s already 10 days ahead):

Followed by another, one refresh later:

Funny thing is that the changes persist even after a logout / login. You can now use it to predict the future !

I have reported the bug, let’s hope for a quick fix.

UPDATE: After a while, I logged back in to find all dates correctly displayed (I said to myself – wow, quick reaction time), except for one miss:

All subsequent refreshes produced the same result (+10h).

It is WordPress based (currently version 2.3.3), with a customized theme to display certain interface elements. It is page-centric, rather than post-centric, since they needed a presentation website but with an easy to use interface for adding news.

For page navigation, I’ve devised a custom tree / list menu, that I animated with the use of MooTools. It unfolds on the different levels of the site’s structure.

So, if you ever feel like posting a word on any of my scripts on your blog, or if you feel yo can contribute, do drop me a line, be it over e-mail, on the forums, in a comment or.. anything you may find suitable. And at any time, do ask for directions, and generally.. don’t be a stranger, don’t stay anonymous – we all need to know you and meet your work

As always, credit will be given where due

This was due to a server change I requested because of frequent downtimes on the previous one. However, the new server my site was moved to had certain features differently configured – that rendered my site inaccessible.

First was the php version, that made my WordPress installation go AWOL (had to switch from php 5 to 4 to have it work). That also lead to errors on my forum pages, but those were corrected using some tips from the bbPress forums.

The cause of 404’s on my playground folders was that my .htaccess for that folder used the directive SecFilterEngine Off, in order to disable mod_security (which, when activated, interfered with my Ajax calls). But on this particular folder, mod_security wasn’t configured and thus the .htaccess generated an error and wasn’t correctly interpreted (I used it to disable mod_rewrite in the playground folder too, in order to prevent WordPress’ rewrite rules – but since it had an error in it, the default WP rules were applied and no such page was found).

On a happier note, I just launched the “splash page” of an upcoming community website I’m working on, the one that pushed me to write the code for the vertical kwicks.

However, although Fx.Base has support for specifying the unit, the original Kwicks demo doesn’t play well out of the box specifying ‘em’ as the unit.

Here’s a demo of what I did: vertical kwicks with em sized elements (notice the scalability of the layout – change the font size and it still works flawlessly)

The solution was to replace all occurences of .toInt() with .toFloat() when extracting the height style property, because if for px there aren’t any decimals, for em or %, there are. It took me a while to find it, I hope it saves you some time.

There’s still a jump effect at the first mouse over in Firefox and Safari (but not in MSIE) that I have to figure out (but for the moment I’ll consider it a “nice effect”- people that have seen it seem to like it ).

For now, it’s tested in Firefox 2, Internet Explorer 6 / 7, Safari 3 – all on Windows. If you get a chance to test it in other browsers, I’d appreciate a mention of it (thanks ).