Hi :)

I perform some ajax get and post calls. Get actions usually end with $this->renderPartial, while Post actions usually end with Yii::app()->end()

Anyway I do not see any sql query log in debug bar. Am I missing something? :) thx 👍

If you take a stock Yiic generated yii app, include your extension, and delete your 'db' in the main config.php you'll cause a null in your extension. It was messing up my theme in the rest environment

Hello, install this extension, but get error:

PHP Error
Trying to get property of non-object
yii-debug-toolbar/yii-debug-toolbar/views/yii_debug_toolbar.php(9)

Hi. I think this project is amazing. I did, however, encounter a bug that I spent a rather long time trying to troubleshoot:

With APC enabled, the yii-debug-toolbar gets its opcode cached which causes errors in any execution after the first. Since Yii has its unique autoloading mechanism we can't selectively set the debug toolbar's directory (via .htaccess):

php_flag apc.cache_by_default 0

If the entire Yii project has its opcode cache disabled the debug toolbar works as-expected. Either a fix or at least a mention in the documentation would be helpful so others don't spend time debugging the debugger. ;-)

Add posibility to disable widget for specific routes.

Improvement that resolves an issue with showing the database connection details when server info returns data in array

Using the current debug toolbar on a Yii 1.1.6 application crashes. The toolbar's code refers to CController::actionParams which was added on Yii 1.1.7.
It would be nice if the changelog mentionned this requirement. Adding a test in the code would also be nice.

it happens if there is more event handlers attached to onEndRequest. All of them can't save states to session after Yii-debug-bar. Bug is not permanent, but sometimes we had problems with flash messages, user states & other things that tried to save their data via states to session.

When Yii::app()->end() is sent the toolbar should be disabled as this is usually used when exiting with content and the debug toolbar still sends it's html out.

You can have html in parameters and in that case the log doesn't show the correct parameter value if contains another "=".

Just replace:

list($key,$value) = explode('=', $param);

with

list($key,$value) = explode('=', $param, 2);

Add possibility to exclude some routes (disable tool-bar rendering for specific controllers/actions )

I try to use the extension in an application with modules and it doesn't work. The PHP code produced by the extension is returned in the source.
I'm not sure it's because I use modules but with another app without modules, I worked perfectly.

if in condition use something with commas ( status IN( :status ) , status => '101,102',), then sql params binding don't work properly, because there are exploding by comma on line 364 in file \yii-debug-toolbar\panels\YiiDebugToolbarPanelSql.php
$params = explode(',', $params);
then on line 370 exploding by =
list($key,$value) = explode('=', $param, 2);
and offset 1 is undefined. Then we have html code of PHP Notice appended to sql panel of toolbar, it append stylesheets too, in result - site looks bad.

Такая вот беда =)

Apache/2.2.4 (Win32) mod_ssl/2.2.4 OpenSSL/0.9.8k PHP/5.3.3 Server at localhost Port 80
That's what my Denwer installation says (russian WAMP or smth like that)

Windows XP SP3.

