Every software has bugs. We try to ship the best possible version of DokuWiki every time, but errors happen. This page is here to help you with reporting bugs you might encounter.

Before you report something, try to research if the problem you encounter, really is a bug. Maybe it is intended behavior for some reason? Maybe there's a setting you could to tune?

You should also search the forum if people had the same problem before. Maybe there's a fix already?

However if still in doubt, just open a bug report. We can always close it, should it turn out to not be a bug.

All bugs should be reported in our bug tracker at github located at: https://github.com/splitbrain/dokuwiki/issues

Use the search to check if your problem already has been reported. Also make sure you search through closed bugs as well - the bug might have been fixed already in development.

If the bug was reported already, check if can provide additional information to aid fixing the bug. See below on how.

When reporting a bug you should try to include as much information as possible that helps developers with identifying the problem.

This can include:

• DokuWiki version
• Operating system of the server and client
• The used web server
• The used PHP version
• The used browsers (try multiple)
• Everything that's special about your setup (plugins, auth backends, weird network config, etc.)
• Exact steps to reproduce the problem
• Screenshots

It is especially important to gather exact error messages! See if you can find error logs from the web server and the JavaScript console (see below).

Please also read How to Report Bugs Effectively for more tips on submitting useful bug reports.

As mentioned above, DokuWiki developers need detailed error messages to debug a problem. Sometimes those are printed directly to the screen, but sometimes they aren't. In those cases you might want to check the following options:

When ever something goes fatally wrong, PHP will just stop processing your request. The usually results in a blank or partially rendered page. Sometimes errors are less grave, but things are still missing.

In all those cases PHP will log an error message to some log file. Where exactly that log file resides is different from system to system. 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 on a hosted server, best ask your provider on where to find that log.

Sometimes things go wrong on the client side (inside your browser). To figure out what, you will need to access the JavaScript console of your browser. To do so use the following keyboard shortcuts:

If you see any errors (usually shown in red) in the console, go to your config manager and disable the compress setting. Reload the page and check the JavaScript console for errors again.

If you find errors in the JavaScript console you should always attach them to your bug report. Preferably the ones found with the compress setting disabled. However sometimes errors only show up with compress enabled - in that case send us these error messages.

• An error occurred while fetching this feed: http://pipes.yahoo.com/pipes/pipe.run?_id=02bfefe73ba14054570ce82f1929e433&_render=rss&owner=splitbrain&repo=dokuwiki