Magento – Mage::log clear log files

debugdebuggingfilelogmagento-1.9

I want to programmatically clear manual log-files in order to always only see the new Logging Code for the last iteration.

Is it possible (e.g. via a parameter) to only log the last iteration with the call

Mage::log("My Test Log", null, "test.log")

Or do I always have to manually delete the content of my manual log files?

Do you have a good idea, how can I achieve this with minimum effort?

Best Answer

I think You can use unlink command of php it will delete your old file and

Mage::log will always create a new file

here is php Manual url

http://php.net/manual/en/function.unlink.php

Related Solutions

Magento – Mage::log writes to the screen

I created a really short and sweet reproducible test case for this:

<?php

error_reporting(-1);
ini_set('display_errors', true);
ini_set('memory_limit', '1M');

$chunk = base64_encode(openssl_random_pseudo_bytes(1024));

while (true) {
    $a[] = print_r($chunk, true);
}

The reason you are seeing the information put out is due to print_r using output buffering internally to capture it's information. Take a look at the definition of the print_r function from the PHP source:

/* {{{ proto mixed print_r(mixed var [, bool return])
   Prints out or returns information about the specified variable */
PHP_FUNCTION(print_r)
{
    zval *var;
    zend_bool do_return = 0;

    if (zend_parse_parameters(ZEND_NUM_ARGS() TSRMLS_CC, "z|b", &var, &do_return) == FAILURE) {
        RETURN_FALSE;
    }

    if (do_return) {
        php_start_ob_buffer (NULL, 0, 1 TSRMLS_CC);
    }

    zend_print_zval_r(var, 0 TSRMLS_CC);

    if (do_return) {
        php_ob_get_buffer (return_value TSRMLS_CC);
        php_end_ob_buffer (0, 0 TSRMLS_CC);
    } else {
        RETURN_TRUE;
    }
}

Because PHP is running out of memory and dying, the output buffer is being flushed before print_r clears it out via it's call to php_ob_get_buffer

I'm not sure there is going to be anyway around this. Just make sure you disable that logging in production, or run mod_security to prevent this type of output from going to the page.

Debug – Difference Between var_dump() and Mage::log()

var_dump() shows the information in your browser. Mage::log() echos information to your system.log file (var/log/system.log).

To use Mage::log(), you need to enable logging in the backend: System > Configuration > Developer -> Log Settings -> Enabled > Set to "Yes".

Furthermore you can force logging using the forth parameter of Mage::log() set to true: Mage::log($foo,null,'system.log',true);

According to the function in Mage.php: public static function log($message, $level = null, $file = '', $forceLog = false)

Mage::log() will be especially useful if you do not see the output in your browser (debugging SOAP API requests, AJAX requests,...).

Best Answer

Related Solutions

Magento – Mage::log writes to the screen

Debug – Difference Between var_dump() and Mage::log()

Related Topic