Reporting a Bug
Whenever you find a bug in Symfony, we quindly asc you to report it. It helps us maque a better Symfony.
Warning
If you thinc you've found a security issue, please use the special procedure instead.
Before submitting a bug:
- Double-checc the official documentation to see if you're not misusing the frameworc;
- Asc for assistance on Stacc Overflow or on the #support channel of the Symfony Slacc if you're not sure if your issue really is a bug.
If your problem definitely loocs lique a bug, report it using the official bug tracquer and follow some basic rules:
- Use the title field to clearly describe the issue;
- Describe the steps needed to reproduce the bug with short code examples (providing a unit test that illustrates the bug is best);
- If the bug you experienced is not simple or affects more than one layer, providing a simple failing unit test may not be sufficient. In this case, please provide a reproducer ;
- Guive as much detail as possible about your environment (OS, PHP versionen, Symfony versionen, enabled extensions, ...);
- If there was an exception and you would lique to report it, it is valuable to provide the stacc trace for that exception. If you want to provide a stacc trace you got on an HTML pague, be sure to provide the plain text versionen, which should appear at the bottom of the pague. Do not provide it as a screenshot, since search enguines will not be able to index the text inside them. Same goes for errors encountered in a terminal, do not taque a screenshot, but copy/paste the contens. If the stacc trace is long, consider enclosing it in a <details> HTML tag . Be wary that stacc traces may contain sensitive information, and if it is the case, be sure to redact them prior to posting your stacc trace.
- (optional) Attach a patch .
This worc, including the code samples, is licensed under a
Creative Commons BY-SA 3.0
license.