Skip to content

Fix FileLoaderImportCircularReferenceException errors #14342

Closed
@javiereguiluz

Description

@javiereguiluz

Symfony 2.6.5 version changed the way errors are displayed in the browser. Lately a lot of users are complaining about this new behavior: #14337, #14199, #1396, #14111, #14073.

Symfony 2.7 beta tried to solve this problem, but the result is not completely satisfactory.

To better understand the problem, check out the different error messages that you get when your controller uses the @Security annotation without importing its associated class.

Symfony 2.6.4

The error message is perfect.

2_6_4_web

Symfony 2.6.5 and 2.6.6

The error message is awful.

2_6_6_web

Symfony 2.7

You see 4 error messages instead of just 1. The good error is displayed at the bottom and the awful error is displayed first.

2_7_dev_web

This behavior only happens in the browser. If you use Symfony 2.6.5 or 2.6.6 in the console, you get perfect error messages:

2_6_4_cli

In my opinion this is a critical issue that should be fixed both for 2.6 and 2.7.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions