The Issuetracker and You
Please search for an existing issue before reporting your problem.
The report will be publicly visible. So, don't include passwords or other confidential information.
Proper issue self checklist
Am I using an ancient revision/version and should update before reporting a possibly fixed issue?
Am I using any modification to core or database that could cause this issue?
Is it clear which branch I am using? (3.3.5/6.x/other)
Did I include the revision of the core I am using?
Did I include the version of the database I am using?
Did I include the operating system I am using?
Did I include the steps to reproduce the problem?
Did I explain what is wrong and what is the expected behavior/output?
Frequently Asked Questions
Issue description template
**Description**:
**Current behaviour**: Tell us what happens
**Expected behaviour**: Tell us what should happen instead
**Steps to reproduce the problem**:
1.
2.
3.
**Branch(es)**: 3.3.5 / 6.x (Select the branch(es) affected by this issue)
**TC hash/commit**:
**TDB version**:
**Operating system**:
[//]: # (This template is for problem reports, for other type of reports edit it accordingly)
[//]: # (If this is a crash report, include the crashlog with https://gist.github.com/)
[//]: # (For fixes containing c++ create a Pull Request)
While it is not mandatory to use the example above, we recommend it. (Adapted from Google Code)