Error handling for non-existant view
-
Kris Jordan
This happens when there are non existent variables in the view.
-
Kris Jordan
- State changed from new to open
- Tag set to headers, view
- Milestone changed from Public Preview to 0.11.1
Caused by headers already being sent and attempting to resend in the error handler. This has been fixed. Raises another question which is being put in the 0.15 milestone:
If we reach an error in a view that would be considered a 500 level error - should we allow headers to be sent as otherwise? If not we need to cache the output of a view entirely before calling the send headers in view. Significant enough of a refactor lets push off to .15 and revisit the issue then.
-
Kris Jordan
- Milestone changed from 0.11.1 to 0.30
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.