I have had a ticket open for 39 days now with my reseller provider to try to resolve this issue. One day, my client (billing/support) software ClientExec stopped working. After working through things with ionCube/ClientExec support, we determined that the culprit was that the dl() function has been disabled.
They claim that the dl() function is enabled
; Whether or not to enable the dl() function.
enable_dl = On
However, look a bit further and you can see that dl,system,exec,passthru,shell_exec all show up under disable_functions.
"Dear Sir, As mentioned before, there is no dl() in the diable_functions in the php.ini"
Not very helpfull. Especially when I CAN SEE that the dl function IS listed under disable_functions. I'm getting incredibly frusterated because it seems like they have no clue what they're doing and I haven't been able to bill my clients/use my ticket system for over a month now!!
Sorry to hear that this is still an issue. It is truly hard to believe that the support at your host are proving to be so inept and incompetent. Thankfully they are very much the exception rather than the rule.
As Karl said, send them a screen shot, and not only of the master and local setting for disable_functions, but of the setting for the configuration (php.ini) file as they may have looked at the wrong php.ini file to conclude that it's not disabled. Try to get a timescale from them as to when they will have the problem resolved.
In your case the host is clearly being negligent by not addressing in a reasonable timeframe the matter of their breaking your website, particularly as it can be trivially resolved, and at this point they are now causing wilful damage to your business. On the basis that you would have fair grounds for action through the courts to recover damages in these circumstances, you should try to speak to someone more senior than first line of support. One approach may be to phone them to discuss the cancellation of your contract.
You're welcome to encourage them to get in touch with us through our helpdesk or at 1-866-IONCUBE if they need assistance from a third party in getting to grips with the problem, as this could be solved in a matter of minutes once the right person at your host takes ownership of the problem. By going on record as encouraging them to seek assistance, any subsequent failure for them to do so will also give further basis to any claim of compensation on the grounds of negligence and incompetence.
Hopefully you can get this resolved soon now, but if not, there are plenty of hosts on WHT who would give good support and have not let this become an issue in the first place. Whilst moving host is not ideal, it may be for the best now that the credibility of the support from your host has been called into doubt, and the risk of further harm to your business in the future from any further incident at your host may reasonably be considered to be unacceptable.
If you haven't yet, try and telephone the host and have one last go as it can be easier to make progress with someone on the telephone. Explain that whilst enable_dl is on, the disable_functions list takes precedence and dl is on the list. If you still get nowhere then my advice would be not to waste any more time with them and change host as soon as you can, and consider at least a VPS or fully dedicated. The good thing about being on a shared server thus far will be that migration to another host should be easy.
The default timeout in the SOA record for your domain is only 4 hours, so once you've switched your A record to the address of a new server, it should be a maximum of 4 hours before people accessing your domain hit the new server and you'll be back up.