Hi,
Several times I discovered a problem with Debug Bar switching on/off on the frontpage. On some installations it works fine on other it fails. Switching on/off in the backend seems to work.
Now I’ve tested Debug Bar on a resetted clean wp3.3.1 installation and theme TwentyEleven with all other plugins disabled. When I toggle Debug Bar no output field is displayed although it is contained in the HTML page (can be toggled on with Firebug). When toggling fails, the URI is extended with a ‘#’.
Original call: https://www.example.com/product-page/
After toggling fails: https://www.example.com/product-page/#
Also I found a conflict with the commercial plugin LoopBuddy. The meta boxes on the options page of this plugin could not be expanded/collapsed and the save button disappeared as long as Debug Bar was active. The reason must not be found at Debug Bar, but there may be other plugins which could have the same strange behaviour.
Jochen
]]>I use this plugin since a half year and I always wanted to give you some response. This plugin is very useful to me. I feel it is much more comfortable than solutions based on FirePHP. I can recommend it to everyone who needs to debug PHP code. Thus I’ve rated it with 5 stars.
]]>The calculation of the variable $currentWorkingFile only considers forward slashes. Windows uses back slashes instead. Thus the function explode() does not match. A more system independant approach may be:
$currentWorkingFile = basename(__FILE__);
$cwdFullPath = dirname(__FILE__);
$cwd = basename( $cwdFullPath);I use this mod since several month and had no problems on Linux or Windows.
]]>We are working to correct the issues related to the 3.1.3 (currently in beta) update. We plan to have a new version released shortly that will take care of both issues.
]]>Awesome idea! Thank you!
]]>