Is their anything known about mysqli changing permissions when suphp is enabled (or the other way round!)? Now, I must start off by saying I know NOTHING about php, msql or any other cryptic letters and rely on the script authors and my host to deal with matters. I run two scripts. My main one is basically a highly customised CMS. To run this securely and smoothly I had suphp enabled. My second script is a database made up from datafeeds and runs automatically, updating itself weekly. This is on my main domain and is just in the background. My other sites run the CMS and then have a piece of php to call and display information on the external database, which is run by my second script. All was working beautifully, until..... I noticed a site that was pretty dormant (and only using my first script) had an error message and couldn't read the database. This had happened with two other sites previously, and after investigating it was believed because msqli was not enabled. So my host enabled mysqli. Just after that I found out that my second script could no longer call from the external database, just giving the error message: The second script itself is still working perfectly on the main site, just that the external sites can no longer access it. On contacting my host they replied that "It appears your php sapi was seto to suphp instead of DSO. Has this always been the case? I've switched it dso and am looking over your sites now to make sure there aren't any issues." The second script can now call and display the info from the external database. HOWEVER, with them having disabled suphp I will now have to go through ALL my sites, entering ftp info into the admin area and changing certain file permissions to 666 and certain folders to 777. This is because of my main cms script. It requires ftp info because it automatically upgrades from the authors site. Now I really don't want to do this! so am really hoping somebody may have a solution.