Developer Mode

inter · October 26, 2012, 08:09:48 AM

Hi!
My idea!
Make a new version of the developer mode setting
so that from the admin area you can change the value of the variable $db_show_debug.
Thanks!

mrintech · October 26, 2012, 10:12:40 AM

Hi

Your site tiraspol . me has been blocked by Kaspersky:

vbgamer45 · October 26, 2012, 10:26:02 AM

Quote from: Inter on October 26, 2012, 08:09:48 AM
Hi!
My idea!
Make a new version of the developer mode setting
so that from the admin area you can change the value of the variable $db_show_debug.
Thanks!

I agree since a lot of people do not know about that setting

emanuele · October 26, 2012, 10:38:53 AM

The fact that people don't know something exists is not bad by default.

Don't know, seems a bit too much an option for development.
Make more evident the option exists yes, it's a good point.

inter · October 26, 2012, 11:38:01 AM

Quote from: mrintech on October 26, 2012, 10:12:40 AM
Hi

Your site tiraspol . me has been blocked by Kaspersky:

ups, thanks for report
I use avast

Arantor · November 26, 2013, 12:48:49 AM

This is an interesting one. I know I changed it for <the fork that shall not be named>, to make it more accessible, but there's a whole slew of things attached to it.

Most importantly, security. The way things are currently built, it is not actually possible to make this happen from the admin panel. There is physically no way to export a true boolean value out into Settings.php; this is entirely intentional and by design - every little bit of security helps. As it stands, to enable this you need to go into the file directly to change it.

This is consistent with other forum systems; anyone capable of understanding the output would be able to turn it on in the first place.

I dunno, I'm ultimately undecided about the work required to make this happen. I know I did it more extensively elsewhere but there were consequences to that; you have to start logging immediately in all cases and then - and only then - ditch logging if you know the user couldn't see it anyway. It just gets messy.

Suki · November 26, 2013, 09:06:23 AM

I don't know how useful this would be to be honest, it will just save you some time but thats about it. If you have the need to see the debug info chances are you already know how to do that.

Gargoyle · November 26, 2013, 07:37:20 PM

Tell me of this developer mode... Curious now.

Arantor · November 26, 2013, 07:42:33 PM

Add $db_show_debug = true; to Settings.php before the closing ?> in the file.

Gargoyle · November 26, 2013, 07:47:10 PM

Im guessing bad stuff with be in red then? Neat lil feature!

Arantor · November 26, 2013, 07:49:34 PM

Well, it's not 'bad stuff'. On occasion it can be extremely useful for debugging by seeing what queries (and what other stuff) is happening on the current page load. But most people don't need it, and making it easier to access is not really a smart idea.

One of the things I actually kind of regret doing in Wedge now.

Gargoyle · November 26, 2013, 07:53:11 PM

Ah yes I see your point now.... Yeup just turned it off... I agree with you... LOL!!!

Arantor · November 26, 2013, 07:53:51 PM

There are certain times in the code we actually forcibly turn it off in 2.1 now because of the way things are done...

Arantor · November 28, 2013, 01:34:08 PM

But yeah, on reflection I think it's not a good idea to actually make this easier to get at. The whole reason for using true rather than 1/0 in the Settings.php was deliberately so people couldn't access it from the admin panel, so you could never force that information to be visible as it could be a security risk.

I see more reasons to say no than I do to say yes :/

News:

Developer Mode