I was observing 404 errors in console, so I changed the lines 169 - 175 of the style.css file from:

    background:url(../close.png) no-repeat center center;
    background-image: url(data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAACIAAAAiCAYAAAA6RwvCAAAAGXRFWHRTb2Z0d2FyZQBBZG9iZSBJbWFnZVJlYWR5ccllPAAAA7dJREFUeNqsWM1PE0EU3+7ShdJKoTRA8UYgIUKM3rmaEI0euXsw0YMHIZEbxBijEiIHLkb/A44SDYlXzkYPGBM+ri1NWz7aUmhp6+9tps10mLfdfrzkl2535r39zc77mvUdHh4abUoUCAD3xP/fQAFItWJkYmLC+e1p8eGPgQcC08ycf8BPgW2vhr0SeQa8AWIe5k4LvATiwCrwtZmS2WT8IfAL+OKRhCoxoftH2GqLyBLwHbhvdC53ha2lVrfmE/DKzbLP5yubplnt7e310f+rq6tqpVLxVatVy0VtHbgNLHohsupGIhQKFQG7v79f+8CLiwsjl8sVAZsxQbYTwFrDwpTwpaj4ptPu6+vLDw4OBkHA014QobOzs3yhUAgyUx4BP2rhq/rIe53GwMBAeXx83DMJEpobi8WCpMtMWeOc9TkwoyMRjUattrMedBkyM+KZN4isqDMDgUCuExIyGbKlGVpRiSzo8kQ4HA4ZXRLGVuzo6GhBJjKviw6dT5TLZSOTyRinp6cGQrV+n67hnEY6nTaur6+1PkM2NWTm5fCd0xDRhh89CKHpXCMijLGxMef6+PjYiRSSUqlUv6/arOlKMlcjQlV0qsGDTZPehpYIxurXRCSRSFByq5NQ56hvhWwj8cm2p7A9UdKYVBX8fn+F2+tIJGIgmzaQkUnYtm0MDw+zvsLYniQiEc2q/WxxwmqRHxrISA9xxiyLDzTGdsRsJwJoK3QPo3vctnhpAzLqTexhiVOg6JAdU5bLy0vHZ+Ro8mg7Q0QO1LvwenZZJycnN3yCIPsMRRYnjO0DU/SY+wprW7fiWmjKJMgnUIcafEaeoxZCJWJI9lH4UjV2u6pSPp/XJR9jaGiIKrERDAbrjllzYOQJZ4zm6ISxuSsntB3gqTyazWZtMowa0aBFb4HegC6aRkZG2C2hLSObmqEdOcVvUdJUZyBlZ7tVa1ASdEUvjW3ZUqvvO82e3kqlUuVOSZANvBFd0fugawM2VKclOT8/tzohQ7pkgzn/rHNdvLbLJkPxeDzHRRIXIaTDkCB57XacoJPZW8bZQpSskslk0Y0QjdEcmstsB8myegrsYbqmENfJU3dOpZyOEwjdCqLIWUyxWKygVzHFccJ2eVkbar/qdq5ZFC3/R5dUb6EBsqQmyEtLuawj0eykRwpPgL0uRO+esLXW7tmX9nEWeAEk2yCQFLqzzb4MeK3Zn4FRsapNEXqGy2eJTTF3VOh27bOE/Ia2pQ81YeCO+P+XknGrH2pq8l+AAQDv/n2Gmq99BgAAAABJRU5ErkJggg==);
}

