The Symfony blog points out a handy feature included with the latest release of the framework - a web debugging toolbar that gives you a quick summary of the stats for the current page.

The symfony web debug toolbar is one of the developer best friend. It is always conveniently accessible in the browser when using the development environment. It gives you everything you need to know about the current page and ease the debugging of your applications. Until now, all the information available in this toolbar were hardcoded. But as of symfony 1.2, the web debug toolbar is entirely configurable.

The toolbar contains information like: the version of the framework you're using, cache information, logging, memory usage and the execution time of the page. They also include a bit on how to customize your toolbar, adding and removing panels from the bar as well as changing up the look with styles.

On the Debuggable blog Felix has posted two quick tips you can use in your CakePHP application - one related to debugging and the other about custom config files.

For tip #1

If you just put a debug() statement in, you will see hundreds of outputs and would not know which one belongs to the case you are interested in. My favorite solution to this problem is to use the Configure class as a toggle for showing the debug information.

For tip #2

This is a very simple one. To make your application configurable via a global config file, all you need to do is the following.

Both come complete with code examples.

On the local.ch blog today, there's this new post (from Philipp Kelle) showing how to, with the help of geben, easily debug your applications from emacs.

While PHP-developing it sometimes is just too tedious to do those 'add a echo here and there, then reload and search the echoed strings on the screen'-loops. So I searched for a debugger for my favourite editor emacs. After a lengthy install procedure I finally got it running: With geben on emacs you can debug PHP (step through and evaluate expressions).

The post steps you through the installation - adding in xdebug, changing the PHP configuration, and getting and installing geben (along with other required packages).

The Developer Tutorials blog has a new post covering a very helpful tool when it comes to debugging your sever-side scripts with something light and client-side (but powerful) - the FirePHP project combined with Firebug.

FirePHP is a plugin for Firebug, the web development plugin for Firefox, that allows PHP scripts to talk to a Firebug panel. FirePHP installs alongside Firebug, and provides a simple PHP library to bridge the two. FirePHP provides a window of insight into your PHP applications, with a simple debugging interface that won't interfere with your page content. If you already use Firebug on PHP-powered applications, FirePHP is definitely worth a look.

The FirePHP library installs onto your server and is included, via PHP, into your application. Passing errors back is as simple as using the fb() method to send information out to the Firebug instance waiting on your browser.

Jonathan Snook hands off a handy tip for the CakePHP developers out there concerning the debugging information that can be displayed at the bottom of your application's pages.

I just wanted to document this somewhere but whenever I work on a CakePHP project, there's always the debug info that sits at the bottom of the page. It's big and bulky and once I'm off the default CakePHP styles, it's usually pretty ugly. I've done various stylings but I finally took a moment to implement a really simple idea: Fixed position the table and then use hover styles to toggle the visibility.

He includes the simple four style entries that can be used to tame this debugging information down into something a bit more useful (and less intrusive).

Mike Bernat is a big fan of XDebug and has posted about why he thinks installing it is the best decision you'll ever make.

I finally got around to installing Xdebug on my development environment and have decided it is the best thing since sliced bread. Installation was a breeze and the information it provides when something has gone wrong is incredibly helpful during debugging.

He explains what the software does, how it can help you and your development - even how to get it up and running on your PHP install (seriously, it's drop dead easy...why haven't you installed it yet?). He also points to the tutorial on the Zend Developer Zone introducing the powerful tool.

The IBM developerWorks website has a new tutorial (login required) showing how to use the Eclipse PDT functionality to debug scripts your PHP development.

The PHP Development Tools (PDT) plug-in, when installed with Eclipse Europa, gives you that ability to quickly write and debug PHP scripts and pages. PDT supports two debugging tools: XDebug and the Zend Debugger. Learn how to configure PDT for debugging PHP scripts and discover which perspectives you use when taking closer looks at your scripts.

You'll need to have a machine with PHP, Eclipse, Apache and the PHP Development Tools already installed to follow along (as well as a trial version of the Zend Studio Web Debugger). They also include the methods for setting up XDebug as the debugger.

On PHPFreaks.com there's a new tutorial providing a beginner's guide to debugging in PHP (with the built in functionality PHP has, not external software).

Everyday the forums see probably hundreds of topics posted where the problem is a fairly simple error. [...] As a beginner, it can be difficult to find and solve these errors. By tackling each of these in turn, I hope to teach you some methods of finding and solving them.

They look at the different sorts of errors - syntax errors, fatal errors, warnings, notices - as well as some of the ones a bit harder to track down like database problems and logical errors.

On the Developer Tutorials website Akash Mehta has posted a tutorial showing how to debug your CakePHP applications with the help of the Zend Studio for Eclipse software from Zend.

After I recently upgraded to Zend Studio for Eclipse, I noticed one troubling feature of my setup - I couldn't debug applications with "pretty urls". [...] In this tutorial, I'll show you how to make use of that power and debug your Cake applications with Zend Studio for Eclipse.

His is a four step method of simple things to get the connection working:

• Disable all .htaccess files
• Add "index.php" to pretty URLs
• Set a breakpoint to debug
• Debug your application using /index.php/ URLs

In a new post to the SitePoint PHP blog Troels Knak-Nielsen gives a check up for a project he's worked some on - an interface he came up with to talk, via the dbgp-protocol, to a XUL frontend.

Spectator is a XUL application, which should make it cross platform. I have tinkered a bit with XUL before, but not a full application. [...] So what can spectator do? Mind that this is a first version and I really just meant it as a proof of concept. I think I got a bit further than that, but it probably still has a few bugs. Still, with the current version, you can step through a program, set breakpoints and inspect the stack. Really all you would expect from a debugger.

You can grab the latest version from the subversion repository on the Google Code website.