As RTH editor Ryan McGreal posted earlier, RTH has updated the backbone code that runs the site with the intention of improving user functionality while also making the site easier to maintain.
However, in any new software there will inevitably be bugs and glitches that weren't caught during beta testing and it will be up to the community to inform the editors of any problems that are discovered.
This can be done either through email, or if you have a github account (it's free) you can post issues directly to the site's bug database.
Now that you know where to report problems, the question is what sort of information needs to be included in a report. Basically, when writing the report you should do your best to answer the following questions:
Remember, the less information you provide, the more difficult it is to address the problem. Simply saying "It doesn't work..." will not lead to a solution. Also, once your report has been submitted, it may take some time for the issue to be resolved so don't submit the same problem repeatedly. Be patient and watch for updates to the issue in the database.
If there are any further questions/comments regarding error reporting feel free to post them below.
You must be logged in to comment.
There are no upcoming events right now.
Why not post one?