Gubed PHP Debugger

[McCabe]

Ewald Kicker's excellent 'get started' howto for Quanta and Gubed:

Dutch: http://www.kde.nl/doc/quanta-debugphp/
English: http://www.very-clever.com/quanta-gubed-debugging.php
German: http://www.very-clever.com/debuggen-quanta-gubed.php
_________________
http://anticapslock.com

[MPCoughlin]

Experimenting revealed a subtle error in the tutorial, which says to copy the decompressed /Gubed directory to your DocumentRoot and create the LocalSettings.php file in that /Gubed directory. I discovered that Gubed won't work unless LocalSettings.php is in the /ServerScripts directory - below the /Gubed directory. For instance,

/Gubed/ServerScripts/LocalSettings.php
NOT
/Gubed/LocalSettings.php

In the case of Ubuntu/Damien Linux, this translates to:
/var/www/Gubed/ServerScripts/LocalSettings.php

Next, I discovered that, although the Gubed LocalSettings_dist.php example comments suggest that the default $gbdDebugServer is the local workstation, Gubed doesn't work without actually creating the following lines in LocalSettings.php, specified in the tutorial, i.e. even though they are stated to be the default settings.

$gbdDebugServer = localhost;
$gbdDebugPort = 8016;

Next, if you copied the decompressed /Gubed directory, including its subdirectories, as implied, but not explicitly stated, in the tutorial, then the default Quanta debugger location won't work, because the StartSession.php script is in a directory lower than the default Quanta path. The Quanta debugger path needs to be:

http://localhost/Gubed/ServerScripts/StartSession.php?gbdScript=/%rfpp
NOT the default
http://localhost/Gubed/StartSession.php?gbdScript=/%rfpp

Next, the order of operations in using Gubed with Quanta is subtle, but critical.

First, Quanta must be opened with a configured project (Project -> Project Properties -> Debugger setup, as above)
BEFORE
browsing (e.g. for local development) to http://localhost/Gubed/ServerScripts/StartSession.php

After specifying the /pathTo/YourScriptToBeDebugged.php (e.g. the path relative to the DocumentRoot) ... and clicking the "Debug" button, your browser status bar will say, "Waiting for LocalHost ..."

Finally, you can go back to Quanta ... and click your desired debugging method buttons, such as Trace ... or run the whole script etc.

Now, you can get to work ...

I hope this alleviates some Gubed/Quanta configuration frustrations for others ...

/Mike