BLOG:CMS :: Support Forum

This isn't a question, it's a mini HOWTO on getting FancyURL's to work in a rather particular case. If you've tried everything else and they still don't work, this might help.

Summary:
Change

ForceType application/x-httpd-php

to

SetHandler application/x-httpd-php

in the .htaccess.

The normal process for configuring FancyURL's (Radek's instructions):
- your webhosting MUST support .htaccess and FilesMatch
- copy files from /extra/fancyurls/ to root dir
- modify fancuurls.config.php file (set up your domain URL)
- switch to FANCY URLs in Global Settings

My problem:
I set up BLOG:CMS on my OS X iBook and enabled FancyURL's. It worked fine. I uploaded to website and everything worked - except for FancyURL's. The odd thing is, each time I tried to access a FancyURL (like /archive) I got a "500 Internal Server error" but the error didn't show up in my Apache error logs.

After hours of frustration, trawling through the support forums and confirming that I'd done everything perfectly right, I discovered my webhost uses a little extra program called PHPSuexec which runs on top of Apache. I don't know exactly what it does, suffice for some cool security stuff, but it stuffs up the normal way of getting FancyURL's working.

Luckily, the fix is really simple - here's my new code:

ErrorDocument 404 /error.html
<FilesMatch "^archive|archives|blog|category|extra|feed|item|member$">
    SetHandler application/x-httpd-php
</FilesMatch>

This works and is live - check out my site at http://www.futurechurch.co.za.