Page 1 of 1

Displaying compilation errors

Posted: Wed May 17, 2006 11:16 pm
by AZRoushStang
So I'm working with a site that is being hosted by godaddy.com. The problem I am having is that when I have a compilation error, I get no feedback. It just returns a blank page (no html at all when I view source). It makes it really difficult and a PITA trying to debug my fat fingers and sometimes sloppy mistakes. Is there a way to get the errors to display and tell me what went wrong, or is this something that I have to try and take up with godaddy?

Posted: Thu May 18, 2006 12:33 am
by Burrito
look at error_reporting() you should.

hint:

Code: Select all

error_reporting(E_ALL);

Posted: Fri May 19, 2006 12:04 am
by AZRoushStang
well that didn't work, but I think that godaddy makes it really difficult to change any perameters....using a phpinfo() funtion it prints out all of the php info and error reporting is set to 2047 (or E_ALL), but print errors is set to off...so I guess i have to call them...

Posted: Fri May 19, 2006 12:05 am
by Burrito
you could try some ini_set()ting as well...

Posted: Fri May 19, 2006 12:10 am
by feyd
If you set your own error handler, it will get called for every error (excluding fatals) regardless of error_reporting settings and their choices in display settings. It is a good idea to run through locally before uploading to a server however to help catch fatals such as parse errors.


set_error_handler()

Posted: Fri May 19, 2006 12:33 am
by AZRoushStang
I just got off the phone with GoDaddy...apparently, the account is set up as an ASP hosting account (would have been good to know), instead of a PHP hosting account After explaining to the tech "help" guy that if I can get none erroneous php code to run that there has to be a PHP interpureter on the server and hence it would reason that the error reporting would come back. Apparently, in their ASP hosting accounts the PHP works, but in a "simulated" mode, aka a lot of stuff doesn't work. That also may explain why my file uploads don't work. So, I am checking with the account owner to make sure we can change it to a PHP account...now if I'm still having the errors then I will have some words for their tech support....but, I'm hoping that it is as simple as changing the accont type....

Anyway, thanks for the inputs....if I'm still having problems after the account change then I will give those options a try....


-R

Posted: Fri May 19, 2006 12:37 am
by RobertGonzalez
Dude, GoDaddy kinda blows when it comes to hosting on their Windows accounts for PHP. There are a ton of PHP features that do not work on their Windows accounts. I had this same problem so I ended up going with a Linux hosting account. Fixed all the stupidity issues related to the hosting account (didn't do a thing for my stupidity issues). But their Linux accounts are really good for PHP development.

Posted: Fri May 19, 2006 12:57 am
by AZRoushStang
Thanks for the heads up...I'll have to keep that in mind...Do you know if there is a pricing difference for the PHP Linux vs. PHP Windows accounts...

Posted: Fri May 19, 2006 2:12 am
by RobertGonzalez
Yeah, the Linux accounts are a little cheaper. If you really want to save money hint that you are considering paying for a year all at once. When I did that they offered me a years hosting for like $26. Hard to beat that.