Last 7 days

• Dec 15, 2009

  issue 15 (ZFDebug, JSON and jQuery) commented on by beausy   -   This plugin actually breaks pages that use jQuery. It doesn't matter if you omit using ZendX_JQuery, set the ZendX_JQuery render state to prevent loading the jQuery lib twice, set noConflict, or not use ZendX_JQuery at all. For example, load up a jQuery dialog with a click event. Then try to click the object. It either will, or will not open. If it does open, refresh the page and try again. The behavior is erratic. Now unload ZFDebug from the page and behavior will be normal. Example: <a href="#" id="test">Test</a> <div id="dialog"></div> <script type="text/javascript"> //<![CDATA[ $(document).ready(function() { $("#dialog").dialog({"title":"Confirm","modal":true,"resizable":true,"closeOnEscape": true,"autoOpen":false,"buttons":{"No":function() { $(this).dialog('close'); return false; }, "Yes":function() { $(this).dialog('close'); return false; } } }); $('#test').click(function(e) { e.preventDefault(); $('#dialog').html('Test'); $('#dialog').dialog('open'); return false; }); }); //]]> </script> A quick fix is to explicitly use jQuery() instead of ZendX_JQuery_View_Helper_JQuery::getJQueryHandler() or any other specified jQuery handler. ZFDebug needs to honor ZendX_JQuery's jQueryHandler, or allow setting of ZFDebugs jQueryHandler to make it compatible.

  This plugin actually breaks pages that use jQuery. It doesn't matter if you omit using ZendX_JQuery, set the ZendX_JQuery render state to prevent loading the jQuery lib twice, set noConflict, or not use ZendX_JQuery at all. For example, load up a jQuery dialog with a click event. Then try to click the object. It either will, or will not open. If it does open, refresh the page and try again. The behavior is erratic. Now unload ZFDebug from the page and behavior will be normal. Example: <a href="#" id="test">Test</a> <div id="dialog"></div> <script type="text/javascript"> //<![CDATA[ $(document).ready(function() { $("#dialog").dialog({"title":"Confirm","modal":true,"resizable":true,"closeOnEscape": true,"autoOpen":false,"buttons":{"No":function() { $(this).dialog('close'); return false; }, "Yes":function() { $(this).dialog('close'); return false; } } }); $('#test').click(function(e) { e.preventDefault(); $('#dialog').html('Test'); $('#dialog').dialog('open'); return false; }); }); //]]> </script> A quick fix is to explicitly use jQuery() instead of ZendX_JQuery_View_Helper_JQuery::getJQueryHandler() or any other specified jQuery handler. ZFDebug needs to honor ZendX_JQuery's jQueryHandler, or allow setting of ZFDebugs jQueryHandler to make it compatible.
• Dec 15, 2009

  issue 7 (jQuery option to use ZendX_JQuery) commented on by beausy   -   This plugin actually breaks pages that use jQuery. It doesn't matter if you omit using ZendX_JQuery, set the ZendX_JQuery render state to prevent loading the jQuery lib twice, set noConflict, or not use ZendX_JQuery at all. For example, load up a jQuery dialog with a click event. Then try to click the object. It either will, or will not open. If it does open, refresh the page and try again. The behavior is erratic. Now unload ZFDebug from the page and behavior will be normal. Example: <a href="#" id="test">Test</a> <div id="dialog"></div> <script type="text/javascript"> //<![CDATA[ $(document).ready(function() { $("#dialog").dialog({"title":"Confirm","modal":true,"resizable":true,"closeOnEscape": true,"autoOpen":false,"buttons":{"No":function() { $(this).dialog('close'); return false; }, "Yes":function() { $(this).dialog('close'); return false; } } }); $('#test').click(function(e) { e.preventDefault(); $('#dialog').html('Test'); $('#dialog').dialog('open'); return false; }); }); //]]> </script> A quick fix is to explicitly use jQuery() instead of ZendX_JQuery_View_Helper_JQuery::getJQueryHandler() or any other specified jQuery handler. ZFDebug needs to honor ZendX_JQuery's jQueryHandler, or allow setting of ZFDebugs jQueryHandler to make it compatible.

  This plugin actually breaks pages that use jQuery. It doesn't matter if you omit using ZendX_JQuery, set the ZendX_JQuery render state to prevent loading the jQuery lib twice, set noConflict, or not use ZendX_JQuery at all. For example, load up a jQuery dialog with a click event. Then try to click the object. It either will, or will not open. If it does open, refresh the page and try again. The behavior is erratic. Now unload ZFDebug from the page and behavior will be normal. Example: <a href="#" id="test">Test</a> <div id="dialog"></div> <script type="text/javascript"> //<![CDATA[ $(document).ready(function() { $("#dialog").dialog({"title":"Confirm","modal":true,"resizable":true,"closeOnEscape": true,"autoOpen":false,"buttons":{"No":function() { $(this).dialog('close'); return false; }, "Yes":function() { $(this).dialog('close'); return false; } } }); $('#test').click(function(e) { e.preventDefault(); $('#dialog').html('Test'); $('#dialog').dialog('open'); return false; }); }); //]]> </script> A quick fix is to explicitly use jQuery() instead of ZendX_JQuery_View_Helper_JQuery::getJQueryHandler() or any other specified jQuery handler. ZFDebug needs to honor ZendX_JQuery's jQueryHandler, or allow setting of ZFDebugs jQueryHandler to make it compatible.
