Suggestion: content->controller->edit

[CodingJungle]

if your code for whatever reason throws an exception when editing a content item, you get this error:

which is fine for a live site, but for a developer, its a rabbit hole. so in system/Content/Controller.php  in the edit method's main catch, can we have something like:

if( \IPS\IN_DEV ){
    throw $e;
}
else
{
    \IPS\Output::i()->error( 'edit_no_perm_err', '2S136/E', 404, '' );
}

or possible it being logged to the logs? something more than a error message that says "you can't edit this any longer"? I just want this for in_dev mode, it would make things a lot easier than have to each version, go into and editing a core file for my dev environment in case my code is throwing a E_NOTICE, so i know what it is and can fix it faster.

thanks.

[HeadStand]

+1. I've run into this several times myself. It can be very frustrating.

[TSP]

If the error is caused by something else than what the message says, wouldn't that be a bug though? In which case I believe they would need to add an less specific error message.

[CodingJungle]

its a generic \Exception catch. I'd imagine its there since the content controller is used on the front end, I'd just like it when its in_dev, that it throw the error instead of catching it.

[teraßyte]

I run into this issue too recently.

[bfarber]

I've added debug logging here for a future release, so if you have debug logging enabled you'll be able to investigate the real exception easier.