Bug #97789
closedMissing entries in System Log module
0%
Description
When the Web->Info Log module is used and a depth is selected, this value is saved into the be_user UC data.
Using the System->log module afterwards then uses the depth constraint to check if pid restrictions should be built up.
https://github.com/TYPO3/typo3/blob/main/typo3/sysext/belog/Classes/Domain/Repository/LogEntryRepository.php#L128
But since this value is loaded from the UC field and not even present in that screen, this check must be changed or reset in the system log module.
I was missing log entries with event_pid 0 from the recycler that got filtered away because of this constraint.
Updated by Benni Mack 5 months ago
- Status changed from New to Closed
We "removed this issue" by moving the Log module in one condensed singular module in v12, as this whole concept had flaws since its beginning of Extbase in BElog in v6.
Sorry, but this is the state we currently have until we revamp the logging functionality. If you feel this is the wrong decision, feel free to reach out to me.