When loading a page of the template, I'm getting an Error 500 (Internal Server Error), what should I do?
It may occur when setting very permissive file permissions (777) and your hoster added some security checks to avoid this. Try to lower permissions. Normal operations seems to have succes in this case, but often cache files can not be written. try setting the permissions to 766, most scxripts will work.
This can also happen if the .htaccess files in your (root) directory use settings or trigger actions which are not supported by your Apache server config. If you're not running the server yourself, but are registered with a webhost, you can either ask your webhost to enable the options in question, or just comment them out in the htaccess files.
Another problem can occur if you're using .htaccess files using UTF-8 codification with Byte-Order Mark (BOM). Reencode your .htaccess files properly without BOM to solve this.
There coulds have been a change in default PHP settings, so try to run the Test program startHere.php again and check if there are errors.
When certain code examples are entered on a page, the Server returns a “Error 403 – Forbidden”, “Error 406 – Not Acceptable”, “Error 403 – Forbidden”, “503 – Service Temporarily Unavailable” or similar errors. What's the problem?
This is usually a problem caused by overly-restrictive security policies set in the webserver (usually mod_security) or an application level Firewall (Sophos Firewall Webapp Control is known to be problematic).
There is no way to fix this in the Leuven-Template, because it is not a problem caused by the template scripts themself. You need to check your webserver or application firewall audit logs to identify the problematic rule and disable it.
While using the template, I'm often getting errors reading: “Writing xyz failed”. How come?
If you made sure your which folders have to be set are correct, you're most probably with a webhost which has enabled PHP's Safe Mode. Unfortunately, this keeps the template from writing to directories using the web interface, because all actions are triggered with the user ID of the wwwuser, but only the FTP user is allowed to write to the directories on your webspace.
Solution: Get your hoster to disable the the safemode option or find another provider.