Bug #55716

Why are we rebuilding Monolog?

Added by Sander Leeuwesteijn almost 8 years ago. Updated almost 6 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
-
Start date:
2014-02-06
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
6.2

Description

Was wondering, when looking through the logging manual, and seeing the feature requests, it just seems Monolog is being copied?

Why not implement Monolog like many others did? It has support for many features requested and connects with the most common systems.

https://github.com/Seldaek/monolog

Used by:
Symfony2 comes out of the box with Monolog.
Silex comes out of the box with Monolog.
Laravel 4 comes out of the box with Monolog.
PPI comes out of the box with Monolog.
CakePHP is usable with Monolog via the cakephp-monolog plugin.
Slim is usable with Monolog via the Slim-Monolog log writer.
XOOPS 2.6 comes out of the box with Monolog.
Aura.Web_Project comes out of the box with Monolog.

#1

Updated by Steffen Müller almost 8 years ago

This is a valid question. The only answers I have are: historical reasons and better integration into TYPO3 core, especially extensibility and configuration.

If you feel like replacing the current Logging API with Monolog, then go ahead and contact the core team/active contributor. I don't have time for this task. However I would support the idea.

This request is not valid for 6.2 since it already has reached feature freeze phase.

#2

Updated by Georg Ringer over 7 years ago

it is on my list for CMS 7.

#3

Updated by Steffen Müller almost 6 years ago

  • Status changed from New to Closed

This subproject is going to be closed. If you think this issue is still valid, please open a new issue in the core project.

Also available in: Atom PDF