-
Notifications
You must be signed in to change notification settings - Fork 37
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.
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
Issue with passing sessions in testing environment #5
Comments
I have this same issue, but it works in my local environment and does NOT work in my production environment. Were you able to find a fix for this or did you just stick with your temporary work-around? |
Hey! Important message, please visit http://anm-metro.com/may.php?2tehi |
Hello! New message, please read http://cognibyte.com/fresh.php?sx2j |
Hey! Open message http://ittcorp.de/wanted.php?5d3u El software de antivirus Avast ha analizado este correo electrónico en busca de virus. |
Hey! Open message http://seoxanh.com/them.php?e0wq1 |
Hello, Yours faithfully, [email protected] |
Hello! Just take a look at that cool stuff I just have found, it's so fantastic! Here it is http://thrive.outdoorrenovators.com/aestddab Bests, ghosst |
Dear! Sent from my iPhone, ghosst |
I'll start by saying that this is most likely not a laracasts/Validation error, but since the entire setup is exactly what @JeffreyWay suggested in the README it's probably the best place to ask for help.
So here's the issue:
I've got a FormValidator setup and the exception is caught in the error handler under
global.php
, which doesEverything works just fine when using this pattern in the production environment.
However, I'm storyBDD-ing it with Behat, which triggers the testing environment via the URL (i.e. my-project.testing vs my-project.dev)
The problem is, the errors do not appear in the view after the redirect, if I
dd()
in the error handling closure, I can see that the validator returns the expected errors, however they never get passed to the view.Worth mentioning the fact that my session driver for the testing environment is set to native, and I've tried cookies as well, so I think it's rather an issue with Redirect + flashing session data happening in this particular situation.
I have a temporary work-around, with the try..catch working in the controller, but I'd like to go back to using global error handling rather then the ugly try catch version.
The text was updated successfully, but these errors were encountered: