4. Reporting Bugs
Hinton design uses a bug tracking system to store, list and manage all reported bugs, it can be found at the location listed below. Please DO NOT post bug reports to our forums, they will be locked. In addition please DO NOT use the bug tracker for support requests. Posting such a request will only see you directed to the support forums (while taking time away from working on real bugs).
http://bugs.hintondesign.org
While we very much appreciate receiving bug reports (the more reports the more stable phphg will be) we ask that you carry out a few steps before adding new entries:
- Firstly determine if your bug is reporductive, how to determine this depends on the bug in question. Only if the bug is reproductive is it likely to be a problem with phphg (or in some way connected). If something cannot be reproduced it may turn out to have been your hosting provider working on something, a user doing something silly, etc. Bug reports for non-reprodiceable events can slow down our attempts to fix real, reproduceable issues.
- Next please read or search through the existing bug reports (remember to check open AND closed reports!) to see if your bug (or one very similar to it) is already listed. If it is please add to that existing bug rather than creating a new duplicate entry (all this does is slow us down).
- Check the forums (use search) to see if people have discussed anything that sounds similar to what you are seeing. However, as noted above please DO NOT post your particular bug to the forum unless it's non-reproduceable or you sure it's related to something you have done rather phphg.
- If no existing bug exists then please feel free to add it.
If you do post a new bug (i.e. one that isn't already listed in the bug tracker) then please include the following details:
- Your server type/version, eg. Apache 1.2.22, IIS 4, Sambar, etc.
- PHP version and mode of operation, eg. PHP 4.1.1 as a module, PHP 4.0.1 running as CGI, etc.
- DB type/version, eg. MySQL 3.23.32, PostgreSQL 7.1.2, MSSQL Server 2000 SP1, etc.
Please also be as detailed as you can in your report, if possible list the steps required to duplicate the problem. If you have a fix which you are VERY SURE works (and is consistent with our coding guidelines) and does not introduce further problems or incompatibilities please let us know. However only include it in the bug report if you really must, if we need it we'll ask you for it.
Once a bug has been submitted you will be emailed any follow up comments added to it. Please if you are requested to supply additional information, do so! It is extremely frustrating for us to receive bug reports, ask for additional information but get nothing. In these cases we have a policy of closing the bug, which may leave a very real problem in place. Obviously we would rather not have this situation arise.