Feature #80289
closedAlow to globally disable devLog
100%
Description
Somehow I always assumed that $GLOBALS["TYPO3_CONF_VARS"]['SYS']['enable_DLOG'] = 0
globally disables devLog.
Since today I know I was wrong after we discovered, that the database of one project grew up to 25GB in just few weeks.
So I tried to investigate why devLog is stil writing data even though I have seen 'enable_DLOG' = 0.
I see now that the API method GeneralUtility::devLog() dos not care about that setting at all. It is up to the devLog extension developer to check if he actually can call this method.
This is not very fortunate in my opinion. A developer can forget to check for TYPO3_DLOG==1
and the user of such extension is fully unaware of the implications.
I find it much more consistent and clear, if the setting ['enable_DLOG'] = 0 globaly disables any devLog possibilities.