Table of Contents

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 asetting you could tune?

You should also search theforum 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 DokuWiki bugs should be reported in our bug tracker at GitHub located at:https://github.com/dokuwiki/dokuwiki/issues. For bugs in plugins and templates use the plugin's own bugtracker — you'll find a link to that on the plugin's documentation page.

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 you can provide additional information to aid fixing the bug. See below on how.

As mentioned above, DokuWiki bugshave to be reported athttps://github.com/dokuwiki/dokuwiki/issues. You will need a free GitHub account to do so. Pleasedo not report bugs anywhere else (IRC, Twitter, Forum). The Bug Tracker at GitHub is the only canonical way to report a bug. Again: report plugin bugs in the plugin's bug tracker.

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, template, auth backends, weird network config, etc.)
• Exact steps to reproduce the problem
• Screenshots
• What did you try to fix the problem and what where the exact results?

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 readHow 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 logs:

• Server/PHP Error Logs
• DokuWiki Error logs
• JavaScript Console log

The following provides more details on this:

Whenever something goes fatally wrong, PHP will just stop processing your request. This usually results in ablank or partially rendered page. Sometimes errors are less grave but things are still missing.

In all of 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 web server's error log, the system global log or a specific PHP error log. This is configured in theerror_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 where to find that log. If you don't have access tophp.ini and can't find the log file you could also try adding the following to the.htaccess file in your DokuWiki root folder:

php_value display_errors 1php_value display_startup_errors 1

That may send the error message to the browser.

Another solution might be theshowphperrors plugin, it could be able to show the error in the browser in some cases.

Since the Igor release (July 2022), DokuWiki logs also errors. Via admin interface you can use theLogViewer. If the LogViewer cannot reached, you can find the log files in your file system in[wiki_folder]/data/log/error/<date>.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 yourconfig 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.

• [issue-open]: bin/plugin.php doesn't suppor $auth object by solewniczak (2025-03-21 13:58)
• [issue-open]: XML-RPC dokuwiki.appendPage does not handle attributs by gitahz (2025-03-15 01:47)
• [issue-open]: Avoid bot loops using stricter access controls on media manager by leonbottou (2025-03-13 19:40)
• [issue-open]: getallheaders support is sketchy by splitbrain (2025-03-12 12:22)
• [issue-open]: Exceptions in remote API return zero Error code by splitbrain (2025-03-12 09:08)
• [issue-open]: authldap too slow by deepsingh111 (2025-02-24 18:09)
• [issue-open]: Dokuwiki can be used to send emails to arbitrary email addresses by drtonyr (2025-02-24 12:07)
• [issue-open]: Search: Matching full word matches before partial word matches and general order improvements. by racquetmaster (2025-02-23 16:50)