Hi!
I am evaluating various PHP IDEs and most of them use the dbg debugger. I encountered one common problem among most IDEs:

- in order to debug a series of scripts I have to have a stop at the beginning of each script. This hiccuping is utterly annoying and makes the debugger basically unusable
- using a header("location:... redirect often confuses the debugger

BUT

when using NuSphere this doesn't happen. Good, you might say, but NuSphere is a bit expensive for a hobbyist like me and other IDEs offer similar or even more features for way less money.....except for the debugger implementation.

Is this a free vs. commercial dbg issue?
Is there any way to buy the commcerical dbg without forking over 300$ for NuSphere?
Is there anything I can configure in the free dbg version to overcome these problems?

Any pointers are greatly appreciated.

where did you see $300?

NuSphere PhpED Standard starts at $59 (well, now, while it is on sale), PhpED Pro is currently at $234 - still well below $300. If you are a non-profit organization or full time student - our sales have special programs for that too. Just let them know using Contact Us.

I saw the 299$ price in the version comparison list (http://www.nusphere.com/products/phped_verscomp.htm). This was quite misleading, but I did get the generous price of 53$ for Standard.

Sales issues aside, can anyone shed some more light on the other questions?

yes, you have to, until you decide otherwise.
Feel free to update debugger settings at tools->settings->debugger and uncheck stop on the first line after run.


are you sure it's debugger is confused? As far as I know it does not care if you call header() function, but if your script contains errors and shows them in the output, header() will fail to add header because output is started, but it's a common mistake and debugger has no relation to this at all.

I was talking more in general. Many other IDEs (such as WaterProof and EnginSite) use the free version of dbg and they do not allow for switching off the stop at script start option AND have the debugger debug more than one script. Also, all those that I tested had massive problems with the header() redirects.
All that made me look around for a different IDE that doesn't have these problems. Since a week I am a happy NuSphere user, but wonder if the difference is in the free vs. commercial version. I doubt that it is an implementation issue as it is unlikely that four or five companies goof up in the same way.

I don't think that problems with header() is somehow connected with debugger at all.
Regarding the four going by the same way, just take into account that phpedit was open source and free for quite a long time.

I have my doubts. I tested this with several other IDEs, without debugger header() redirects are no problem, as soon as I run with the debugger, it fails. I don't understand what this has to do with open source or free.
But what about the stop at script start, is that mandatory for the free version?

Any chance to get a straight answer to this?

I guess no answer is also an answer and one that probably says more than any of the answers that I got so far.

What I can do is to repeat the same answer. Debugger has absolutely NO relation to header function and in NO way it can affect its functionality.
BTW, why don't you read manual for header function if you don't accept answers posted there?

See tools->settings->debugger->stop on the first line after run

It is not the matter if I don't accept the answers, it is a matter of your answers not fitting my questions. NuSphere seems to be the only IDE that uses the commercial version. Many other IDEs use the free version. The free version generates the problems. I talked to the makers of the other IDEs and they all insist that a stop on first line of script is mandatory to make the free DBG version to work at all. They also state that using header redirects breaks the free version of DBG. Now I ask the apparent makers of DBG about this.

Do these differences have to do with the free version versus the commercial version?

The possible answers to this question are either "Yes" or "No".

They are not right.


No. Commercial version behaves exactly the same way regarding those "problems".