This is a static dump of issues in the old "Flyspray" bugtracker for DokuWiki. Bugs and feature requests
are now tracked at the issue tracker at Github.
Closed
Works for me
FS#1042 [[1]] "This topic doesn't exist" regardles of the page requested
other
2007-01-08alpopov
This is a hard to reproduce bug that happens only in Firefox. All of the sadden, dokuwiki starts returning [[1]] page regardless of the actual page requested. When tried from the IE it works fine at the same time.
Clearing browser/wiki cache doesn't solve the problem.
I tried removing Firefox profile (from C:\Documents and Settings\username\Application Data\Mozilla\Firefox\Profiles\xxxxxxxx.default) and restart Firefox: it will solve the problem for a short time, but then in a few hours the problem will re-appear. It tried different versions of Firefox (1.5-2.x) and it happens with all of them, with or without extensions.
There's nothing related to this condition in Apache's error.log. Snippet from the access.log is attached. In this snippet I reqiest page named "dba" and you can see that indexer is trying to index page "1".
Please advice where should look for the cause of this problem and which additional steps should I take.
Most likely cause: look for a place where you used '+' rather than '.' for a string concatenation; '+' is mathmematical and the string is evaluated to 1 or 0 as a boolean then added resulting in 1. It may be in Javascript (and thus unique to Firefox somehow), but I'd bet its in a PHP script like your template.
It could be in your .htaccess file and some re-direct isn't escaping a regular expression correctly bouncing you to ID=1 rather than ID=\\1 or the like. Typically, this is in your web root and should redirect requests for /index.* to /wiki/doku.php
You may have a bounce page that bounces to the page with ID=1. You can use, for example, the following to generate a bounce within the wiki:
<html>
<meta http-equiv="REFRESH" content="0;url=http://www.puzzlers.org/dokuwiki/doku.php?ID=1">
</html>
2010-06-26andi
Can't reproduce. bug is so old I assume this to be fixed meanwhile