• persist request information
• add job that deletes records older than x days

when trying to view design handles on pages served over https get a mixed content warning in chrome devtools console indicating the page was loaded over https, but requested an insecure XMLHttpRequest endpoint
https://mydomain.com/sheep_debug/design/viewHandle/default/store/1/area/frontend/ . This request has been blocked; the content must be served over HTTPS.

Currently we have a static array of PHP extensions that are required by Magento.

Verify what Magento version added this file app/code/core/Mage/Install/etc/install.xml

By using the front end translations the bar is translated on the website into a language I'm not too familiar with. It's not a big issue but imo it would be better to keep English translations at all times.

Would love to hear some input on this

On request profile page we show a clickable absolute url that needs some love;:

• include $_GET values to recreate the exact request url
• non GET requests should not be clickable

Makes more sense to remove jQuery and rely on out of the box prototype library.

When Template hints are enabled, they are displayed for debug blocks too.

It would be great to be able to define which viewers can use the debug bar, and have it disabled for all others and public use.

Things to consider:

• make a hole in FPC for toolbar so that request token will point to correct profile information, displayed information is related to current request and not to the request that filled in FPC
• check if profile information is recorded for all FPC request flows

Layout - Handles for this request -> specify the XMLs that contain the handles
Layout - Layout updates -> specify the XMLs in which the updates are defined

This way, one could easily locate anything, without touching grep or browsing for 15 minutes between files and folders.

$result = Mage::helper('debug')->getLastRows(Mage::getBaseDir('var') . DS . 'log' . DS . $file, 10);

The number of lines for exception.log is too low if your stack trace is more than 10 lines...
One way to deal with this is move 10 to the config (so it can be set to 20-30-whatever) or start from the last line and go back 3 lines from line starting with: #0

012-08-20[...] ERR (3): 
exception 'Exception' with message ....
Stack trace:
#0 /usr/local/zen

Use a tree to display rendered blocks.

For example:

I cant see in frontend.Magento 1.7.0.2.Use not default store,and theme.In backend all ok.
No included any js file

It would be interesting to show code that is responsible to generate a specific SQL.

Long time ago when I've checked this possibility, implementation involved overwriting some Zend classes. Lets see if anything changed since then. We need something simple and production safe (people should not be able to commit this change into production).

After updating to Magento 1.8.1, installing debug bar from magento connect and it doesn't work. Also doesn't work in fresh install.

Currently we don't plan to spent any time on this issue. Please let us know if you're on any of these Magento version and we'll take a look.

For now we know at least one error that needs to be addressed for Magento CE 1.7:
.PHP Fatal error: Call to undefined method Mock_Magento_Db_Adapter_Pdo_Mysql_3fc14b29::delete() in /home/travis/build/madalinoprea/magneto-debug/code/Debug/Model/Service.php on line 215

Just updated to the latest version. Toolbar works good to me except the template hints. Somehow they're not showing up. The do show up in the back-end when I enable them through the toolbar.

When I enable them throught the back-end it works fine.

Could you tell me what the reason is for the thrown error in https://github.com/madalinoprea/magneto-debug/blob/master/code/Debug/Model/Block.php#L56 ?

I ran into some issues getting that on certain pages, still debugging what caused in but it originates from the Innoext_Warehouse module. Still, not sure why it needs to be a fatal error instead of perhaps a warning in a log? #

Forgot to mention this before when i sent over an update for the Readme but whatever code is meant to be shown under Known Issues for enabling the SQL profiler is missing/incomplete.

Installed via modman

2016-03-05T00:12:07+00:00 CRIT (2): Not valid template file:adminhtml/default/default/template/sheep_debug/toolbar.phtml 2016-03-05T00:12:36+00:00 CRIT (2): Not valid template file:adminhtml/default/default/template/sheep_debug/toolbar.phtml 2016-03-05T00:12:45+00:00 CRIT (2): Not valid template file:adminhtml/default/default/template/sheep_debug/toolbar.phtml 2016-03-05T00:12:54+00:00 CRIT (2): Not valid template file:frontend/base/default/template/sheep_debug/toolbar.phtml 2016-03-05T00:13:09+00:00 CRIT (2): Not valid template file:frontend/base/default/template/sheep_debug/toolbar.phtml 2016-03-05T00:13:30+00:00 CRIT (2): Not valid template file:adminhtml/default/default/template/sheep_debug/toolbar.phtml

It seems that a bug was introduced when I've changed the display for blocks: template source is not retrieved via Ajax anymore.

app/design/adminhtml/base/default/template/debug/controller.phtml
Just done a modification to line 80 to check if $data is an array before looping it.

line 80:
line 98:

This error occurred when I installed fooman speedster mod.

