README

Debug panel for Yii 1.1 (Ported from Yii 2). Updated to fix compatability with PHP8.1+ Forked from https://github.com/koftikes/yii-debug-toolbar

Installation

This extension is available at packagist.org and can be installed via composer by following command:

composer require --dev biskyt/yii-debug-toolbar.

To enable toolbar in your application add following lines to config:

return [
    'preload' => ['debug'],
    'components' => [
        'debug' => [
            'class' => 'Yii2Debug',
        ],
        'db' => [
            'enableProfiling' => true,
            'enableParamLogging' => true,
        ],
    ],
];

Configuration

You can customize debug panel behavior with this options:

• enabled - enable/disable debug panel.
• allowedIPs - list of IPs that are allowed to access debug toolbar. Default ['127.0.0.1', '::1'].
• accessExpression - additional php expression for access evaluation.
• logPath - directory storing the debugger data files. This can be specified using a path alias. Default /runtime/debug.
• historySize - maximum number of debug data files to keep. If there are more files generated, the oldest ones will be removed.
• highlightCode - highlight code. Highlight SQL queries and PHP variables. This parameter can be set for each panel individually.
• moduleId - module ID for viewing stored debug logs. Default debug.
• showConfig - show brief application configuration page. Default false.
• hiddenConfigOptions - list of un secure component options to hide (like login, passwords, secret keys). Default is to hide username and password of db component.
• internalUrls - use nice routes rules in debug module.
• panels - list of debug panels.

Each attached panel can be configured individually, for example:

'debug' => [
    'class' => 'Yii2Debug',
    'panels' => [
        'db' => [
            // Disable code highlighting.
            'highlightCode' => false,
            // Disable substitution of placeholders with values in SQL queries.
            'insertParamValues' => false,
        ],
    ],
]

Each panel have callback option filterData. You can define custom function for filtering input data before writing it in to debug log. It's useful when you need to hide something secret or just delete data from logs. Be careful with data structure manipulation. It can lead to log parsing errors.

Example:

'debug' => [
    'class' => 'Yii2Debug',
    'panels' => [
        'db' => [
            'filterData' => function($data) {
                // Your code here
                return $data;
            }
        ],
    ],
]

Creating own panels

To create own debug panel you can extend class Yii2DebugPanel, for example:

class MyTestPanel extends Yii2DebugPanel
{
    /**
     * The name of panel printed in debugger
     */
    public function getName()
    {
        return 'Name';
    }

    /**
     * Return summary html with results of execution in current request.
     * Data is available through $this->data
     */
    public function getSummary()
    {
        return '';
    }

    /**
     * Return detailed html report with results of execution in current request.
     * Data is available through $this->data
     */
    public function getDetail()
    {
        return '';
    }

    /**
     * Return data required for storing in logs.
     */
    public function save()
    {
        return array();
    }
}

And attach this panel in config:

'panels' => [
    'test' => [
        'class' => 'path.to.panel.MyTestPanel',
        // ...
    ],
],

Disable individual panels

To disable an individual panel, either a core or custom panel, set the enabled property in the panel config to false.

Example: Disable core profiling panel

'panels' => [
    'profiling' => [
        'enabled' => false,
        // ...
    ],
],

Variables dumping

With static method Yii2Debug::dump() you can dump any data and examine it later in debug log.