Bug #55211
closed
Depreciation Log seems to cache old issues
0%
Description
After deletion of the depreciation log in BE (Reports -> Delete Depreciation Log) it is deleted from file system (checked w. terminal).
Re-checking after some FE action brings up old entries again, which shouldn't be there, since they have been deleted earlier. Looks like a caching issue.
Updated by Markus Klein almost 11 years ago
- Status changed from New to Needs Feedback
The deprecation log is not cached at all!
Are you sure the deprecations found in the new file are not present in the system anymore?
Updated by Thomas Skierlo almost 11 years ago
Yes, I've had 'loadTCA' calls in 4 extensions, and I've removed them all yesterday. Since the messages always reappeared under Reports, I checked the file directly using a terminal. Non of the (old) messages could be found here, so the file which is written is perfectly ok.
If I open this very log using Reports, all old messages re-appear (without effecting the real file).
If I delete the file using Reports -> delete DL, file is deleted from file-system.
Reopening it in BE after some action: back again, those sticky little bastards. With dates older than the last file deletion.
Updated by Wouter Wolters almost 11 years ago
Can you try to use the clear cache in the Install Tool. Probably you removed the loadTca from ext_tables.php files which is cached.
Updated by Thomas Skierlo almost 11 years ago
I did not clear the cache in the install tool. Only did it in the BE - AND - I deleted everything from typo3temp/Cache/ folder.
Anyhow. Doing it via the install tool seems to solve the problem.
Question is. What does a user expect here? After clearing the log, the file is physicaly deleted from file system and none of the 'old' errors finds it's way back into the real log again. So the written log always is correct.
If it would be a pure problem of caching ext_tables.php, those 'old' messages should re-occur in the (physical) log, since the cached (old) version should trigger them again. But they don't show up, except if viewing the log in the BE.
As long as we have no real/working "Clear all caches" in BE, it makes no sense to keep a function of log-clearing in the Reports module. Maybe it should be moved to the install tool as well?
Updated by Wouter Wolters almost 11 years ago
Have a look at this text: https://review.typo3.org/#/c/26912/3/NEWS.md
Updated by Alexander Opitz over 10 years ago
- Status changed from Needs Feedback to Closed
No feedback within the last 90 days => closing this ticket.
If you think that this is the wrong decision or experience this issue again, then please write to the mailing list typo3.teams.bugs with issue number and an explanation or open a new ticket and add a relation to this ticket number.