Some desktop applications have a way to report errors. This would help us know which bugs happen the most often. For example, we could check for sql errors or hard php errors.
Of course, this would be totally optional. Even better would be for people to be able to share their Tiki configuration (anonymously) at the same time so maybe we could detect that bug X only happens with a specific combination of on/off settings.
Firefox talkback:
http://www.mozilla.org/support/firefox/faq#talkback
Of course, knowing about all the bugs doesn't automagically fix them. However, some are super easy to fix if we notice them, like this one:
http://dev.tikiwiki.org/tiki-view_tracker_item.php?itemId=1399
The same way TikiWiki community members can vote on bugs and feature request, the "crowdsourcing" of error reporting will make it easier to distinguish the most common issues. It would also be a hint that some very rarely reported issues are probably related to a rare server configuration.
The same way I invest to address the most voted on features/bugs, I would do the same here. Specifically, I would like to see reports of the top-10 Postgres-related errors. I am sure these are easy to fix and could make TikiWiki more useful to Postgres users. I would like to use Tiki on Postgres eventually.
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.
filename | created | hits | comment | version | filetype | ||
---|---|---|---|---|---|---|---|
No attachments for this item |