Comments on: WTF Bluehost Continued. http://brickblog.net/2008/01/03/wtf-bluehost-continued Brick blog, intended about Lego, but wound up everything else Thu, 28 Aug 2008 18:01:52 +0000 http://wordpress.org/?v=2.3.1 By: Jim Cns http://brickblog.net/2008/01/03/wtf-bluehost-continued#comment-4327 Jim Cns Sun, 18 May 2008 02:07:45 +0000 http://brickblog.net/2008/01/03/wtf-bluehost-continued#comment-4327 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? 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?

]]> By: Crazy Penguin http://brickblog.net/2008/01/03/wtf-bluehost-continued#comment-4308 Crazy Penguin Sun, 20 Jan 2008 18:10:57 +0000 http://brickblog.net/2008/01/03/wtf-bluehost-continued#comment-4308 You picked a real winner with being hosted by Bluehost!? <a href="http://www.inetintegrity.com/weblog/?p=1" rel="nofollow">Bluehost Blues!</a> You picked a real winner with being hosted by Bluehost!?

Bluehost Blues!

]]> By: Dave http://brickblog.net/2008/01/03/wtf-bluehost-continued#comment-4264 Dave Thu, 03 Jan 2008 18:38:42 +0000 http://brickblog.net/2008/01/03/wtf-bluehost-continued#comment-4264 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 :-) 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 :-)

]]>