Project

General

Profile

Actions

Bug #81203

closed

parent::__wakeup() deprecated / log messages not useful

Added by Oliver Kleinecke almost 7 years ago. Updated almost 7 years ago.

Status:
Rejected
Priority:
Should have
Assignee:
-
Category:
-
Target version:
-
Start date:
2017-05-12
Due date:
% Done:

0%

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

Description

Hi !

We are using latest stable Typo3-Version (7.6.18) in productional environment, including self-developed extensions. As you can imagine, error-management is important to our company, to make future-updates safe etc. .. Unfortunately, our deprecation log gets filled with annoying messages about parent::__wakeup() calls ... even though none of our own current self-developed domain models makes any calls to this function.
Please update sysext-core to not use that deprecated function any more or remove the deprecation-warning until sysext core itself is properly updated.
In addition, those deprecation-log messages are indeed quite useless, because it lacks additional info, which model/modules are causing those log-entries.
I`d appreciate an overhaul of the deprecation-log-feature, to give more useful info !
Thanks in advance,
O. Kleinecke

Actions #1

Updated by Steffen Gebert almost 7 years ago

Hey Oliver,

may I ask, why you reported the issue in this project? We've seen couple of reports recently, which are in the category "OTHER > Server Team > forge.typo3.org", which is actually about issues regarding this issue tracker itself. Is there maybe somewhere a link pointing to the wrong place? Correct would be CMS > Core.

I'm moving this issue to there. Would be nice to receive your feedback.

Yours
Steffen

Actions #2

Updated by Steffen Gebert almost 7 years ago

  • Project changed from 9 to TYPO3 Core
  • TYPO3 Version set to 7
Actions #3

Updated by Wouter Wolters almost 7 years ago

  • Status changed from New to Rejected

I'm sorry but I have to reject this ticket. The code you mention has been deleted in version 8.0 and does therefor not exist in our latest stable 8,7 LTS release.
Version 7.6 is in high priority bugfixing and security updates only mode and will not receive such a change anymore.

The usage of the deprecation log logging in production is really not recommended. I suggest you to disable this on your production environments. The Install Tool presets suggest this configuration already for you to have a tiny bit more perfomance.

Actions

Also available in: Atom PDF