Then, when working on another site yesterday, a Base64 encoding and Base64 decoding experiment, I needed an XML sitemap yet again. So I improved up the XML Sitemap PHP Script a bit further and decided it should be released.

Why make an XML Sitemap for Static Files?

Let's first address the "why" of this script: in lots of cases, you'll have static files, either they're PDF's, or static PHP or HTML files that create a site. I want all of those in an XML sitemap for two reasons:

• to tell Google that they're there;
• to be able to see in Google Webmaster Tools whether they're all indexed.

Configuring the XML Sitemap PHP script

Of course this script needs a bit of configuration before it'll work well. It has the following constant & variables:

• SITEMAP_DIR
  The directory to search for files in.
• $filetypes
  An array of all the file types that you wish to include in your XML sitemap.
• $replace
  An array of all the files that should be replace with other URL's, useful to, for instance, replace 'index.php' with an empty string, so it'll look like just example.com/
• $ignore
  An array of all the files to ignore in the XML sitemap, useful for your config.php, for instance
• $xsl
  A relative path to the XSL file included in the script.
• $chfreq
  The change frequency for files, can be 'hourly', 'daily', 'monthly' or 'never'.
• $prio
  The priority, a value between 0 and 1, since you can't differentiate between files, there's no big harm in setting them all to 1.

Styling the output of our XML Sitemap PHP Script

Of course, we'll want our XML Sitemap to look good, as well as work well. For that we use an XSL stylesheet which is included in the download. It makes the XML sitemap look like this:

XML Sitemap PHP Script output, styled with XSL

Download XML Sitemap PHP Script

I've added the whole script on Github, so you can play, fork, etc. Or you could just download the zip.

XML Sitemap PHP script is a post by Joost de Valk on Yoast - Tweaking Websites.A good WordPress blog needs good hosting, you don't want your blog to be slow, or, even worse, down, do you? Check out my thoughts on WordPress hosting!

There are three things in that integration that should catch your eye. If you click on "Yoast", that's what Twitter calls a "follow intent". So when you click on that link, Twitter generates a popup that looks like this:

I think that's pretty cool. You're welcome to disagree, of course, but then you might as well stop reading now. Twitter generates similar popups when you click on the retweet and reply buttons, right behind the text of the tweet.

How to create Web Intents

Creating these Web Intents is hilariously easy. You need the normal JS library that you have for the follow and tweet buttons, so there's no need to include anything else. Here it is:

<script type="text/javascript" src="http://platform.twitter.com/widgets.js"></script>

Then, a "follow intent" link, is crafted as easily as this:

<a href="https://twitter.com/intent/user?screen_name=yoast">Yoast</a>

That's easy right? That's all you need to do. Let's check the other web intents, starting with the retweet intent:

<a href="http://twitter.com/intent/retweet?related=yoast&tweet_id=<ID>">

All you have to do is replace the <ID> with the tweet to be retweeted. A reply intent is crafted just as easily:

<a href="http://twitter.com/intent/tweet?related=yoast&in_reply_to=<ID>">

There's no need to use extra JavaScripts, write extra code, nothing. Feel free to just use this in your theme, your posts, wherever and Twitter's script will change it for you. In their documentation for Web Intents, Twitter provides you with images to use as well, which I'm using too, as you can see.

Now I'd like to hear from you! Do you have creative ways of using Web Intents?

Web Intents from Twitter is a post by Joost de Valk on Yoast - Tweaking Websites.A good WordPress blog needs good hosting, you don't want your blog to be slow, or, even worse, down, do you? Check out my thoughts on WordPress hosting!

There's all sorts of factors that decide on whether your email is delivered or not, but one of the most important ones is a DNS record called SPF. SPF stands for Sender Policy Framework and let's the receiving mail server reliably determine whether the server that is sending you email is actually allowed to send you email. Adding one will increase your email reliability incredibly.

As with most DNS type records, the syntax is quite hard to explain so I won't even try. Let me link you to the Wikipedia page if you really want to know. What I found way more helpful though when I was searching and trying to figure out how to do this is Microsoft's wizard for this stuff. It asks you a bunch of questions and will still require some time from your side but it got me to the desired end-result a lot faster.

SPF records, Google Apps for Domain and email reliability