A lighter version that would contain layout, template and block information (and anything else necessary for them) would be great for front-end developers that don't want to go through all the back-end stuff.

i get the following error in the console

Uncaught HierarchyRequestError: Failed to execute 'appendChild' on 'Node': This node type does not support this method. toolbar.js:14

it only happens on a page from a custom block what can i do to fix it

Add Show Source link for block class in Block Panel that will retrieve block's source code.

Investigate other common and easy possibilities to install Magento extensions on Windows.

Current idea:

• change Git repository to have a folder structure relative to Magento root folder (app, js, skin folders) and Windows users we'll have only to overwrite these 3 folders over their in instance

Any other suggestions? I didn't use Windows in a while.

Simplify presented information

Currently we start and end capturing assuming an HTTP request that is routed, dispatched.

Please check this error.

I have just install in CE 1.9.1 and this error show in console & debug toolbar not showing.

Hi,

I am using Magento 1.6.1 (+ installation with modman) and I'm encountering some issues :

• I have a "Debug Toolbar" item in the configuration backend page, but clicking on it gives me a 404 error.
• Nothing new on frontend

Additional infos :

• "Magneto_Debug" does show in Configuration/Advanced
• debug table is not present in the databse
• symlinks are activated

Many thanks !

• Highlight block without children that have rendering time above a threshold
• Highlight SQL that was executed above a threshold
• Highlight models that were loaded more than specified threshold
• Highlight collections that were loaded more than specified threshold
• Aggregate all these notices to be visible (e.g toolbar)

Hi,
I've just install it through magentoconnect on a 1.5.0.1: "magento_debug" shows up in the core_resource table, "debug" table has been create, "cache storage" has been flushed, but the left bar doesn't show up (as it should acording the wiki screenshots).
I haven't see anything in "system -> configuration" (and there is no etc/system.xml, so I assume it's normal) to enable it.
I also disabled all non-core module, to check for conflict, but still.

Am I missing something?
Let me know if you need more info about my install.

Your current versioned release by means of git tag (v-1.0.0) is invalid and causing composer to choke on teh non-semantic versioning/typo as the - hyphen causes (removal would suffice).

So please if you could, v1.0.0 or better yet (if still new) use a v0.1.0 to reflect earlier development stages (I haven't evaluated the software so I can't say, just noticed this when I wanted to try it out that I couldn't due to aforementioned reason)

p.s. I would create a new repo or rename this one, unless the project is intentionally named after the X-men/Marvel supervillain, in which case, forget I mentioned it ;)

Cheers and keep up the good work :)

Unless this was an intended naming convention, would be good to correct all "Magneto" occurrences. Also using Magento as a namespace might create confusion, maybe something like: Moprearo_MageDebug would be more appropriate.

-Toni

Extension Version

1.5.0

Magento Version

1.9.2.4

Exception