#yii-debug-toolbar .yii-debug-toolbar-panel-title .yii-debug-toolbar-panel-close:hover {
    background-image:url(../close_hover.png);
    background-image: url(data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAACIAAAAiCAYAAAA6RwvCAAAAGXRFWHRTb2Z0d2FyZQBBZG9iZSBJbWFnZVJlYWR5ccllPAAABCVJREFUeNqsWG1IU1EYfjfd0i1bTc2WFTW3tG2aFWlEf4KkMIrCvhH6U9DnjxTyV0ZEXxIVGBH1JyKIPiBK8kf1syCKwu8M3VQsK7OV6ba2udZ7bmd6d+85827zhYftnnPe5z73nvc95z1X5XQ6IUHLQqQjiul1E8KHGIqHxGw2C7+pcd58E6KMooAzphPxnKJBKbFSIfsRpxAmBWMLKI4iviBOIm5O5qSepL8c8R5xQ6EIqZmobzPlSkhINeIpYhkkb0WUqzreqbmEOBaTOjQGf/0+CHz7Klxqc+aAehrGbkrM2b6IyEVUKRFyMpYI38dW8HS0gc/5kdmfnpcPepsD0vMLeRSEm6ivEzeqJOlLsuIJyzs40Au/Xr+CP64uRXORZraCoXQ1aHMX8YZsRDRG0lcqpA1hl3p4mt+C+/nThILDWLYR9EtXsrraEY6IEHGwHmCJGG16k7AIYsTX0/KO1WWn95QJqZWODHxyws8XjUmnjPtZg8DFsFqpkB2sdWL4zWuYKuNwmVwu1w6xkA2s7GAFpnaGAcxbd8H8snJQa7QTUZ+aCrlr10NexR5Iy8yW+REuwsmwDeL0XSOLjfYW5pNZtldC9orS/4FoK4LWa5cgHP4L9n1HILNoudCuM82F1qsXgcXJSOs1ESFkF7WKe8JBfxifQMVMY8/o+P+Z+TYoPFwNoYAfMh3FE2udz8d8CPJWCLdKM03MbcXpySJTY5EtmsNuFW+uex4/gJFe14SYxUuiRHi/fIaue7f5CzKb20KEGKWtYx4Pl2jM54WW+joY6euR9Xm/DkDT5bMQHB3h+7O5jepEMiAUDDBvRtpCfn9CWUWEuGUbkF7PdSDZQQLTaC+S9Rks+VB4qCoqmxRyu4mQbmlrisEY5hEtLN8ynh2RmBjt74sK4LyK3VwhHO5uNa0xoxYMEtVk02KZbk7uxB400C/ERPOVc1EBrMsxcTdCScYQ68L9ZiiyjryUprC+wM5c0PoaH4EmIwMCv4eh6+6t8VghAWzdtVdYzHoaHjKFEE6GvRTvvmSZvScd8f3hHfjT2z0lS3zaQgtkb6tkde3EN3I/kjX3ET9kwVdSOmV7jaF0Fav5BxEh3X3PyPaVBVaYta48aRGkJtHOt7C6zrPKgMvSoCU2vbhEIEpGBKcw6qQ1LLNmrWaVioRIk2kUtvK4SsWSVaCdl8cbcjxW8UxOZqcRJ2TThITZCO+HZvB2dsQsnnUFNtAtWRpLZ430FKjinH0VHSdCXg8EhwaFS03WbEjR6Sc7TkRCoErp2beKlvwX+EtkKqRkGATEYTXSY4SSkx5x2Eyr7WStnXLVJXr2JfPoQBxEDCYgYJD6Oib7MqC0DLiOyKFPVU9TD2J8lqinY3Oo75R9lhC/oQbRhxoSIDZ63UGK9Xg/1ETsnwADAJrrTk7nZiozAAAAAElFTkSuQmCC);
}

to

    background: url(close.png) no-repeat center center;
}

#yii-debug-toolbar .yii-debug-toolbar-panel-title .yii-debug-toolbar-panel-close:hover {
    background-image: url(close_hover.png);
}

I removed the encoded images as all the others are external and corrected the path.

This file has many problems.

1. It contains hard-coded paths that may not work, e.g. if there is no directory named yii-1.1.8.r3324 or if the application is not in the document root of the web server.
2. It won't work on some well-configured servers, because the PHP engine is disabled in the assets/ directory.
3. While the access to the toolbar is filtered, this file is in free access to everyone.
4. When the assets directory allows php files, this "ajax.php" file is dangerous with GET parameters like ?deleteasset=../. It will recursively delete files in the document root of the server.

I believe this makes "assets/ajax.php" a critical bug with a major security concern.

Make resource usage info as a panel widget

Hello, i use XAMPP under Windows 7 with yii 1.1.8.

This is my html page with all errors: http://www.sourcepod.com/eyocsa93-5616

CProfileLogRoute shows the benchmarks which you set using Yii::beginProfile() and Yii::endProfile(). Very useful for finding the choke points in the application.

If the constant YII_DEBUG is set to false, then the debug toolbar is initialized (its JS is loaded) but it is not shown (no HTML).
Tested on a fresh install of Yii 1.1.8 whith the latest code for yii-debug-toolbar.

I use standart Yii redirect in application:

Yii::app()->request->redirect('/newpage'/);

And get error:

Trying to get property of non-object
/extensions/yii-debug-toolbar/yii-debug-toolbar/views/yii_debug_toolbar.php(9)

