WordPress Development Stack Exchange is a question and answer site for WordPress developers and administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I was able to install and setup quite easily NetBeans 6.9.1 and Xdebug on my local environment, based on PHP 5.3.0 (XAMPP).

My problem now is the following: if I put a breakpoint on Wordpress's index.php or other Wordpress core PHP files, NetBeans correctly stop at desired position. If instead I put a breakpoint on a plugin file, an trigger the code execution NetBeans does not stop there.

Do you known how can be solved?

UPDATE: More info about what I am trying to debug

Plugin is called Vanilla Forums and has the following file structure:

- plugins
  - vanilla-forums
    + assets
    + nbproject
    + templates

I set the breakpoint inside a function named vf_validate_options defined in functions.php. I am sure that this function is executed, but NetBeans does not break there.

share|improve this question
If you put a throw new Exception('die'); statement after the line of the breakpoint, does it then stop (in the meaning that this kills/ends your request)? – hakre Feb 16 '11 at 9:51
@hakre Yes, it throws the exception (I am sure that the code where the breakpoint is set is executed) – Drake Feb 16 '11 at 10:35
@Drake: Is this code executed in the main page, or in an Ajax call? I believe the Xdebug debugger must be enabled with some GET or POST variables and then sets a cookie, maybe it is not enabled for the Ajax request? – Jan Fabry Feb 17 '11 at 15:40
I have the exact same problem and still can't find a fix! I'm using nusphere phped but I tried Eclipse too with no results! The only file that xdebug stop on the breakpoint is are the wordpress "core" files. Neither the theme's php file are debugable! Let me know if you find a solution, I made a post on the wordpress official forum with no replies:( – Kreker Feb 22 '11 at 20:30
I think Jan Fabry is onto the solution. I prefer to use the Firefox plugin EasyXdebug, which will add the XDEBUG_SESSION_START query parameter to all requests. – Jeff Stieler Jun 13 '11 at 13:34

You've followed these instructions right?


share|improve this answer

Hi @Drake:

Stupid question, I know, but have you "activated" the plugin? That's where I trip up when plugins are not being debugged.

share|improve this answer
Yes, plugin is activated. What am I trying to debug is a function trigger by a menu created by plugin self in administrator area. – Drake Feb 16 '11 at 16:42
@Drake - What is a "function trigger?" Can you please post your code as an update to your question? – MikeSchinkel Feb 16 '11 at 20:33

there is no way to debug the plugin's files. The only way I found for debug wordpress is to use nusphere phped wich is , unfortunately, not freeware. That seems the only one can do that, I don't know why but I spend very long time figuring how to debug with netbeans and eclipse...with no results!

share|improve this answer

Well, since WordPress itself provides WP_DEBUG, and wp_die($msg) ... why whould you need to debug with Xdebug? Unless you are building your plugin using a framework?

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.