a:5:{i:0;s:48:"Block ANONYMOUS_41 is already marked as rendered";i:1;s:4648:"#0 /vagrant/vendor/madalinoprea/magneto-debug/code/Debug/Model/Observer.php(261): Sheep_Debug_Model_Block->startRendering(Object(Mage_Adminhtml_Block_Template))
#1 /vagrant/html/app/code/core/Mage/Core/Model/App.php(1358): Sheep_Debug_Model_Observer->onBlockToHtml(Object(Varien_Event_Observer))
#2 /vagrant/html/app/code/core/Mage/Core/Model/App.php(1337): Mage_Core_Model_App->_callObserverMethod(Object(Sheep_Debug_Model_Observer), 'onBlockToHtml', Object(Varien_Event_Observer))
#3 /vagrant/html/app/Mage.php(456): Mage_Core_Model_App->dispatchEvent('core_block_abst...', Array)
#4 /vagrant/html/app/code/core/Mage/Core/Block/Abstract.php(906): Mage::dispatchEvent('core_block_abst...', Array)
#5 /vagrant/html/app/code/core/Mage/Adminhtml/Block/System/Store/Tree.php(135): Mage_Core_Block_Abstract->toHtml()
#6 /vagrant/html/app/design/adminhtml/default/default/template/system/store/tree.phtml(81): Mage_Adminhtml_Block_System_Store_Tree->renderWebsite(Object(Aitoc_Aitquantitymanager_Model_Rewrite_FrontCoreWebsite))
#7 /vagrant/html/app/code/core/Mage/Core/Block/Template.php(241): include('/vagrant/html/a...')
#8 /vagrant/html/app/code/core/Mage/Core/Block/Template.php(272): Mage_Core_Block_Template->fetchView('adminhtml/defau...')
#9 /vagrant/html/app/code/core/Mage/Core/Block/Template.php(286): Mage_Core_Block_Template->renderView()
#10 /vagrant/html/app/code/core/Mage/Adminhtml/Block/Template.php(81): Mage_Core_Block_Template->_toHtml()
#11 /vagrant/html/app/code/core/Mage/Core/Block/Abstract.php(919): Mage_Adminhtml_Block_Template->_toHtml()
#12 /vagrant/html/app/code/core/Mage/Adminhtml/Block/System/Store/Store.php(78): Mage_Core_Block_Abstract->toHtml()
#13 /vagrant/html/app/design/adminhtml/default/default/template/system/store/container.phtml(36): Mage_Adminhtml_Block_System_Store_Store->getGridHtml()
#14 /vagrant/html/app/code/core/Mage/Core/Block/Template.php(241): include('/vagrant/html/a...')
#15 /vagrant/html/app/code/core/Mage/Core/Block/Template.php(272): Mage_Core_Block_Template->fetchView('adminhtml/defau...')
#16 /vagrant/html/app/code/core/Mage/Core/Block/Template.php(286): Mage_Core_Block_Template->renderView()
#17 /vagrant/html/app/code/core/Mage/Adminhtml/Block/Template.php(81): Mage_Core_Block_Template->_toHtml()
#18 /vagrant/html/app/code/core/Mage/Adminhtml/Block/Widget/Container.php(308): Mage_Adminhtml_Block_Template->_toHtml()
#19 /vagrant/html/app/code/core/Mage/Core/Block/Abstract.php(919): Mage_Adminhtml_Block_Widget_Container->_toHtml()
#20 /vagrant/html/app/code/core/Mage/Core/Block/Text/List.php(43): Mage_Core_Block_Abstract->toHtml()
#21 /vagrant/html/app/code/core/Mage/Core/Block/Abstract.php(919): Mage_Core_Block_Text_List->_toHtml()
#22 /vagrant/html/app/code/core/Mage/Core/Block/Abstract.php(637): Mage_Core_Block_Abstract->toHtml()
#23 /vagrant/html/app/code/core/Mage/Core/Block/Abstract.php(581): Mage_Core_Block_Abstract->_getChildHtml('content', true)
#24 /vagrant/html/app/design/adminhtml/default/default/template/page.phtml(74): Mage_Core_Block_Abstract->getChildHtml('content')
#25 /vagrant/html/app/code/core/Mage/Core/Block/Template.php(241): include('/vagrant/html/a...')
#26 /vagrant/html/app/code/core/Mage/Core/Block/Template.php(272): Mage_Core_Block_Template->fetchView('adminhtml/defau...')
#27 /vagrant/html/app/code/core/Mage/Core/Block/Template.php(286): Mage_Core_Block_Template->renderView()
#28 /vagrant/html/app/code/core/Mage/Adminhtml/Block/Template.php(81): Mage_Core_Block_Template->_toHtml()
#29 /vagrant/html/app/code/core/Mage/Core/Block/Abstract.php(919): Mage_Adminhtml_Block_Template->_toHtml()
#30 /vagrant/html/app/code/core/Mage/Core/Model/Layout.php(555): Mage_Core_Block_Abstract->toHtml()
#31 /vagrant/html/app/code/core/Mage/Core/Controller/Varien/Action.php(390): Mage_Core_Model_Layout->getOutput()
#32 /vagrant/html/app/code/core/Mage/Adminhtml/controllers/System/StoreController.php(60): Mage_Core_Controller_Varien_Action->renderLayout()
#33 /vagrant/html/app/code/core/Mage/Core/Controller/Varien/Action.php(418): Mage_Adminhtml_System_StoreController->indexAction()
#34 /vagrant/html/app/code/core/Mage/Core/Controller/Varien/Router/Standard.php(254): Mage_Core_Controller_Varien_Action->dispatch('index')
#35 /vagrant/html/app/code/core/Mage/Core/Controller/Varien/Front.php(172): Mage_Core_Controller_Varien_Router_Standard->match(Object(Mage_Core_Controller_Request_Http))
#36 /vagrant/html/app/code/core/Mage/Core/Model/App.php(365): Mage_Core_Controller_Varien_Front->dispatch()
#37 /vagrant/html/app/Mage.php(692): Mage_Core_Model_App->run(Array)
#38 /vagrant/html/index.php(83): Mage::run('', 'store')
#39 {main}";s:3:"url";s:78:"/index.php/backoffice/system_store/index/key/274106fb194fa00797bd5e72d02c5439/";s:11:"script_name";s:10:"/index.php";s:4:"skin";s:5:"admin";}

Uncaught Error: Call to undefined function getallheaders() in /vendor/madalinoprea/magneto-debug/code/Debug/Model/Controller.php:47

The function getallheaders does not exist when using Nginx.
This polyfill fixes it:
https://github.com/ralouphie/getallheaders

I've got this after installing toolbar in project which doesn't have system.log:

Warning: fopen([...]var/log/system.log): failed to open stream: No such file or directory

Error is gone after creating empty file.

after i installed it. I logged in backend and got the error:

Mage registry key "_singleton/debug/observer" already exists

How can i fix it?

After initial installation:
modman clone https://github.com/madalinoprea/magneto-debug
and
n98-magerun.phar cache:flush

SQLSTATE[42S02]: Base table or view not found: 1146 Table 'magento1.sheep_debug_request_info' doesn't exist, query was: DESCRIBE `sheep_debug_request_info`

#0  lib/Varien/Db/Statement/Pdo/Mysql.php(110): Zend_Db_Statement_Pdo->_execute(Array)
#1  app/code/core/Zend/Db/Statement.php(291): Varien_Db_Statement_Pdo_Mysql->_execute(Array)
#2  lib/Zend/Db/Adapter/Abstract.php(480): Zend_Db_Statement->execute(Array)
#3  lib/Zend/Db/Adapter/Pdo/Abstract.php(238): Zend_Db_Adapter_Abstract->query('DESCRIBE `sheep...', Array)
#4  lib/Varien/Db/Adapter/Pdo/Mysql.php(504): Zend_Db_Adapter_Pdo_Abstract->query('DESCRIBE `sheep...', Array)
#5  lib/Zend/Db/Adapter/Pdo/Mysql.php(171): Varien_Db_Adapter_Pdo_Mysql->query('DESCRIBE `sheep...')
#6  lib/Varien/Db/Adapter/Pdo/Mysql.php(1694): Zend_Db_Adapter_Pdo_Mysql->describeTable('sheep_debug_req...', NULL)
#7  app/code/core/Mage/Core/Model/Resource/Abstract.php(212): Varien_Db_Adapter_Pdo_Mysql->describeTable('sheep_debug_req...')
#8  app/code/core/Mage/Core/Model/Resource/Db/Abstract.php(586): Mage_Core_Model_Resource_Abstract->_prepareDataForTable(Object(Sheep_Debug_Model_RequestInfo), 'sheep_debug_req...')
#9  app/code/core/Mage/Core/Model/Resource/Db/Abstract.php(449): Mage_Core_Model_Resource_Db_Abstract->_prepareDataForSave(Object(Sheep_Debug_Model_RequestInfo))
#10 app/code/core/Mage/Core/Model/Abstract.php(318): Mage_Core_Model_Resource_Db_Abstract->save(Object(Sheep_Debug_Model_RequestInfo))
#11 .modman/magneto-debug/code/Debug/Model/Observer.php(163): Mage_Core_Model_Abstract->save()
#12 .modman/magneto-debug/code/Debug/Model/Observer.php(226): Sheep_Debug_Model_Observer->saveProfiling()
#13 app/code/core/Mage/Core/Model/App.php(1357): Sheep_Debug_Model_Observer->onLayoutGenerate(Object(Varien_Event_Observer))
#14 app/code/core/Mage/Core/Model/App.php(1336): Mage_Core_Model_App->_callObserverMethod(Object(Sheep_Debug_Model_Observer), 'onLayoutGenerat...', Object(Varien_Event_Observer))
#15 app/Mage.php(448): Mage_Core_Model_App->dispatchEvent('controller_acti...', Array)
#16 app/code/core/Mage/Core/Controller/Varien/Action.php(350): Mage::dispatchEvent('controller_acti...', Array)
#17 app/code/core/Mage/Core/Controller/Varien/Action.php(269): Mage_Core_Controller_Varien_Action->generateLayoutBlocks()
#18 app/code/core/Mage/Adminhtml/Controller/Action.php(275): Mage_Core_Controller_Varien_Action->loadLayout(NULL, true, true)
#19 app/code/core/Mage/Adminhtml/controllers/IndexController.php(81): Mage_Adminhtml_Controller_Action->loadLayout()
#20 app/code/core/Mage/Core/Controller/Varien/Action.php(418): Mage_Adminhtml_IndexController->loginAction()
#21 app/code/core/Mage/Core/Controller/Varien/Router/Standard.php(254): Mage_Core_Controller_Varien_Action->dispatch('login')
#22 app/code/core/Mage/Core/Controller/Varien/Front.php(172): Mage_Core_Controller_Varien_Router_Standard->match(Object(Mage_Core_Controller_Request_Http))
#23 app/code/core/Mage/Core/Model/App.php(365): Mage_Core_Controller_Varien_Front->dispatch()
#24 app/Mage.php(683): Mage_Core_Model_App->run(Array)
#25 index.php(83): Mage::run('', 'store')
#26 {main}

There are several common extensions that extend same models we do. We need to find a better way to reduce/remove rewrite conflicts conflicts.