• Dec 15, 2009

  issue 39 (ArrayObject::ksort not available in PHP 5.1.6 (Red hat versi...) reported by ecolinet   -   Using Redhat enterprise linux 4 the PHP version is locked to PHP 5.1.6. It seems that ArrayObject::ksort is not implemented in that version [1] but the Registry Plugin use it. The bug is in ZFDebug_Controller_Plugin_Debug_Plugin_Registry::getPanel, adding a test like method_exists($this->_registry, 'ksort') solves the problem. [1] http://php.net/manual/en/arrayobject.ksort.php says that the minimal version is 5.1.0 but it doesn't seems to be true

  Using Redhat enterprise linux 4 the PHP version is locked to PHP 5.1.6. It seems that ArrayObject::ksort is not implemented in that version [1] but the Registry Plugin use it. The bug is in ZFDebug_Controller_Plugin_Debug_Plugin_Registry::getPanel, adding a test like method_exists($this->_registry, 'ksort') solves the problem. [1] http://php.net/manual/en/arrayobject.ksort.php says that the minimal version is 5.1.0 but it doesn't seems to be true
• Dec 15, 2009

  issue 38 (Memory plugin use memory_get_peak_usage instead of memory_ge...) reported by ecolinet   -   According to php.net manual memory_get_peak_[1] returns the "peak" usage and memory_get_usage [2] returns the current memory allocation. So for mark, preDispatch and postDispatch memory_get_usage seems better. [1] http://us.php.net/manual/en/function.memory-get-peak-usage.php [2] http://us.php.net/manual/en/function.memory-get-usage.php

  According to php.net manual memory_get_peak_[1] returns the "peak" usage and memory_get_usage [2] returns the current memory allocation. So for mark, preDispatch and postDispatch memory_get_usage seems better. [1] http://us.php.net/manual/en/function.memory-get-peak-usage.php [2] http://us.php.net/manual/en/function.memory-get-usage.php

Last 30 days

• Nov 25, 2009

  Installation (Instructions for installing ZFDebug) Wiki page commented on by maximvassilyev   -   Thanks that's very useful

  Thanks that's very useful
• Nov 21, 2009

  Documentation_Plugin_Memory Wiki page commented on by broich   -   Hey! There is an error in your usage code example, the second line says "$zfdebug" but it should be $zfDebug. {{{ $zfDebug = Zend_Controller_Front::getInstance()->getPlugin('ZFDebug_Controller_Plugin_Debug'); $zfMemory = $zfDebug->getPlugin('Memory'); $zfMemory->mark('Memory usage'); ... # some memory expensive operations ... $zfMemory->mark('Memory usage'); }}}

  Hey! There is an error in your usage code example, the second line says "$zfdebug" but it should be $zfDebug. {{{ $zfDebug = Zend_Controller_Front::getInstance()->getPlugin('ZFDebug_Controller_Plugin_Debug'); $zfMemory = $zfDebug->getPlugin('Memory'); $zfMemory->mark('Memory usage'); ... # some memory expensive operations ... $zfMemory->mark('Memory usage'); }}}

Earlier this year

• Nov 15, 2009

  issue 37 (Position of <script> in page causes page reload on Firefox) reported by silvan.muhlemann   -   On my installation (Firefox 3.5.5 Win, safe mode) the page I loading gets loaded twice when the debug bar is enabled. 127.0.0.1 - - [15/Nov/2009:17:50:20 +0100] "GET /f//family/overview HTTP/1.1" 200 63717 127.0.0.1 - - [15/Nov/2009:17:50:30 +0100] "GET /f//family/overview HTTP/1.1" 200 63717 I can avoid this weird behavior by placing the <script> generated by the Debug bar right before the </head> tag. The patch is attached.

  On my installation (Firefox 3.5.5 Win, safe mode) the page I loading gets loaded twice when the debug bar is enabled. 127.0.0.1 - - [15/Nov/2009:17:50:20 +0100] "GET /f//family/overview HTTP/1.1" 200 63717 127.0.0.1 - - [15/Nov/2009:17:50:30 +0100] "GET /f//family/overview HTTP/1.1" 200 63717 I can avoid this weird behavior by placing the <script> generated by the Debug bar right before the </head> tag. The patch is attached.
• Nov 13, 2009

  issue 35 (v1.6: Implement animation without jQuery) Status changed by gugakfugl   -   No more animation. The panels appear instantly and there should be no more problems with mootools or prototype + faster loading

  Status: Fixed

  No more animation. The panels appear instantly and there should be no more problems with mootools or prototype + faster loading

  Status: Fixed
• Nov 12, 2009

  r136 (- Fixed duplicate file and line output to error_log by Excep...) committed by gugakfugl   -   - Fixed duplicate file and line output to error_log by Exception plugin

  - Fixed duplicate file and line output to error_log by Exception plugin
• Nov 12, 2009

  r135 (- Cleanup) committed by gugakfugl   -   - Cleanup

  - Cleanup
• Nov 12, 2009

  r134 ([CHANGED] No longer dependant on jQuery framework) committed by gugakfugl   -   [CHANGED] No longer dependant on jQuery framework

  [CHANGED] No longer dependant on jQuery framework
• Nov 11, 2009

  r133 ([FIXED] Sugested fix for issue #36 for release 1.6) committed by gugakfugl   -   [FIXED] Sugested fix for issue #36 for release 1.6

  [FIXED] Sugested fix for issue #36 for release 1.6
• Nov 11, 2009

  issue 36 (error messages not shown if application terminated without t...) Status changed by gugakfugl   -   That's indeed true as the dispatchLoopShutdown() method is never called. Thanks for the suggested patch, I'll look into it.

  Status: Accepted

  That's indeed true as the dispatchLoopShutdown() method is never called. Thanks for the suggested patch, I'll look into it.

  Status: Accepted
• Nov 06, 2009

  issue 30 (ZFDebug conflicts with jQuery UI Dialog) commented on by grangerp   -   I had the exact same problem and I was able to fix it. I just commented the line jQuery.noConflict() on line 424 of the file zfdebug/ controller/plugin/debug/plugin/debug.php. var ZFDebugLoad = window.onload; window.onload = function(){ if (ZFDebugLoad) { ZFDebugLoad(); } //jQuery.noConflict(); ZFDebugCollapsed(); }; I did not investigate yet why it cause the problem.

  I had the exact same problem and I was able to fix it. I just commented the line jQuery.noConflict() on line 424 of the file zfdebug/ controller/plugin/debug/plugin/debug.php. var ZFDebugLoad = window.onload; window.onload = function(){ if (ZFDebugLoad) { ZFDebugLoad(); } //jQuery.noConflict(); ZFDebugCollapsed(); }; I did not investigate yet why it cause the problem.
• Nov 05, 2009

  Installation (Instructions for installing ZFDebug) Wiki page commented on by val.root   -   $options = array( 'plugins' => array('Variables', 'File' => array('base_path' => '/path/to/project'), what should I enter to /path/to/project? application folder?

  $options = array( 'plugins' => array('Variables', 'File' => array('base_path' => '/path/to/project'), what should I enter to /path/to/project? application folder?
• Nov 05, 2009

  r132 (- Appearance update) committed by gugakfugl   -   - Appearance update

  - Appearance update
• Nov 02, 2009

  r131 (- Updated layout) committed by gugakfugl   -   - Updated layout

  - Updated layout
• Oct 22, 2009

  issue 36 (error messages not shown if application terminated without t...) reported by martin.minka   -   What steps will reproduce the problem? 1. enable zfdebug in application 2. make sure display_error is set to On 3. raise some Warnings in your controller code 4. call die(); in your controller What is the expected output? What do you see instead? The zfdebug will not be rendered but the errors/warnings should appear. What version of the product are you using? On what operating system? commit 109 Please provide any additional information below. I suggest to add to ZFDebug_Controller_Plugin_Debug_Plugin_Exception: ... /** * Set to true if panel was rendered */ protected $_isPanelRendered = false; ... /** * Make sure that errors will be displayed if application was terminated without to render error panel * For example if die() or exit() was called. * * $return void */ public function __destruct () { if (!$this->_isPanelRendered && ini_get('display_errors')) { foreach (self::$errors as $e) { echo sprintf("<br /><b>%s</b>: %s in <b>%s</b> on line <b>%d</b><br />\n", $e['type'], $e['message'], $e['file'], $e['line']); } } } ... public function getPanel () { $this->_isPanelRendered = true; .... }

  What steps will reproduce the problem? 1. enable zfdebug in application 2. make sure display_error is set to On 3. raise some Warnings in your controller code 4. call die(); in your controller What is the expected output? What do you see instead? The zfdebug will not be rendered but the errors/warnings should appear. What version of the product are you using? On what operating system? commit 109 Please provide any additional information below. I suggest to add to ZFDebug_Controller_Plugin_Debug_Plugin_Exception: ... /** * Set to true if panel was rendered */ protected $_isPanelRendered = false; ... /** * Make sure that errors will be displayed if application was terminated without to render error panel * For example if die() or exit() was called. * * $return void */ public function __destruct () { if (!$this->_isPanelRendered && ini_get('display_errors')) { foreach (self::$errors as $e) { echo sprintf("<br /><b>%s</b>: %s in <b>%s</b> on line <b>%d</b><br />\n", $e['type'], $e['message'], $e['file'], $e['line']); } } } ... public function getPanel () { $this->_isPanelRendered = true; .... }
• Oct 20, 2009

  issue 35 (v1.6: Implement animation without jQuery) Summary changed by gugakfugl   -  

  Summary: v1.6: Implement animation without jQuery

  Summary: v1.6: Implement animation without jQuery
• Oct 20, 2009

  issue 35 (Implement animation without jQuery) reported by gugakfugl   -   Only used for visuals, so a custom implementation will be more compatible

  Only used for visuals, so a custom implementation will be more compatible
• Oct 20, 2009

  issue 34 (v1.6: Make the slider resizeable) reported by gugakfugl   -   Resizing the panels will make it much easier to read long output

  Resizing the panels will make it much easier to read long output
• Oct 19, 2009

  r130 (- Output update) committed by gugakfugl   -   - Output update

  - Output update
• Oct 18, 2009

  issue 22 (Disable output rendering) Status changed by gugakfugl   -  

  Status: Invalid

  Status: Invalid
• Oct 18, 2009

  issue 22 (Disable output rendering) commented on by gugakfugl   -   Sending the variable ZFDEBUG_DISABLE as a get or post parameter will disable ZFDebug for that request. Using the plugins will always require testing for the existence first.

  Sending the variable ZFDEBUG_DISABLE as a get or post parameter will disable ZFDebug for that request. Using the plugins will always require testing for the existence first.
• Oct 18, 2009

  r129 (- Layout adjustments) committed by gugakfugl   -   - Layout adjustments

  - Layout adjustments
• Oct 15, 2009

  r128 (- Adding a getWriter method) committed by gugakfugl   -   - Adding a getWriter method

  - Adding a getWriter method
• Oct 14, 2009

  r127 (- Another cleanup for 1.6) committed by gugakfugl   -   - Another cleanup for 1.6

  - Another cleanup for 1.6
• Oct 14, 2009

  r126 (- Log layout) committed by gugakfugl   -   - Log layout

  - Log layout
• Oct 13, 2009

  r125 ([CHANGED] Logging improved) committed by gugakfugl   -   [CHANGED] Logging improved

  [CHANGED] Logging improved
• Oct 12, 2009

  r124 (- Update to 1.6) committed by gugakfugl   -   - Update to 1.6

  - Update to 1.6
• Oct 08, 2009

  r123 (- Optimized and moved around) committed by gugakfugl   -   - Optimized and moved around

  - Optimized and moved around
• Oct 08, 2009

  r122 (- Styling) committed by gugakfugl   -   - Styling

  - Styling
• Oct 08, 2009

  r121 (- Updating Time plugin to only do average over last 10 reque...) committed by gugakfugl   -   - Updating Time plugin to only do average over last 10 requests

  - Updating Time plugin to only do average over last 10 requests
• Oct 08, 2009

  r120 (- Adding Log plugin) committed by gugakfugl   -   - Adding Log plugin

  - Adding Log plugin
• Oct 08, 2009

  r119 (- More interface work) committed by gugakfugl   -   - More interface work

  - More interface work
• Oct 08, 2009

  r118 ([NEW] Prototype for new interface) committed by gugakfugl   -   [NEW] Prototype for new interface

  [NEW] Prototype for new interface
• Oct 04, 2009

  r117 (- Branching for updated interface ) committed by gugakfugl   -   - Branching for updated interface

  - Branching for updated interface
• Oct 04, 2009

  r116 (- Updating version to 1.5.4) committed by gugakfugl   -   - Updating version to 1.5.4

  - Updating version to 1.5.4
• Sep 24, 2009

  Documentation_Plugin_Time Wiki page commented on by onyxraven   -   overriding the REQUEST_TIME could make other things break. I'd suggest setting something like PHP_REQUEST_TIME in the top of your index and modifying the Time plugin to match.

  overriding the REQUEST_TIME could make other things break. I'd suggest setting something like PHP_REQUEST_TIME in the top of your index and modifying the Time plugin to match.
• Sep 22, 2009

  issue 31 (Add CSS validation to HTML plugin) Labels changed by gugakfugl   -   Makes sense to have a link to CSS validation, but it will require a bit more work, as css is often placed in separate files. I'll take a look when I have a bit of spare time.

  Labels: Type-Enhancement −Type-Defect

  Makes sense to have a link to CSS validation, but it will require a bit more work, as css is often placed in separate files. I'll take a look when I have a bit of spare time.

  Labels: Type-Enhancement −Type-Defect
• Sep 21, 2009

  Installation (Instructions for installing ZFDebug) Wiki page edited by gugakfugl   -   Revision r115 Edited wiki page through web user interface.

  Revision r115 Edited wiki page through web user interface.
• Sep 21, 2009

  Changelog (Changelog for ZFDebug.) Wiki page edited by gugakfugl   -   Revision r114 Edited wiki page through web user interface.

  Revision r114 Edited wiki page through web user interface.
• Sep 21, 2009

  Changelog (Changelog for ZFDebug.) Wiki page edited by gugakfugl   -   Revision r113 Edited wiki page through web user interface.

  Revision r113 Edited wiki page through web user interface.
• Sep 21, 2009

  Changelog (Changelog for ZFDebug.) Wiki page edited by gugakfugl   -   Revision r112 Edited wiki page through web user interface.

  Revision r112 Edited wiki page through web user interface.
• Sep 21, 2009

  issue 26 (plugins inside options should allow pre instanciated classes) Status changed by gugakfugl   -   Fixed in revision 111

  Status: Fixed

  Fixed in revision 111

  Status: Fixed
• Sep 21, 2009

  r111 ([NEW] Plugins in constructor options can now be instances, i...) committed by gugakfugl   -   [NEW] Plugins in constructor options can now be instances, issue #26

  [NEW] Plugins in constructor options can now be instances, issue #26
• Sep 21, 2009

  r110 ([CHANGED] Moving icon data to individual plugins, issue #8 [...) committed by gugakfugl   -   [CHANGED] Moving icon data to individual plugins, issue #8 [CHANGED] Improved verification of plugins

  [CHANGED] Moving icon data to individual plugins, issue #8 [CHANGED] Improved verification of plugins
• Sep 21, 2009

  issue 8 (Move icons to individual plugins) Status changed by gugakfugl   -   Fixed in revision 109

  Status: Fixed

  Fixed in revision 109

  Status: Fixed
• Sep 21, 2009

  r109 ([CHANGED] Moving icon data to individual plugins, issue #8) committed by gugakfugl   -   [CHANGED] Moving icon data to individual plugins, issue #8

  [CHANGED] Moving icon data to individual plugins, issue #8
• Sep 21, 2009

  issue 29 (Time Plugin is inaccurate) commented on by gugakfugl   -   Is the dispatchLoop time not adequate for measuring just the ZF time as is now in trunk?

  Is the dispatchLoop time not adequate for measuring just the ZF time as is now in trunk?