Project

General

Profile

Actions

Bug #43900

closed

Deactivate deprecation_*.log when enableDeprecationLog settings has an invalid value

Added by Michael Schams almost 12 years ago. Updated about 6 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
-
Target version:
-
Start date:
2012-12-12
Due date:
% Done:

100%

Estimated time:
TYPO3 Version:
4.5
PHP Version:
Tags:
Complexity:
easy
Is Regression:
Sprint Focus:

Description

Invalid value "1" in InstallTool (option: enableDeprecationLog) causes TYPO3 to write deprecation_*.log
Correct behaviour would be not to write anything if the system has been configured incorrectly.

In detail:

InstallTool -> show all configuration -> locate "enableDeprecationLog". Text reads:

Commalist: Enables the logging of deprecated methods and functions. Default is 'file'. The following options are allowed: file [...], devlog [...], console [...]

However, if the value "1" is used (which is an invalid value for enableDeprecationLog according to the text above and the documentation), TYPO3 writes typo3conf/deprecation_[HASH].log

Under normal circumstances, falling back to a specific (or safe) value is legitimate, if the system is misconfigured - but in this case, TYPO3 fills up the disk space if the deprecation_*.log is written, which introduces a risk for some sites (depending on extensions used and individual configuration).

Therefore, using an invalid value for the enableDeprecationLog setting should not write anything.


Files

issue-43900.diff (5.69 KB) issue-43900.diff patch for issue #43900 Michael Schams, 2013-04-28 07:03
Actions

Also available in: Atom PDF