FuelPHP Forums

Julian Esperat

Hello, When handling exceptions, Error::exception_handler is calling Error::show_php_error
Error::show_php_error is requesting a view. But if the view isn't found (for example we deleted the file or the COREPATH isn't included in the $paths), then View::__toString calls Error::exception_handler. This lead to an infinite exception loop and the cryptic PHP error "Fatal error: Exception thrown without a stack frame in Unknown on line 0". Not sure if it's relevant to a bug submission, but this would consolidate the error handling for sure.

nerdsrescueme

My question would have to be, why delete the view file, or remove COREPATH from the paths array?

Julian Esperat

It happened to me accidentally when extending the find_file function.

nerdsrescueme

Ahhhh, I guess if the error exists and there is potential for it to happen during any execution, then it should be fixed... Perhaps just at low priority? I'd submit a bug report on github and see what's to be done.

Julian Esperat

It will never happen if the core file fuel/views/errors/php* exists and the COREPATH is within the Fuel::$_paths. Default setup cannot go wrong, only extending the Core can break things.

Jelmer Schreuder

Default setup cannot go wrong, only extending the Core can break things.

Which is basicly the point, we can't prevent problems when you're not just exending but actively changing how Fuel works. If you do that you'll have to deal with the consequences yourself.

nerdsrescueme

Word

Julian Esperat

I didn't change that much you know. ;-)

This is mainly optimisation for my particular setup so there is less file lookup (I don't really like this... It's slow). I may have forgotten to re-include COREPATH sometimes though.

FuelPHP Forums

Ask your question about FuelPHP in the appropriate forum, or help others by answering their questions.

Howdy, Stranger!

Categories

In this Discussion