Table of Contents
I only get a blank or partial page
I only get a blank (empty) page when running DokuWiki or the output stops right after the template header. What's the problem?
This indicates some fatal error occurred which aborted the running PHP process without sending any output to the browser. Fatal errors are commonly triggered by faulty plugins, language or config files. To find out what happened, you need to look up the error message in the appropriate error log.
Error Log
Where that error log is located varies from setup to setup. Errors might be logged to the webserver's error log, the system global log or a specific PHP error log. This is configured in the error_log directive in php.ini.
Typical locations are:
- /var/log/apache2/error.log
- /var/log/apache/error.log
- /var/log/httpd/error.log
- /var/log/syslog
If you are using a shared server, most of these servers might write the PHP error log to a error_log file next to the PHP file that caused the error. Sometimes it's at the DokuWiki root, but other times you want to search through the subfolders as well. If you still cannot find it, you might want to contact the administrator of the server.
If you absolutely can't find the log file, you can try to install the showphperrors plugin, it might be able to show the error in the browser in some cases.
DokuWiki Error logs
Since the Igor 2022 release, DokuWiki logs also errors. Via the admin interface you can use the LogViewer. If the LogViewer cannot be reached, you can find the log files in your file system in [wiki_folder]/data/log/error/<date>.log.
Some sources of a fatal error
- Adding &purge=true to the URL may fix a problem if an error persists after upgrading a faulty plugin.
- If the full template (e.g. header and footer) is shown, but the wiki content isn't rendered your disk might be full or refer to largepage.
- If enabled, php_blenc.dll and php_operator.dll can cause this behavior. Disable these modules in your php.ini file.
- The findbadphp.php script might help you with finding certain errors, but is no replacement for having the real error message from the error log.
- Simply deleting the associated meta file can sometimes fix the problem.