Logging Project

There was a new Logging Improvements project kickstarted at the Developer Days. You brought some up very good ideas!

Would you like to join that project? We will have another real kickstart meeting within the next few weeks (2-4 weeks, I assume). Would be really great!

@Steffen: What of the proposed changes should be implemented in the meantime until a full-blown logging system has evolved?

Here's my opinion on your suggestions:

1) Is "INSERT DELAYED INTO" generic SQL or proprietary implementation? It would need to be DBAL compatible to make it into TYPO3 core.
2) Does not work if script execution stops unexpectedly (e.g. on PHP fatal). Logging is expected to succeed, even if something crashes badly afterwards. This argument is also valid for 1)

Example:

<?php

class brokenExample {

        public function fail() {
                undefinedFunction();
        }   

        public function __destruct() {
                echo 'Class ' . __CLASS__ . ' was terminated successfully';
        }   
}

$test = new brokenExample();
$test->fail();

PHP Fatal error:  Call to undefined function undefinedFunction() in /tmp/test.php on line 6
PHP Stack trace:
PHP   1. {main}() /tmp/test.php:0
PHP   2. brokenExample->fail() /tmp/test.php:15

3) Introducing yet another configuration option was the common practice and this practice resulted in a confusing configuration overflow. We should catch all these nasty unflexible stuff and create one clean API to rule them all (TM).

Would you like to join the logging project team?

item 3) is possible with 6.0 though not 100% resolved.

With the new Logging API in 6.0 you can configure to write all logs to PHP error_log.

Still this Logging API needs to be integrated (replace all old log functions and calls). This is targeted for 6.1/6.2.