When trackers are not present (perhaps lost or otherwise mistyped) a 500 (internal server error) is produced.
At the very least it should be throwing the correct error 404 (page not found), but ideally would produce a Tiki error reporting something like "Sorry that tracker does not exist" or something similar.
This situation of lost trackers happed on dev.tiki.org where trackers where lost:
https://dev.tiki.org/tiki-view_tracker_item.php?trackerId=5&itemId=4130
https://dev.tiki.org/tiki-view_tracker_item.php?trackerId=5&itemId=4129
They were indexed by Google and linked within the content of the tiki-sites. It looks bad flaunting server misconfiguration errors on our sites.
To help developers solve the bug, we kindly request that you demonstrate your bug on a show2.tiki.org instance. To start, simply select a version and click on "Create show2.tiki.org instance". Once the instance is ready (in a minute or two), as indicated in the status window below, you can then access that instance, login (the initial admin username/password is "admin") and configure the Tiki to demonstrate your bug. Priority will be given to bugs that have been demonstrated on show2.tiki.org.
To help developers solve the bug, we kindly request that you demonstrate your bug on a show.tikiwiki.org instance. To start, simply select a version and click on "Create show.tikiwiki.org instance". Once the instance is ready (in a minute or two), as indicated in the status window below, you can then access that instance, login (the initial admin username/password is "admin") and configure the Tiki to demonstrate your bug. Priority will be given to bugs that have been demonstrated on show.tikiwiki.org.
filename | created | hits | comment | version | filetype | ||
---|---|---|---|---|---|---|---|
No attachments for this item |