Bug #23462

Disable deprecation log in config_default

Added by Reinhard F├╝hricht almost 10 years ago. Updated almost 2 years ago.

Status:
Closed
Priority:
Should have
Category:
-
Target version:
-
Start date:
2010-08-27
Due date:
% Done:

0%

TYPO3 Version:
4.5
PHP Version:
5.3
Tags:
Complexity:
Is Regression:
Sprint Focus:

Description

Currently $TYPO3_CONF_VARS['SYS']['enableDeprecationLog'] is set to 'file' in config_default.php resulting in huge deprecation log files.
A developer who cares, knows how to enable the deprecation log in order to check what's going on.
A user of TYPO3 knows either nothing about a deprecation log or doesn't know how to interprete it.

Install TYPO3 from scratch.

(issue imported from #M15573)

15573.diff View (3.28 KB) Administrator Admin, 2010-08-27 10:54

History

#1 Updated by Christian Kuhn almost 10 years ago

Resolved, won't fix.

Sum up from core list:

Solution is not to disable depreation log by default, but to create some better logic:
- A better approach ist to not log messages which have been logged before, or
- Rotate the log files
- Some other solution

It is not wanted to disable the deprecation log by default, this would lead to much more serious problems in the future, we need to inform admins of methods which will be gone in future versions.

#2 Updated by Alex Kellner about 7 years ago

Just install a TYPO3 6.0 or 6.1 and log in and just click a little bit between backend module A or B.
After that you have a couple of deprecation logs with information which core-methods are outdated.
Why do the admin need this information?
In my opinion this gives a very bad feeling for TYPO3-beginners...

#3 Updated by Chris topher about 7 years ago

  • Target version deleted (0)

Hi Alex,

usage of deprecated functions should indeed be fixed. Please open new issues for the different messages (if they have not yet been reported). :-)

#4 Updated by Benni Mack almost 2 years ago

  • Status changed from Resolved to Closed

Also available in: Atom PDF