English spoken conference

Symfony 5: The Fast Track

A new book to learn about developing modern Symfony 5 applications.

Support this project

WARNING: You are browsing the documentation for Symfony 4.0 which is not maintained anymore. Consider upgrading your projects to Symfony 5.0.

You are browsing the Symfony 4.0 documentation, which changes significantly from Symfony 3.x. If your app doesn't use Symfony 4.0 yet, browse the Symfony 3.4 documentation.

Reporting a Bug

Reporting a BugΒΆ

Whenever you find a bug in Symfony, we kindly ask you to report it. It helps us make a better Symfony.

Caution

If you think you've found a security issue, please use the special procedure instead.

Before submitting a bug:

If your problem definitely looks like a bug, report it using the official bug tracker 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 obvious or affects more than one layer, providing a simple failing unit test may not be sufficient. In this case, please provide a reproducer;
  • Give as much detail as possible about your environment (OS, PHP version, Symfony version, enabled extensions, ...);
  • If you want to provide a stack trace you got on an HTML page, be sure to provide the plain text version, which should appear at the bottom of the page. Do not provide it as a screenshot, since search engines will not be able to index the text inside them. Same goes for errors encountered in a terminal, do not take a screenshot, but copy/paste the contents. If the stack trace is long, consider enclosing it in a <details> HTML tag. Be wary that stack traces may contain sensitive information, and if it is the case, be sure to redact them prior to posting your stack trace.
  • (optional) Attach a patch.

This work, including the code samples, is licensed under a Creative Commons BY-SA 3.0 license.