Hi
I have just started with PhpED and have got it up and running to debug on my localhost but I am having problems setting up to debug on my remote site. So my question is.
When they say you have to install the debuger module and edit the php.ini do they mean on the remote server, if so my hosting company say I can not edit the php.ini file, (and not sure about uploading the debuger to the php ext dir) so does this mean I can't remote debug or is there another way to do this.
Forgive me if this is a silly question but I have only started trying out PhpED and still trying to get my head around all the setting up

Many thanks
Steven

Yes, for remote debugging you need to edit the php.ini file on the remote server. For all intends and purposes, you have to have root/administrator access on the remote server to do a proper installation of the DBG module. In this case, it will be up to your hosting company to do this.

If you are on a shared server (which appears to be the case), I would not blame your host if they are not be willing to co-operate. I say that because shared hosting services are meant to be optimized for to run as smoothly as possibly for lots of website, and your host may not want to disturb this delicate balance with a special PHP module just for one customer (you).

Well below is more or less our official statement regarding this:
What hosting companies do concern of is that the software they install is compatible, stable, non-vulnerable and does not slow down the system
Since debugger is a very tiny module and does not operate if not enabled, it can not slow down virtual hosts it is not enabled for.
It can not slow down virtual hosts for which it is enabled until it runs debug session and for which it may slowdown up to ~5%. In other words, if you run debugger with debug session using IDE, the page will come ~5% later than it would without the debugger.
Regarding stability:
we have no crash reports for debugger for many years.
Regarding compatibilty:
we got no compatibility reports other than compatibilty with other 3rd part products and they all are solveable.
Regarding vulnerability:
commercial version of debugger is based on the open sources that come with free version of debugger and again we have no issues with vulnerability.