I use Google Apps for domain to handle my email, which means that I do most of my sending through a Google SMTP server. Because of that I had set the SPF record in the manner Google suggests here. The thing missing from that is very, very subtle, but makes all the difference. It's a few letters, let's see if you can spot it. This is the SPF record Google gave me:

v=spf1 include:_spf.google.com ~all

This is what it actually needed to be:

v=spf1 a include:_spf.google.com ~all

You will have spotted the addition of "a " after "spf1". This simple addition means that all web servers that are identified in my domains A records, hence, all the web servers from which I run my domain and subdomains, are allowed to send email as well.

The include directive means that Google can setup SPF records for the domain _spf.google.com and thus add or remove mail servers without you having to change anything.

How to test email reliability

If you're now thinking "I don't know whether this has been set up correctly for my domain", don't fret. You can test it quite easily. Go to this SPF testing tool and use the 3rd form on the page. Using only the first and third input of that form, enter your web server's IP address and your from address, which is usually wordpress@yourdomain.com if you're running WordPress. With my initial test, it gave this result:

This means that this test won't fail your email per se (as there was no SPF record), but for stricter email servers, it might, in other words, you've got quite low email reliability. Now I ran it with the SPF record I has just fashioned using Microsoft's wizard and it gave me this:

That is the result you want to see, as that means my server's email reliability just went up quite a bit.

WordPress specific email reliability: using another SMTP server

Quite often email from your own server won't work as expected, especially when you're on a shared host it can give issues. There are quite a few plugins out there to help you set up an external SMTP server, I've relied on Coffee2Code's Configure SMTP plugin myself a few times. There's some issues with that though, especially once you're starting to get more visitors, as most SMTP servers for free email services have a limit to how many emails you can send per day.

If you can, just use your own server or outsource the email delivery to a third party that specializes in sending service emails. I've been testing SendGrid myself, but wasn't completely happy with it. Their reliability was a lot higher but the costs are quite high too when you get several hundreds of comments. You might think "that's only a couple of hundred emails", well, it's not.

If you have subscribe to comments enabled, which I highly suggest you do, it'll be a lot more. I get anywhere from 20 to 200 comments on a post, average about 80 at the moment. If 50% subscribes to comment notifications, that adds up to an enormous amount of email being sent.

As for newsletters, there are plugins for sending those from your WordPress install too. I highly encourage you not to do that. Use Mailchimp, or any other newsletter service for that. Their reliability is way higher and you get awesome statistics and subscription services to boot. I use them for my WordPress Newsletter and never regret it.

Are you using other services that send email for you?

If you're using other services that send email for you, for instance if you're using Freshbooks (aff) for invoicing like I do, be sure to include them in your SPF too, just add another include like we did above for Google:

include:_spf.freshbooks.com

There are more services that support this, be sure to check if you're using any services that send email on your behalf. Email reliability is important, but even more important when it's sending your invoices!

Update from Antonio Romero in the comments, the same goes for MailChimp:

include:servers.mcsv.net

Just updated my own SPF with that as I use my own email address as a from address there.

Conclusion: make sure your email reliability is high!

Whether you run your own server or not, it can't hurt to do the check above to see whether your email has a high chance of being delivered. If you're sending email from your web server, be sure to do the above check and make the necessary changes to your SPF record if needed!

Bonus tip: DKIM

If you're using Google Apps for domain, be sure to read this guide and implement everything in it. It'll help you set up domain keys, which adds another layer of spam protection.

Email Reliability: use an SPF record is a post by Joost de Valk on Yoast - Tweaking Websites.A good WordPress blog needs good hosting, you don't want your blog to be slow, or, even worse, down, do you? Check out my thoughts on WordPress hosting!

His tips in particular are useful for optimizing the performance of social media buttons and ads etc, but keep in mind there are lots of aspects of WordPress to optimize, like SEO, database performance and more.

Killer Performance Tips from the Expert is a post by Joost de Valk on Yoast - Tweaking Websites.A good WordPress blog needs good hosting, you don't want your blog to be slow, or, even worse, down, do you? Check out my thoughts on WordPress hosting!

Let's draw an analogy: when you have someone build a house for you, what would you say if they'd say: "oh and btw, we'll leave a banner up on your roof", or to make the analogy better, when they said nothing at all and just did it? You'd either be mad and tell them to come take it off, or you'd throw it off yourself, right?

