yii-debug-toolbar

The function itself already has condition to check jquery including status.

Yii::app()->getClientScript()->registerCoreScript('jquery');

Hello,

Firstly id like to say this is a very nice tool, and I love having it in such a handy place while developing. Elegant display and very useful information presented.

Im wondering why class YiiDebugToolbar has to load jquery every time the widget is requested [see YiiDebugToolbar::registerClientScripts()]. Is it possible to have it check to see if jQuery is already loaded, and only call

Yii::app()->getClientScript()->registerCoreScript('jquery');

if jQuery is not found? The problem I am experiencing is with some partially rendered views (as popups) within some of the views in my app. As it subsequently loads jQuery for the view-within-a-view, my jQuery library stops functioning, and the resultant popup freezes. When I comment out this line within the YiiDebugToolbar class, everything works fine.

Is it possible to get this updated with the extension? If not I can extend this out myself.

Thanks!

I have my config set like this:

array(
    'class'=>'ext.yii-debug-toolbar.YiiDebugToolbarRoute',
    'additionalPanels'=>array('ext.sample.YiiDebugToolbarPanelSample'),
),

YiiDebugToolbarRoute tries to call YiiDebugToolbar->appendPanel() ... but that doesn't exist. Are additionalPanels not supported? Or were appendPanel and prependPanel accidentally left out?

Thanks!

Elapsed time - This is the time elapsed from the time of receipt of the request to the server, see $_SERVER['REQUEST_TIME'] Page Load Time - This is the time elapsed from the time of start a application

Here are some stats of "hello world" application from my Mac. No database connection.

• Page Load Time: 0.07 s
• Elapsed Time: 0.9 s

Why elapsed time is much higher than page load time? How are they defined? 0.9 sec is quite slow for a simple page like this. :)

What exactly you mean?

I am not getting any instruction to use this extension. Please help. thanks

The only feature i'm missing right now is ability to set levels in config.

OceanWind, that's correct, so if this is production you probably don't want that (at least not long term). Are you sure that the ip address that your production system sees when you go to it is the one you entered in ipTables? This sounds somewhat similar to my problem, where my external ip was different than my internal ip, and thus the plugin didn't recognize me when I cam in from my home system.

One very hacky way (which I used) to determine that was to add a Yii::log($ip, 'error'); to the allowIp function in YiiDebugToolbarRoute.php. Check the application log for the reported ip address and add it to the extensions ipFilters list. That showed me what my request came in on, and then I added that to the ipFilters variable. Maybe this helps...

Thanks, Sven.

I was hoping to get a display on my production system, where the problem is occurring.

Won't setting 'ipFilters'=array('*') make the debugger display for everyone?

Oceanwind, you may want to try setting ipFilters to:

'ipFilters'=>array('*')

At least temporarily. If that gets the plugin displayed, you can then try to figure out what ip address is seen by apache.

Is there anything else I need to do to get this to display? I've entered my IP into ipFilters, loaded the plugin into extensions, and set the DB connects to enable profiling and paramLogging. But nothing happens...

:-/

This debugger is way better than others I have seen in yii extension lib...

When I was trying to get WSDL from site with enabled yii-debug-toolbar, I was getting WSDL with HTML from yii-debug-toolbar.

Here is temporary solution YiiDebugToolbarRoute.php

protected function onBeginRequest(CEvent $event)
    {
        $route = Yii::app()->getUrlManager()->parseUrl(Yii::app()->request);
        $this->enabled = (preg_match('#^(?:services|test)/#',$route) == 0);
 
        $this->getToolbarWidget()
             ->init();
    }

Hello comment #6372 :)

You're right. I was trying to be politically correct and I was using Yii::app->end(). Ignoring it and just calling Php's exit() function does the trick.

To recap:

In order to correctly download a file (from inside a controller):

Yii::app()->request->sendFile("taxo.json",json_encode($dump, true),'text/plain', false);
exit();

Just don't use the $terminate option of the sendFile and rudely call exit() yourself after sending the file...

Hey, I'm comment #6372:D

I found out that you obviously can disable the toolbar with the exit function. Yii::app()->end() does not work because it calls some "end-methods", so the toolbar.

Of course it only helps in specific situations, for example sending a file to the browser.

Hello,

Really nice extension but I have a major problem (that has ALREADY been pointed to (in one way or another) THREE (3) different times (in comments #6372, #6248 and #5763) but still there is no resolution.

When I download a file with Yii::app()->request->sendFile(...)

The web debug html code is also injected in the downloaded file. Pretty much the same side effect as the Ajax request and webservices calls already mentioned.

How can I temporarily turn it off for specific controller actions...?

Thank you...

Hey blacksheep,

I was also unable to see the toolbar. For me it turned out to be an issue with the extensions ipFilter. If you don't specify one, the extension will use:

'ipFilters'=>array('127.0.0.1','::1')

that's quite nice/reasonable, but in my case I had routing set up a little more complicated (going out to the ether and then coming back through my router). So I temporarily set it to:

'ipFilters'=>array('*')

which is not secure, but allowed me to see the toolbar. After taht I just had to identify what ip was actually being used. One very hacky way (which I used) was to add a Yii::log($ip, 'error'); to the allowIp function in YiiDebugToolbarRoute.php. Check the application log for the reported ip address and add it to the extensions ipFilters list. Hope this helps.

how can i see the toolbar?? i follow the instruction, but how can i read into the toolbar? thanks!

Is there a possibility to disable the toolbar for a specific action?