Every Day Free – But Never Cheap!
Exclusively for RapidWeaver users • only free and low-cost stuff

Another RapidWeaver blog

Yes, it's true: one more blog about our favorite web site building application for MacOSX. But this one is a little different. It started back in 2011 as a blog focusing solely on free and low-cost stuff for (producing a web site with) RapidWeaver: themes, tools, tips, tricks, anything, as long as it was free – or low-cost.
    Over time, the Stacks plugin became more popular, and coding yourself was no longer an option for many people, so I started to develop my own stacks in the spirit of the blog: free (well, actually pay-what-you-want) and low-cost.
    This blog evolved with it, and is now primarily about those new stacks, although from time to time I will post about other free and low-cost stuff for RapidWeaver.

ShareThis | follow me on twitterFollow me on Twitter

Do you know something free (or low-cost) & useful related to RapidWeaver not mentioned here? Have a suggestion for a subject to write about here or for a new stack?
Tips, questions and remarks are always welcomed.
Just and help to expand this little blog!

A 404 page that works

A custom 404 page is more or less essential if you don't want to lose visitors. It's always annoying to be confronted with a 404 page, and the chances are real they will leave immediately, especially when it's such an ugly standard 404 page. A well designed 404 page can gently lead them to a more useful page. And remember: it's not always you fault when they land on a non-existing page. You never know who has done you the pleasure to link to your site, but make a typo in the url.
There are many tutorials out there that explain how to make such a page and set up the .htaccess file, so there's no need for me to repeat that here. The standard solution advocated is to put the line
ErrorDocument 404 /notfound.html
in the .htaccess file.

So, you made a cool 404 page for your site in RapidWeaver and edited the .htaccess file as explained in one of the may tutorials and guess what? It sometimes works, but sometimes doesn't… Sometimes the page is shown without any CSS styling, and the links don't work. The problem occurs when the faulty url is supposed to be in another directory than the one the 404 file lives in. Sounds complicated, but when you take a look at this little demo site I made, you'll see that it's in fact really easy. Just take a look at Part I to Part IV and you'll not only understand the problem, but also find a super-easy solution.

(When you're just interested in the solution, you can of course skip all the in-between-stuff and jump straight to the solution.)

Update: you may also want to read A 404 page that works #2 (about a sitemap on your 404 page and a 404 page on an IIS server).

See older posts...