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 expand this little blog!

A 404 page that works #2

Over a year ago, I wrote about how to make a 404 page work properly with RapidWeaver. Judging by the number of emails I get about this subject, it appears to be a relevant matter to many of you. Some additional issues became apparent, so here's a sequel with two advanced tips.

Tip 1: a sitemap on your 404 page
Showing your sitemap on the 404 page using PlusKit's can be a good idea, especially when not all menu items are visible (e.g. with a drop down menu). You're visitor can go to a more useful page with a single click. However, the links in the site map may not work properly anymore, so when clicking them you will end up on the 404 page again…

As usual, the solution is quite simple once you know it: in Setup > Advanced set File Links Are to Relative to Website Address. Thank you Dick for pointing this out!

Tip 2: a 404 page on an IIS server
I try to avoid IIS servers as much as any other Microsoft product, because I find them far more difficult to handle than Apache servers. For that reason, I'm all but an IIS specialist, but as far as I know, in some cases there is no way to set a full url to your custom 404 page when your site is hosted on such a server. In that case, the trick from my original post useless. But don't despair, there's a solution!. It's not ideal, but a least it works…

1. Let's assume you have set a custom 404 page on the IIS server where your visitors are directed to like www.mysite/404.html.

2. Duplicate this page and give it a proper folder and file name, e.g. make the location www.mysite/not-found.html.

4. Replace your original 404 page with a built in HTML page. Make sure you make the folder and file name the same as on the old page!

5. In this new 404 page, go to Page Inspector > Page and disable Apply Theme.

6. Paste the following code in the main content area of this page:
<!DOCTYPE html>
<html>
   <head>
       <meta charset="UTF-8" />
           <title>Not Found</title>
           <meta http-equiv="refresh" content="0; url=http://www.mysite/not-found.html">
   </head>
   <body>
   </body>
</html>

Don't forget to change the url (http://www.mysite/not-found.html) to the url of your 404 page!

7. Publish.

What happens now, is that when a visitor tries to visit a non-existing page, the server will redirected him to www.mysite/404.html, and from there he will immediately be redirected to www.mysite/not-found.html – which is a fully working 404 page.

Ok, I admit it's quite a hassle, and in the end it's still a dirty trick workaround. And yes, your visitor may see a flash of white when redirected. But until somebody comes up with a better idea I'm using this solution…

See older posts...