Print screen of back trace http://img707.imageshack.us/img707/1404/screenshot20120413at144.png

If the site includes a <base> tag the toolbar links always redirect you to the base url when clicked.
For example let's say that you have a <base href="http://test.com/"> in your template and you are visiting an internal page like http://test.com/foo/bar.html, if you click on a link of the toolbar you will be redirected to http://test.com#yw1, this makes impossible to debug internal pages.
This happens because the href of the links is in format "#name", to fix it you can simply include the current page url before the fragment.

Otherwise on PHP 5.2.x it will cause error with E_STRICT. (Not with 5.3.x anymore, but many of us still have to use 5.2.x.)

I receive error in last version Controller SiteController can't find view "index" when tries to open index page of site with this extension installed. I'm using Twig as views renderer and extension of views files is ".twig".

Will be great if potentially inefficient queries will be highlighted. Check http://www.yiiframework.com/extension/dbprofiler/ for details.

If you run in console mode it kills the entire app for several reasons:

exception 'CException' with message 'CConsoleApplication and its behaviors do not have a method or closure named "getClientScript".'

{main}CException: CConsoleApplication and its behaviors do not have a method or closure named "getViewRenderer".

В php 5.4 выдаёт ошибку Illegal string offset 'class'
/extensions/yii-debug-toolbar/YiiDebugToolbar.php(186)
186 isset($config['class']) || $config['class'] = $id;

Functions json_encode() and memory_get_peak_usage() need php version >= 5.2.0

Clicking the icon in the top right doesn't do anything. Is there java script missing? this is what the div looks like.

using version malyshev-yii-debug-toolbar-95c08de on yii 1.1.8

Собственно в теме всё и написано. Как проверить:

1. Создаём пустой webapp в Yii 1.1.13
2. Подключаем в него yii-debug-toolbar согласно мануалу
3. В index.php комментируем строку:

defined('YII_DEBUG') or define('YII_DEBUG',false);

Панель пропадёт. Появится если, например, в контроллере сделать Yii::log('something');

Решение найдено, будет запушено ниже :) Это место аналогично как для dev так и для main ветки.

#62

