Bug #24040

Handling deprecation log

Added by Ben van 't Ende over 10 years ago. Updated over 6 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
-
Target version:
-
Start date:
2010-11-13
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
4.3
PHP Version:
Tags:
Complexity:
Is Regression:
No
Sprint Focus:

Description

The deprecation log is shown in the reports module. There has been a huge discussion whether or not the deprecation log should be turned on or of by default. I think it should be turned of because users are not interested in it at all. On the other hand if there is an easy way to deal with the deprecation log it is fine if it is turned on by default. Here are three suggestions for the deprecation log handling in the reports module to make it more user friendly.

1. Show the size of the deprecation log (if it is small you can leave it as it is)
2. Deactivate the deprecation log (at the moment you need to dive into the install tool and search for it to turn it off - in the text it is also suggested to turn it off when it gets to big)
3. Clear the deprecation log (especially when it is very large you might not want to waste that space)

(issue imported from #M16373)


Related issues

Related to TYPO3 Core - Feature #23387: Add a feature to remove/clear deprecation_xyz.logClosed2010-08-17

Actions
Related to Logging Project - Task #23489: Avoid duplicate entries in deprecation logRejected2010-09-01

Actions
Related to TYPO3 Core - Bug #24227: Deprecation Log blocks systemClosed2010-11-29

Actions
Related to TYPO3 Core - Feature #62850: Possibility to clear deprecation.log in Install ToolClosed2014-11-11

Actions
#1

Updated by Ingo Renner over 10 years ago

The discussion has been long, that's true, but IMO we agreed on having it on by default. That's the only way to allow us to stay backwards compatible and at the same time still remove old APIs.

1. is implemented in the status report already
2. and 3. are not in the scope of the reports module (or at least the system status report) as it is a pure informative module, only reading information.

I could see a report listing and analyzing the deprecation log though.

#2

Updated by Ben van 't Ende over 10 years ago

In order to have a broader acceptance of the deprecation log we need to have the possibilities I mentioned in 2 and 3. Should this be in the Install Tool then?

#3

Updated by Markus Klein over 8 years ago

  • Target version deleted (0)

If we implement #23489 then is will not be a problem anymore.

#4

Updated by Alexander Opitz about 7 years ago

  • Status changed from New to Needs Feedback
  • TYPO3 Version set to 4.3
  • Is Regression set to No

Hi Ben,

as #23489 is rejected, we should go forward here. As I can see point 1. and 2. is done, so clearing deprecation.log in install tool is the only thing left over.

Do I understand this correct?

#5

Updated by Alexander Opitz over 6 years ago

  • Status changed from Needs Feedback to Closed

The last missing part got his own issue: #62850

Also available in: Atom PDF