Feature #19992
closedCheck for Extension Updates: Update Information should be written to sys_log
0%
Description
If you install/remove an extension this is always logged to sys_log table. Example: "Extension list has been changed, extension xyz has been removed/installed."
IMHO this functionality should also be provided for extension updates in Extension Manager. This would be a great feature to follow the update history.
The log entry could be saved like this: "Extension xyz has been updated/changed from version 1.0.0 to version 1.2.5."
(issue imported from #M10398)
Updated by Jonas Felix over 15 years ago
I could not found any sys_log insert calls in the em/ module. Where does the extension manager log anything? I would like to patch that!
Updated by Martin Kutschker over 15 years ago
eg line 2047 $GLOBALS['BE_USER']->writelog(5,1,0,0,'Extension list has been changed, extension %s has been %s',array($extKey,($this->CMD['load']?'installed':'removed')));
Note that this is buggy this way because two different messages (installed and emoved) have the same msg no. So while you're at it you could start with a bug fix that creates the new messages 5.1.1 and 5.1.2 for installing and removing as a starter. And please add the version number in the new log message.
Updated by Chris topher over 14 years ago
@ Jonas: Still interested in providing a patch?
Updated by Susanne Moog over 13 years ago
- Status changed from Needs Feedback to New
- Target version changed from 0 to 4.7.0
- Complexity set to medium
Updated by Alexander Opitz over 11 years ago
- Status changed from New to Needs Feedback
As this report is very old, is the handling in newer TYPO3 CMS Versions (like 6.0/6.1) more like you expect it?
Updated by Alexander Opitz about 11 years ago
- Status changed from Needs Feedback to Closed
No feedback for over 90 days.
Updated by Jonas Felix about 11 years ago
- Status changed from Closed to New
This is still a needed request. It's still not solved.
Updated by Mathias Schreiber almost 10 years ago
- Status changed from Accepted to Closed
Taken into account in #63909.
The issues are not linked on purpose, so the refactoring ticket does not get bloated with relations.