co-stack / logs
TYPO3 Logging API reading module and devlog extension in one
Installs: 118 030
Dependents: 0
Suggesters: 0
Security: 0
Stars: 3
Forks: 8
Type:typo3-cms-extension
pkg:composer/co-stack/logs
Requires
- php: ^8.1
- ext-json: *
- ext-pdo: *
- psr/log: ^2.0 || ^3.0
- typo3/cms-core: ^12.4 || ^13.0
Requires (Dev)
- co-stack/logs-dev: @dev
- typo3/cms-beuser: ^12.4 || ^13.4
- typo3/cms-install: ^12.4 || ^13.4
- typo3/cms-lowlevel: ^12.4 || ^13.4
- typo3/minimal: ^12.4 || ^13.4
- typo3/testing-framework: ^8.0 || ^9.0
This package is auto-updated.
Last update: 2025-10-21 11:07:29 UTC
README
Introduction
Finally, a backend module to read from the TYPO3 Logging API and a deprecation log reader.
Currently, only logs written by the DatabaseWriter and FileWriter are supported for reading. If you need a special log reader feel free to contact me or create a pull request with your proposal ;)
Basic Usage

The TYPO3 Logging API exists for a long time, but hasn't been a nice way to read those logs if the user has no direct access to the database or files.
Backend module created - problem solved!
The ConjunctionReader creates an instance of Reader for each Writer,
which reads from the specific location where the writer writes the log
entries. Therefore, it's possible to read and filter logs across all log
destinations (tables, files, etc.)
TYPO3 & PHP compatibility
| EXT:logs | TYPO3 | PHP |
|---|---|---|
| v5 | v12 & v13 | >= 8.1 |
| v4 | v11 | >= 7.4 |
| v3 | v9 & v10 | >= 7.2 |
TODO
- Register as devlog
- Identify and fix that one bug that sometimes won't delete a log entry
Known issues
- Deleting a log entry is not executed without an error message if the used webserver is nginx and the log message contains a semicolon
Found a bug? Feedback?
Please report any bug or negative side effects, as well as your feedback here: Issues
Other stuff
Copyright & Author: Oliver Eglseder oliver.eglseder@co-stack.com License: GPL-2.0+