Server change causes DSEFU Crash

chrisinoz · #1 07-01-2008, 12:48 AM

Hi - I have lodged a support ticket with John but should he not be around I thought I best ask here as the client site is down. Site has been running fine for 4 months or more. Nothing has changed. Then yesterday client got

The file /home/awoman/public_html/DSEFU.php has been encoded with the ionCube PHP Encoder and requires the free ioncube_loader_lin_4.4.so ionCube PHP Loader to be installed.

http://www.awomanscharm.com.au/

I am at a loss to know what to do at this point.

Cheers
Chris

chrisinoz · #2 07-01-2008, 01:42 AM

At lest I had the sense to disable dsefu in auth.php for now till a solution is found.:>

balinor · #3 07-01-2008, 03:30 AM

Did the host happen to disable Ioncube support on the server or upgrade the server in some way?

chrisinoz · #4 07-01-2008, 03:45 AM

John got back to me and concurs with your thoiughts - thanks. It certainly is NOT a problem with DSEFU. I am planning to use DSEFU again on another site.

chrisinoz · #5 07-02-2008, 01:29 AM

DSEFU was not the problem - Hoster had changed some settings. They rest it back after complaining. All working well.

hoosierglass · #6 07-03-2008, 07:23 AM

I just had the same thing happen to me today. Not sure how long it has been down either. Any clues as to what the host changed to cause this?

Emerson · #7 07-03-2008, 07:30 AM

Most likely they upgraded the web server software and failed to update the ioncube loaders to work with the new server version.

chrisinoz · #8 07-03-2008, 03:54 PM

I am assuming that what Emerson said is what happened - they certainly did a server upgrade at that time as 5 client sites of ours using a cms system crashed about the same time.

taponitrof · #9 08-21-2008, 01:28 PM

Hi,

I just had the same issue. What caused it was we added a php.ini file to turn OFF register_globals, but apparently, that, or something else in the script, caused the problem. Just thought I mention it so some one else could learn from my pain.

intel352 · #10 08-22-2008, 03:56 AM

Quite likely the server php.ini included Ioncube support directly. I'll bet the custom php.ini that you added, *didn't* include the Ioncube loader, which is why you saw that error.

You can download the Ioncube loader files from http://www.ioncube.com, to find out. Just put the /ioncube/ folder in the root of your X-Cart installation, if it works (while that custom php.ini is in place), then you won't have to worry about it any further