I have just had a detailed conversation with Nick from IonCube on the phone, and have to say what an increible support guy.

I asked him if there was any specific problems with the hosting company GoDaddy, as many of my clients and other people on the Internet using IonCube with GoDaddy appear to be having problems with IonCube.

He said that basically its not GoDaddy that's the problem, its just the way they have their servers configured, and need to have a different way of adding in the Ion Cube Loaders.

He said they cant make this any simpler as because there is no one standard server set up, they have had to make it such a way it will work with most/all servers how ever they have been configured. unfortunatly, this means that there are sometimes a little struggle getting it to work first time.

I asked him to send me a detailed instruction on how to do this, so i can add it to my forum.

If it is too complicated, most hosting companies, if you direct them to this post, will do it for you for free.



On servers where runtime install is not supported, which would normally include servers running PHP 5.2.5 onwards or those where dl() was disabled in some way, the Loader must be installed in the php.ini file.

The php.ini file may only be editable by the server administrators, however if a server uses PHP as a CGI module then user editable php.ini files may be supported. If this is the case, the Loader can usually be installed via the user's own php.ini file.

With CGI, PHP will usually load a php.ini file if it finds one in the same location as the first PHP file processed. Therefore it may be necessary to replicate the php.ini file into each location where there are top level PHP scripts (e.g. index.php) for a request that uses encoded files. Alternatively there may be a php.ini in the users area in a fixed location that is always processed. Loading a phpinfo file will indicate which php.ini file is being processed, and it should be clear whether the file is in the user's area vs. a system area.

Installing in a php.ini file is a one line edit of the general form

zend_extension = /path/to/ioncube_loader_xxx_y.z.so

where /path/to is the full file system path to where the Loader is located, xxx is the first 3 letters of the operating system in lower case, e.g. lin for a Linux system, and y.z is the PHP version, e.g. 4.3 or 5.2


So, what we do if trying to set someone up with a custom php.ini file is first to see whether they are supported. A phpinfo page will usually suggest whether one is already being processed, e.g. /home/content/d/i/y/diysec/html/php.ini in your example is probably a user editable php.ini file. If it looks like a system location, e.g. /usr/local/lib/php.ini, then creating a php.ini file in the same location as a phpinfo page and then refreshing to see whether the path to the php.ini file has changed should work. If in the user's own area, the location of the php.ini file should reveal the full file system path, and that can be used as the basis to work out where the Loader is installed. e.g. if ioncube_loader_lin_4.3.so where in html/ioncube in your example, then the following line for the php.ini file may work:

zend_extension = /home/content/d/i/y/diysec/html/ioncube/ioncube_loader_lin_4.3.so


Best regards
Nick
--
ionCube Support


A round a of applause please for Nick
Cheers mate
Ian