This was helpful. The solution here is not intuitive at all.
I think this may fall under the category of a 'usability bug'.
Under the screen "Edit Path Map" with a short sentence that says "Edit server path map" you have to key in the same path twice.
"Path on server" was C:\Program Files\Zend\ZendServer\share\ZendFramework\library
"Path in file system" was C:\Program Files\Zend\ZendServer\share\ZendFramework\library
See screen shot
I honestly had no idea that "Path on server" and "Path in file system" had nothing to do with the root on my server. Why doesn't this dialog say something like, "'Path to shared Zend Framework library on Zend Community Server"? Moreoever, why do people need to key in the same path twice. Also quirky is that the second line in this screenshot gets added by Zend Studio each time the debugger gets run. See below screenshot.
Lastly here is something else that is a gotcha. Within the main dialog titled "Debug Configuration" there is an "Advanced" tab. This tab has a radio option called "The server". If you click it you may find that you'll be able to debug the first index.php page but not other pages. This also happens when "Debug all pages" has been selected. Moreoever, once you've selected the radio option "The server" there is no going back! You cannot unselect this radio button. You need to delete the whole configuration and start fresh.
I think this whole workflow needs to be reevaluated. Zend needs to communicate better to people debugging Zend Framework Projects / Applications with their Zend Community Server. They also need to mention the role of httpd-vhosts because everyone knows if you don't have your Zend Framework Project operating from the web root you'll soon run into problems. Most Zend Framework developers have lots of projects and theirfore I think have lots of vhosts and entries in there host file. Does Zend Studio introduce an exception to this? It seems like PHP projects within Zend Studio are intended to live outside of a web server and once "Debug" gets pressed their magically get server qualities, like http://
<myserver>/something. The problem here is that a Zend Framework module (application) called "something" now appears to be running outside the root (one directory in), which to my belief would cause all kinds of problems. Based on observation, I'd think if your ZF web application is not hosted from the root it's unlikely to debug correctly.
I'd love to know Zend's thoughts on this...