Sometimes the last panels Sql and ViewsRendering are breaking the stylesheets and some layouts looks different. On the same page the debugbar javascript is not working anymore (panel doesn't open). At first i thought this happens because the views are outside of tag, but it seems that the reason is different.

Actually this behavior is happening because of PHP Warning:

preg_match_all() [function.preg-match-all]: Compilation failed: unrecognized character after (?< at offset 3

/protected/extensions/debug-toolbar/panels/YiiDebugToolbarPanelSql.php(365)
This is the actual line:

$matchResult = preg_match_all("/(?[a-z0-9._-:]+)=(?[\d.e-+]+|''|'.+?(?<!)')/ims", $params, $paramsMatched, PREG_SET_ORDER);
The layout problem is triggered because of inline styles in yii/framework/views/exception.php.

I'm using sqlite database, maybe this is raising the exception.

ReferenceError: yiiDebugToolbar is not defined
   yiiDebugToolbar.init();

It seems like the script is not registered at the time of the call. If you change POS_END to POS_HEADER it works:
YiiDebugToolbar, L#168-9:

$cs->registerScriptFile($this->assetsUrl . '/yii.debug.toolbar.js',
                CClientScript::POS_HEAD);

Hello,

first of all, very good work !!!

I needed to add CClientScript::POS_END to the registerScriptFile call on line 153 of "YiiDebugToolbar.php".

E.g.: $cs->registerScriptFile($this->assetsUrl . '/yii.debug.toolbar.js', CClientScript::POS_END);

The reason is that I have this setup:

'clientScript' => array(
'scriptMap' => array(
'jquery.js' => false,
'jquery-ui.js' => false,
'jquery.min.js' => false,
'jquery-ui.min.js' => false,
'jquery.metadata.js' => false,
),
'coreScriptPosition' => CClientScript::POS_END,
)

Add the ability to view cached queries

I extended CActiveRecord to setup a second database connection to a data warehouse. I named the database connection "dw". The toolbar doesn't render on pages that use the dw connection. The rest of the page seems to render fine.

The toolbar is in the HTML, and if I force it to be display "block" instead of "none" I can see it. Further, if I force the SQL block to display, I can see info for the "db" connection, but not the "dw" connection.

This is the error in the Apache log:

PHP Fatal error: Wrong parameters for Exception([string $exception [, long $code [, Exception $previous = NULL]]]) in /home/brad/projects/dca/protected/extensions/yii-debug-toolbar/YiiDebugToolbar.php on line 145

Server:

Ubuntu 10.04.2 LTS
PHP 5.3.2
Apache 2.2.14.

Possibility to explain SQL queries

После установки возникает ошибка:

TypeError: Object function (a,b){return new e.fn.init(a,b,h)} has no method 'cookie' [http://localhost/assets/1cbe31e6/yii.debug.toolbar.js:10]

В коде есть

<script type="text/javascript" src="/assets/51f54240/jquery.js"></script>
<script type="text/javascript" src="/assets/51f54240/jquery.cookie.js"></script>

I'm now to yii, and was very interested to your toolbar, but have the above error after activating.

The document (if I understand correctly) states to extract the tool into protected/extensions, i.e protected/extensions/yii-debug-toolbar/YiiDebugToolbarRoute.php exists as a path

I put the following in main.php:
'routes'=>array(
array(
'class'=>'ext.yii-debug-toolbar.YiiDebugToolbarRoute',

is "extensions" the right place to put it? Why is "ext." above?

thanks in advance

In the log panel, clicking on a line will show the details. But once I have clicked on the global "details" JS action in the table header, then clicking on a line has no effect.

Possibility to execute SQL query from SQL callstack and get results

Extension don't work with yiilite..

Description

Property "SiteController.actionParams" is not defined.

Source File

/var/www/yii/4/tomik/protected/extensions/yii-debug-toolbar/components/YiiDebugViewRenderer.php(77)

00065: 'render',
00066: 'renderPartial'
00067: )) )
00068: {
00069: break;
00070: }
00071: }
00072:
00073: array_push($this->_debugStackTrace, array(
00074: 'context'=>$context,
00075: 'contextProperties'=> get_object_vars($context),
00076: 'action'=> $context instanceof CController ? $context->action : null,
00077: 'actionParams'=> $context instanceof CController ? $context->actionParams : null,
00078: 'route'=> $context instanceof CController ? $context->route : null,
00079: 'sourceFile'=>$sourceFile,
00080: 'data'=>$data,
00081: 'backTrace'=>$backTraceItem,
00082: 'reflection' => new ReflectionObject($context)
00083: ));
00084: }
00085:
00086: }

The hotkeys enables keyboard navigation and shortcuts for enable/disable component and toggling the panels.

I would like to add a wild card for ipv6 addresses like this:

::ffff:192.168.0.*

This is needed because my nginx server returns ip addresses in that format.

The rule

// IPv6
            else if ($ip === $filter)
            {
                return true;
            }

does not allow wildcards

Would be great that you add composer support

Hello,

I downloaded the Debug Toolbar today (7/5/12) from github, and followed the installation instructions.

I'm getting the following javascript error:

Uncaught ReferenceError: yiiDebugToolbar is not defined

on this line:

(function($) {$(function(){yiiDebugToolbar.init()})}(jQuery));

I checked and the yii.debugtoolbar.js lib is installed under 'assets/84af4f51'. I also stepped through the php code and confirmed registerScriptFile() is being called for this file in YiiDebugToolbar.php.

Kind of stuck what's going on here. Is it a bug or is there some setup step I missed?

I'm running:

Yii 1.1.9

Thanks,

Peter

Needs to implement the possibility to make callback to debug toolbar bypass the application controller.