Posting bug in bugtracker

CaMer0n by CaMer0n in e107

The dev team appreciates all of the people that are posting bugs, we've been on a mission to try to clear them recently.

The dev team appreciates all of the people that are posting bugs, we've been on a mission to try to clear them recently. We've ran into a few problem and just want to make sure everyone understands:

* Please make sure you have a recent copy of the CVS before posting the bug. Even bugs from a cvs 1 day old may be out of date.

* If you are looking for a recent fix and see it noted as fixed in the changelog, please make sure you have the updated file. There is a delay between the dev commit and the time the anonymous checkout will see the new files. The changelog will show you the most current revision number and you can open up the file in an editor to check your version of the file. If it's marked as fixed and you have the new file and the bug is still there, please indicate that also.

* Make sure your database validates first. If you run the database validity check and it fails, that is the first thing that needs fixed. It may be that the known good file is bad, but we need to get that fixed and then we can move on to your problem.

* When posting your bug, please indicate the time you last updated, this really helps too.





This news item is from e107 v2 Bootstrap CMS
https://e107.org/blog/706.html