WTF Bluehost Continued.

I submitted a ticket December 23, 2007 and heard back from support on December 31st. Pretty good considering the holidays, I had not expected to hear until into the new year. So overall for response, I’m still fairly happy there. It turns out that I needed to put a customized php.ini file with an increased amount of memory for php scripts into every folder that may be running php scripts. No real explanation why, or what had changed, just that this needed to be done to fix the error.

I had explored this route from info I found on their site and thought I had tried it and it failed. Turns out for some reason the new php.ini file had failed to upload. Odd.

Regardless, I’m curious if anyone has encountered this before? It seems weird to me to have to put this file into every directory. Wouldn’t it be much more efficient for a single file to exist at the root that controlled the settings for the site. Then if one script folder needed different settings, you could dump a file into that directory? Or is this exactly what is happening, but because my site is a sub of the main apache site, I’m not seeing it that way?

Either way it’s fixed now, and I found new widgets for recent and random photos that pull from Flickr rather then gallery which I have stopped using.

3 Comments

  1. Dave
    Posted January 3, 2008 at 2:38 pm | Permalink

    This is what I turned up in Google:
    http://www.washington.edu/computing/web/publishing/php-ini.html

    Basically it should be looking here in this order:
    1. The directory from which the PHP script was called
    2. The root of your Web directory (typically public_html)
    3. The Web server’s default php.ini

    What I really think happened is you got a tech who heard of a solution and applied it. #1 does fix the problem. A better way to fix the problem is #2…but because PHP always looks at the directory first location #1 will always work.

    What probably caused it in the first place is you didn’t have a PHP.ini in either the root directory or the directory where the script was called, or it somehow got changed. Maybe they edited the PHP.ini for the whole server which was your default if you didn’t have #1 or #2 in place or working right.

    That be my speculation anyway, the detective that I am :-)

  2. Posted January 20, 2008 at 2:10 pm | Permalink

    You picked a real winner with being hosted by Bluehost!?

    Bluehost Blues!

  3. Jim Cns
    Posted May 17, 2008 at 10:07 pm | Permalink

    Crazy did blue host kill your kid or somthing? Why do you hate them so much. You put so much hate and effort into this. Tell me what is going on it your head?

Post a Comment

*
To prove that you're not a bot, enter this code
Anti-Spam Image

Your email is never published nor shared. Required fields are marked *
*
*