Skip to content
TYPO3Dev Companion

Report a wrong answer

An answer that names its source can be checked, and one that is wrong can be fixed in the source rather than argued about. This form is how the second half of that happens.

Used for the reply and for nothing else. It is not stored with the report.
How should we come back to you?
The release the installation runs, not the one the answer named.
The tool name and the question are enough to reproduce it. A screenshot is not.
What happens to it

It is read by a person. Where the answer came from bundled knowledge, the fix is a change to that knowledge and ships with the next release; where it came from your installation, the reply says what the tool read and why it read that.

Nothing is collected that you did not attach
The scope is the only thing beyond the six answers, it is optional, and what it holds is listed beside the box. No page on this site carries an analytics script.

Typical turnaround is two working days — longer where the answer has to be reproduced against a release the project no longer runs.

Three things that go elsewhere

This form is for an answer that was wrong. These are not that, and sending them here makes them slower rather than faster.

the repository
A bug in the server itself
Crashes, a tool that does not register, anything reproducible from a checkout. An issue is faster than this form.
documentation
A page that is wrong
Documentation is not answered from here. The page itself carries the way to report what it says.
security
Something that should not be public
A finding that affects an installation goes to the security address instead, and never through this form.