Skip to content

Exception namespace problem with 2.6.1 #12844

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
ghostika opened this issue Dec 4, 2014 · 9 comments
Closed

Exception namespace problem with 2.6.1 #12844

ghostika opened this issue Dec 4, 2014 · 9 comments

Comments

@ghostika
Copy link

ghostika commented Dec 4, 2014

After installing a brand new sf 2.6.1 ( with sf installer), I wanted to try out the new error page function, with the local/app_dev.php/_error/500 and the local/app_dev.php/_error/500.json urls, but I got a general 500 error:

Catchable Fatal Error: Argument 2 passed to Symfony\Bundle\TwigBundle\Controller\ExceptionController::showAction() must be an instance of Symfony\Component\HttpKernel\Exception\FlattenException, instance of Symfony\Component\Debug\Exception\FlattenException given
@stloyd
Copy link
Contributor

stloyd commented Dec 4, 2014

This was fixed, and version with fix was released: 2.6.2.

@perajovic
Copy link
Contributor

Hm, there is not 2.6.2 version in releases.

@stloyd
Copy link
Contributor

stloyd commented Dec 4, 2014

Sorry, I mean 2.6.1...

@nicolas-grekas nicolas-grekas mentioned this issue Dec 4, 2014
Closed
@stof
Copy link
Member

stof commented Dec 4, 2014

The issue is that #12821 has been merged, but this does not play well with BC layers we had to keep.

@fabpot
Copy link
Member

fabpot commented Dec 4, 2014

I have reverted the PR.

@ghostika
Copy link
Author

ghostika commented Dec 4, 2014

@stloyd as you see, I tried it with 2.6.1

@bkosborne bkosborne mentioned this issue Dec 9, 2014
Closed
@Tobion Tobion mentioned this issue Dec 13, 2014
Closed
@jeremylivingston
Copy link
Contributor

What is the game plan for addressing this? Currently it's not possible to debug error pages in development environments.

@stof
Copy link
Member

stof commented Dec 23, 2014

@jeremylivingston this is addressed already in the 2.6 branch. The fix will be part of 2.6.2 (which is not released yet).

@fabpot what is the ETA for the 2.6.2 release ?

@fabpot
Copy link
Member

fabpot commented Dec 24, 2014

@stof There are too many problems in current 2.6 to release 2.6.2 yet.

@fabpot fabpot closed this as completed Dec 24, 2014
@xabbuh xabbuh mentioned this issue Dec 30, 2014
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
6 participants
@fabpot @stloyd @stof @jeremylivingston @perajovic @ghostika