The question is of course: why do web designers and web developers do this? The reasons are simple: they'd like everyone to know that they designed that certain website and they use these footer links (if they're smart), to increase their search engine rankings. Luckily search engines, most notably Google, have been aware of this practice and are pretty good at making links in footers of pages not work as well, but that doesn't change the basic fact that the link should not be there.

The reason why this annoys me is that it's abusing the fact that most people who have a website built either for themselves or their company don't know the value of these links. It's basically the web developer taking advantage of the ignorance of their customer. A customer who, in most cases, wouldn't even now how to take a link like that out. Now what does that make them?

Don't get me wrong; I'm not saying web developers and web designers can't have these links, they should just be very open about it and not make it a default. If you're a customer with footer links on your site, and it hasn't been discussed with you, nor is it not in the contract with your web developer or designer, feel free to take it off or, better yet, ask for that discount.

If you're using a WordPress theme or free template that has one of these footer links, and you've gotten it for free, I'd leave it there, because that's how you "pay" the designer / developer. If it has multiple links like that, or really spammy ones like sometimes happens on non-legit theme sites, I'd personally take them out immediately, or not use the theme at all.

“Design by” footer links… is a post by Joost de Valk on Yoast - Tweaking Websites.A good WordPress blog needs good hosting, you don't want your blog to be slow, or, even worse, down, do you? Check out my thoughts on WordPress hosting!

WordPress

• Code Snippets and Examples

  • The only proper way of adding a Facebook “Like” button to your WordPress blog
  • An article I wrote recently for Smashing Magazine: Lessons Learned From Maintaining a WordPress Plug-In
  • Gravity Forms PayPal integration
  • 16 Vital Checks Before Releasing a WordPress Theme
  • How to Display Human Readable Post Dates in WordPress
  • Control WordPress Content via Userrights or Time
  • A good Beginner’s Guide to the Thematic Framework

• Plugins

  • BuddyPress Courseware beta; a very cool plugin for schools & other educational institutions.
  • Post to post; nice plugin for creating relations between posts.
  • Press This Reloaded; pretty useful if you need to, for instance, adapt the SEO title of a post.
  • WPMU.org features my WordPress Salesforce CRM plugin.
  • Custom Post Permalinks; I seriously think this should be in WordPress core, but as long as it's not, this'll do.

• News

  • Common WordPress Multisite Problems and Solutions
  • Top 10 WordPress News Blogs
  • When is the Best Time to Post a Blog Post? Not enough people think about this.

SEO

• Without any work from me, my Google Analytics plugin now helps you verify your Google Webmaster Tools account.
• I'm seeing similar stuff to this: Google Webmaster Tools Link data - a case study by Dave Naylor, my favourite UK SEO.
• Want an SEO job? Check out the Daily Mail's robots.txt file

Analytics

• Qualitative Web Analytics: Heuristic Evaluations Rock! another great post by Avinash Kaushik
• The new Management API for Google Analytics rocks; check out the docs

Web design / web development

• Practical? No. Cool? Yes. Compressing Your JavaScript and CSS to PNG Images
• What a surprise: Steve Jobs was right, Flash fails on Android
• HTML5 for Web Designers: Book Review at Nettuts+ - I've read it too, it's amazing
• Good Help is Hard to Find is another A List Apart classic. Wonder how to apply this to my plugins...
• A very concise explanation of the viewport metatag by David B. Calhoun
• A pretty awesome example of what can be reached with CSS3 now
• I'd almost start using Typekit: Adobe partners with Typekit to bring legendary typefaces to the web.
• MathML is now part of WebKit nightlies, go forth and play, all you math lovers out there!
• Delay loading of print CSS (in WordPress, but useful for everyone)
• Debugging Tools - jQuery for Designers
• This would work perfectly for WordPress plugin developers: Readme Driven Development

Online Marketing / Social media

• Daring Fireball - Online Advertising: Losing the Race to the Bottom - listen to this, seriously.
• What's this thing called Buzz that Leo talks about? :)
• Facebook Tabs: What They Are & How to Use Them - Good writeup on RWW
• Quite curious how many people will do this: German Homes Can Now Opt Out Of Google - TechCrunch

Science

• Experts are usually wrong
• Everyone looks better after you've tipped back a pint or two, and now we know why
• A nice infographic on the history of the Internet
• Freakonomics: loved the book, looking forward to the movie, check out the trailer.
• Wonder what my wife does? Read her latest paper on the Intergenerational Transmission of Convictions.

Fun

• (Fake) Lady Gaga sings about Java programming with some hilarious quotes
• Gonna have to try this on my son in about 2 years: 4 Tools for Teaching Kids to Code
• Basically, you can't block Mark Zuckerberg on Facebook, because too many other people did it before you
• You know you're a geek when you think this is funny

Lifestyle

• Trying to follow this advice: living a Balanced Freelance Life (even though I'm only partly freelance)

Mac

• Why Daniel Jalkut is sticking with the Mac
• Precipitate: search for and launch the info you stored in the cloud from Spotlight or G Desktop for Mac
• This is bloody hilarious: No Comment: Justin Long's jailbroken iPhone
• This proved to be pretty awesome for mp3 splitting: Macsome Audio Splitter

Link dump: interesting reads from around the web is a post by Joost de Valk on Yoast - Tweaking Websites.A good WordPress blog needs good hosting, you don't want your blog to be slow, or, even worse, down, do you? Check out my thoughts on WordPress hosting!

Instead of just identifying the problem, your 404 error page needs to offer a solution.

In the default WordPress Kubrick theme the 404 error page (example) is probably one of the ugliest pages you've ever seen, and chances are yours is not any better. Today is the time to end that. This post will provide you with everything you need to make your "404 - File not found" page a starting point instead of a dead end street.

The goal of a good 404 error page is simple: to make sure visitors landing on it continue browsing your site, and find the content they came for. Let's get going.

Get into your visitors mindset

Get into the mindset of the person that just got to a 404 error page on your site. They were expecting something else, if not, they wouldn't have gone there. So there's a couple of things you should absolutely not do:

First of all, considering they've probably clicked a link somewhere to get to that 404 error page, whose fault is it that they're getting a 404? Theirs? No. Yours? It very well might be, so you'd better apologize.

Second, make sure the styling of your 404 error page fits in with the rest of your site. Sometimes designers go overboard with their 404 pages, and make them look like, for instance, a Windows blue screen. This can have the very undesired effect of people leaving immediately.

Third, if you are going to make jokes, like that Windows blue screen, make sure it's a joke everyone gets. Especially when you're blogging in English, you might end up with a lot of readers for whom English is their second or third language. Your puns, though well intended, might be going nowhere because their mastery of the language isn't sufficient. Because of that they might leave... Is that worth it?

Let's make a killer 404 error page for WordPress

Ok so we know what not to do. We also know that the visitor came to your site looking for specific content, usually having followed a link from somewhere. Now it's time to start giving them ways of doing that. If you're not using WordPress and you're lazy, the Google 404 widget might be helpful. If you are using WordPress, we can do better than that.

Let's let us be inspired by some great 404 error pages:

I'll be honest: the Conversion Rate Experts guys have inspired the first version of my 404 error page. They offer you 4 options to get to the content you were looking for:

1. search
2. check the URL for misspellings
3. check the sitemap
4. start over at the homepage

That's a great start. Apple gives you a sitemap straight away. Depending on your site's structure that might be a great idea too.

I wanted to add one more thing: a set of pages that actually might be related to the URL people had typed in. To do that, we'd have to parse the URL and see if there's something useful in there. Let's see what we have to work with:

What data does a 404 error page provide?

A lot of people seem to think that a 404 page is a dead end street. It's not, there's a whole lot of data that can help you find the content your visitor was looking for. Let's start with the URL: it contains something very useful. All the text that's there after the slash of your domain should be pointing you to what it is the person was looking for.

Luckily, WordPress stores that information for you. The $wp_query->query_vars['name'] variable holds whatever was in there. It does do some replacing in there though, it replaces all weird entities with a dash (-). We'll use this bit of information to spice up your 404 error page.

First of all, let's check whether there's a direct match for that var in a page name once you strip out all the things that people sometimes add to your URL erroneously. (If you read on there's an adapted version of the Kubrick 404 page which you can use to update your own themes.)

$s = $wp_query->query_vars['name'];
$s = preg_replace("/(.*)-(html|htm|php|asp|aspx)$/","$1",$s);
$posts = query_posts( array( 'post_type' => 'any', 'name' => $s) );

If that doesn't deliver results, you'll want to do a search for that word, to do that we'll have to rip out the dashes in the name, and then do the search. As we're going to re-use the $s variable further on, we'll do that outside of the if statement to check whether the previous query delivered results:

$s = str_replace("-"," ",$s);
if (count($posts) == 0) {
  $posts = query_posts(array( array('post_type' => 'any', 'name' => $s) );
}

Now we have an array with posts, at least, we hope we do, so let's check that, and loop through it:

if (count($posts) > 0) {
  echo "<p>Were you looking for <strong>one of the following</strong> posts
    or pages?</p>";
  echo "<ul>";
  foreach ($posts as $post) {
    echo '<li>';
    echo '<a href="'.get_permalink($post->ID).'">'.$post->post_title.'</a>';
    echo '</li>';
  }
  echo "</ul>";
}

I've made an adapted version of the Kubrick 404 error page, which you can download here.

There's a plugin that does something similar to the above, called Smart 404. It chooses to redirect the visitor to the first result it gets. It wouldn't be my preference, I actually want people to notice that the URL was wrong.

So now we have a great 404 error page, but we haven't used all the data that we were provided with. Another bit of data the 404 provides is the referrer: someone linked to your page with a wrong URL, or is linking to a page that isn't there anymore. So we've got one thing left to do:

Preventing 404 error pages

There's a very cool plugin called 404 notifier by Alex King, which can provide you with an RSS feed of the 404's on your site, and Redirection, one of my all time favorite plugins, offers the same functionality. You could also use my own Google Analytics for WordPress plugin. It tracks the 404's as 404.html (look for them in your content report).

Using Google Analytics has the added advantage that it saves the referrer, so you know which URL the visitor originated from. This allows you to not only redirect the URL to the correct place, but also to ask the site that referred the visitor to fix the URL.

Another great way to keep track of 404's on your site is using Google Webmaster Tools. In the Diagnostics - Crawl Errors area of Webmaster Tools Google gives you a great overview of what 404's it encountered on your site:

Two Things you Need to Know about 404 error pages

These are things that WordPress is doing right, but it's good to know these things:

• Internet Explorer will only show your custom 404 page if it's larger than 512 bytes (hard to get smaller than that with WordPress).
• 404 is not only the name, it's also the HTTP header that the page should send, if not, you might end up with 404 pages in the search engines indexes. You can easily check this with a HTTP header checker.

As said, no need to worry if you're using WordPress, but good to know these things.

There's really no excuse left now for a bad 404 error page on your WordPress blog or anywhere else, so go fix yours! Once you've done that, drop your site's URL in the comments, and I'll make a small gallery of cool 404 error pages in this post.

Practical Guide to creating a 404 Error Page for WordPress is a post by Joost de Valk on Yoast - Tweaking Websites.A good WordPress blog needs good hosting, you don't want your blog to be slow, or, even worse, down, do you? Check out my thoughts on WordPress hosting!

There are a couple of variables you can use, which you'd have to do in standard URL format, remember to properly encode the & if you care about validity of your HTML, so you use & in that case. Here's the full mailto link syntax:

<a href="mailto:info@example.com?subject=subject&cc=cc@example.com">mail link</a>

Here are the variables you can use in mailto links:

Some mailto link examples

A simple mailto link:

<a href="mailto:info@example.com">mail link</a>

mailto link with subject:

<a href="mailto:info@example.com?subject=email%20subject">mail link</a>

mailto link with multiple recipients:

<a href="mailto:info@example.com,email@example.com">mail link</a>

mailto link with a CC:

<a href="mailto:info@example.com?cc=email2@example.com">mail link</a>

A mailto link with message body already started:

<a href="mailto:info@example.com?body=these%20mailto%20links%20are%20cool">
  e-mail link
</a>

A mailto link with 3 lines of message body:

<a href="mailto:info@example.com?body=these%20mailto%0Alinks%20are%0Acool">
  mail links
</a>

A mailto link with 3 lines of message body and a BCC:

<a href="mailto:info@example.com?bcc=mail2@example.com
  &body=these%20mailto%0Alinks%20are%0Acool">
mailto links
</a>

As you can see, you can add as many of these as you want and stack them on top of each other. Remember that after the email address you'll use a question mark to prefix the first variable, and ampersands ( & ) for each consecutive variable.

Happy coding and mailing!

The Full mailto Link Syntax is a post by Joost de Valk on Yoast - Tweaking Websites.A good WordPress blog needs good hosting, you don't want your blog to be slow, or, even worse, down, do you? Check out my thoughts on WordPress hosting!

Next to that links would be in a different color, depleting your color cartridges and not giving you any info whatsoever. When you've printed an article, you usually have to go back to the online version to be able to open the links. There's a solution for that, and it's actually quite easy: using CSS to add the URL after the link. That's really easy to do with the content declaration, like this:

#content a:after {
	content: " (" attr(href) ") ";
	font-size: 80%;
}

Next to that I used display:none; to hide the menu, sidebar and comments, so you get just the article, in black text, on a white background.

Of course, feel free to have a look at (and copy) my print css!

Added a print CSS style sheet is a post by Joost de Valk on Yoast - Tweaking Websites.A good WordPress blog needs good hosting, you don't want your blog to be slow, or, even worse, down, do you? Check out my thoughts on WordPress hosting!

function FrontpageDiggs($url) {
$result['source'] = "http://digg.com/rss_search?search=".$url."&area=promoted&type=url&section=all";
$output = file_get_contents($result['source']);
preg_match_all("/.*(<item>).*/",$output,$matches);
$result['result'] = count($matches[1]);
return $result;
}

Now if you echo $result['result'], you'll get the number of posts for $url that made the frontpage.

Get the number of popular digg posts for a URL is a post by Joost de Valk on Yoast - Tweaking Websites.A good WordPress blog needs good hosting, you don't want your blog to be slow, or, even worse, down, do you? Check out my thoughts on WordPress hosting!

OS X 10.5 is really looking good, can't wait to get home and play around with it.

OS X 10.5 Leopard: Spaces combined with Parallels is a post by Joost de Valk on Yoast - Tweaking Websites.A good WordPress blog needs good hosting, you don't want your blog to be slow, or, even worse, down, do you? Check out my thoughts on WordPress hosting!

Big hunkin’list of Mac Tools for SEO’s and Webdevelopers is a post by Joost de Valk on Yoast - Tweaking Websites.A good WordPress blog needs good hosting, you don't want your blog to be slow, or, even worse, down, do you? Check out my thoughts on WordPress hosting!

Webdesign survey is a post by Joost de Valk on Yoast - Tweaking Websites.A good WordPress blog needs good hosting, you don't want your blog to be slow, or, even worse, down, do you? Check out my thoughts on WordPress hosting!

Keeping track of what people are searching for
I had a few things to make sure while building this search function. First of all, I wanted to have the same info I get when I look at the statistics page for the Search Meter WordPress plugin. Secondly, I wanted to show more then just the post or page title. The last, but also very important demand I have is that it's fast. Well the first one was quite easy, I decided to put the data into the table for the search meter plugin and just use that interface, instead of writing that myself. The function was basically adapted from the code of the plugin:

function save_search($searchstring, $numresults) {
global $table_prefix;
// Save into the DB. Usually this will be a new query, so try to insert first
$query = "INSERT INTO {$table_prefix}searchmeter (terms,date,count,last_hits) VALUES ('$searchstring',CURDATE(),1,$numresults)";
$success = mysql_query($query);
if (!$success) {
$query = "UPDATE '{$table_prefix}searchmeter' SET count = count + 1, last_hits = $numresults WHERE terms = '$searchstring' AND date = CURDATE()";
$success = mysql_query($query);
}
return true;
}

Constructing the Yahoo! API query
The second thing wasn't too hard to do either, as Yahoo! returns a snippet with the searchresult for the query. The REST query is constructed as follows:

$query = "site:yoast.com+".urlencode($searchstring);
$request = 'http://search.yahooapis.com/WebSearchService/V1/webSearch?appid='.$yahooappid.'&query='.$query.'&output=php';

The part output=php makes the API return serialized PHP, which, after calling unserialize, turns into a nice clean array, which you can then loop through to display the results.

The only thing left was adding the search box to my layout for the non-blog pages, and fixing the blog to look the same. In the theme I had to change the action URL of the searchform.php file to /search/, and there it was: my new site wide search function!

So far, it's all good. I've got a few things left, like building in paging so you can see more than 10 results. I've got one thing that bothers me though: it's a bit slow. Of course I could solve this by spidering my own site with something like ht://Dig, but I think there ought to be a better solution... Perhaps you guys and girls know of one?

Implementing a sitewide search function is a post by Joost de Valk on Yoast - Tweaking Websites.A good WordPress blog needs good hosting, you don't want your blog to be slow, or, even worse, down, do you? Check out my thoughts on WordPress hosting!

If you use "old-style" CSS hacks, you're bound to end up in trouble once the IE team decides to fix yet another bug. Because that's what these CSS hacks do: they rely upon bugs in IE to make sure it parses the CSS the way YOU want it to. Conditional comments, on the other hand, rely on a built-in feature, provided to you by the IE developer team to work around your problems. Which one of these do you think has the most chance of surviving the coming years? Right.

Richard Rutter gives a very wise comment on Jens' post, basically agreeing with my opinion, but he says the following as well:

In terms of reliable use among teams, it is of course advisable to avoid CC or CSS hacks wherever possible, however as we all know life isn’t that simple. So where IE-specific workarounds are needed, our workflow is to put those rule in a separate style sheet called via CC and - most importantly - to document the normal style sheet where rules are being overwritten (as is normally the case).

Document those overrides, and do that all the time. If you do that, conditional comments are surely the best way to make sure your layout works in al browsers.

The correct way of using conditional comments is a post by Joost de Valk on Yoast - Tweaking Websites.A good WordPress blog needs good hosting, you don't want your blog to be slow, or, even worse, down, do you? Check out my thoughts on WordPress hosting!

php_value session.use_trans_sid 0
php_value session.use_only_cookies 1

I also wanted Google to get a clean URL when it decided to spider one of the old URL's again, and didn't have access to mod_rewrite, so I redirected them with some PHP. The solution is quite simple:

if (isset($_GET['PHPSESSID'])) {
	$requesturi = preg_replace('/?PHPSESSID=[^&]+/',"",$_SERVER['REQUEST_URI']);
	$requesturi = preg_replace('/&PHPSESSID=[^&]+/',"",$requesturi);
	header("HTTP/1.1 301 Moved Permanently");
	header("Location: http://".$_SERVER['HTTP_HOST'].$requesturi);
	exit;
}

PHPSESSID in your URL? Learn to 301 redirect them with PHP is a post by Joost de Valk on Yoast - Tweaking Websites.A good WordPress blog needs good hosting, you don't want your blog to be slow, or, even worse, down, do you? Check out my thoughts on WordPress hosting!

So I implemented this colorpicker, you can check it out on the RSS viewer page of FeedRoll. It absolutely rocks!

FeedRoll is a post by Joost de Valk on Yoast - Tweaking Websites.A good WordPress blog needs good hosting, you don't want your blog to be slow, or, even worse, down, do you? Check out my thoughts on WordPress hosting!

The problem was caused by the fact that replace only replaced items once, where they should be replaced multiple times. I don't know where Sherman will be using the script yet, once I do I'll of course tell you all about it!

Sortable table script updated to v1.5.5 is a post by Joost de Valk on Yoast - Tweaking Websites.A good WordPress blog needs good hosting, you don't want your blog to be slow, or, even worse, down, do you? Check out my thoughts on WordPress hosting!

As usual, Technorati walks ahead of the pack is a post by Joost de Valk on Yoast - Tweaking Websites.A good WordPress blog needs good hosting, you don't want your blog to be slow, or, even worse, down, do you? Check out my thoughts on WordPress hosting!

It would be so cool if Google, or any other SE for that matter, knew how to handle searches like that. The same could be done for events, resume's etc. Google would probably want to make it simpler, or make another page for it, since I can't see my mum typing in "class:vcard", but the idea is good, and I think something people should be working on.

Update 18-2-2010: It took them a while, but it's hear now: Google & Microformats.

Googling for microformats is a post by Joost de Valk on Yoast - Tweaking Websites.A good WordPress blog needs good hosting, you don't want your blog to be slow, or, even worse, down, do you? Check out my thoughts on WordPress hosting!