https://github.com/in2code-de/logs

This is fork from the co-stack package https://gitlab.com/co-stack.com/co-stack.com/typo3-extensions/logs
https://github.com/in2code-de/logs

Last synced: 21 days ago
JSON representation

This is fork from the co-stack package https://gitlab.com/co-stack.com/co-stack.com/typo3-extensions/logs

• Host: GitHub
• URL: https://github.com/in2code-de/logs
• Owner: in2code-de
• License: gpl-2.0
• Created: 2026-01-22T11:36:25.000Z (5 months ago)
• Default Branch: master
• Last Pushed: 2026-01-22T11:40:57.000Z (5 months ago)
• Last Synced: 2026-04-23T04:28:55.091Z (about 2 months ago)
• Language: PHP
• Size: 622 KB
• Stars: 0
• Watchers: 0
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md
  • License: LICENSE.txt

Awesome Lists containing this project

README

          
> **📦 Migration Notice**  

> This package is a fork from https://gitlab.com/co-stack.com/co-stack.com/typo3-extensions/logs

> It is now maintained by [in2code GmbH](https://www.in2code.de).

>

> - **Old location:** `gitlab.com/co-stack.com/co-stack.com/typo3-extensions/logs`

> - **New location:** `github.com/in2code-de/logs`

> - **Composer name:** `co-stack/logs` (unchanged)

# CoStack.Logs

[![pipeline status](https://gitlab.com/co-stack.com/co-stack.com/typo3-extensions/logs/badges/master/pipeline.svg)](https://gitlab.com/co-stack.com/co-stack.com/typo3-extensions/logs/pipelines)

## 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

![Screenshot of the EXT:logs backend module](Documentation/_res/backend_module.png)

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](https://gitlab.com/co-stack.com/co-stack.com/typo3-extensions/logs/-/issues)

## Other stuff

Copyright & Author: Oliver Eglseder 

License: GPL-2.0+