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.
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:
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.
Show.tiki.org snapshot creation is in progress... Please monitor http:///snapshots/ for progress. Note that if you get a popup asking for a username/password, please just enter "show" and "show".
Password reset was successful
Password reset failed
Show.tiki.org instance destruction is in progress... Please wait...
The public/private keys configured to connect to show2.tiki.org were not accepted. Please make sure you are using RSA keys. Thanks.
Unable to connect to show2.tiki.org. Please let us know of the problem so that we can do something about it. Thanks.
Show.tiki.org is currently under maintenance. Sorry for the inconvenience.
Unable to get information from show2.tiki.org. Please let us know of the problem so that we can do something about it. Thanks.
Show.tiki.org is in the progress of creating the new instance. Please continue waiting for a minute or two. If this continues on for more than 10 minutes, please let us know of the problem so that we can do something about it. Thanks.
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.
The URL for the show2.tiki.org instance that demonstrates this bug is at: http://. Note that if you get a popup asking for a username/password, please just enter "show" and "show". This is different from the initial login and password for a new Tiki which is "admin" and "admin".
For the install log, see http:///info.txt
Note that if you see PHP errors or a Tiki claiming to be missing third party software, the instance creation is probably not finished. Please wait a couple minutes and reload.
Snapshots are database dumps of the configuration that developers can download for debugging. Once you have reproduced your bug on the show2.tiki.org instance, create a snapshot that can then be downloaded by developers for further investigation.
Snapshots can be accessed at: http:///snapshots/. Note that if you get a popup asking for a username/password, please just enter "show" and "show".Create new snapshot
|No attachments for this item|