Internal Server Error 500 after php5.3.4 installed by hostingcompany

[Reneetje]

They also tell php5.3 had a bug which did not show 500 internal server errors, with the upgrade to 5.3.4. these show up again.

They however put a an .ini file in my root to prevent errors showing, however that doesn´t seem to help.

I also tried mebug on admin and includes but no logs were made so to me that means there are no problems with these...

Maybe they put a wrong code into my .ini-file. Is there a way you would or could do that ?

[kuroi]

I would run fast and far from this host.

I don't claim to be an expert in this area and so am happy to be proven wrong, but if you're reporting accurately what they're telling you, it sounds like complete nonsense.

Firstly, in so far as there is such a thing as PHP 5.3, it includes version 5.3.4.

I suspect that what they are describing here is the warning messages that started being output in with PHP 5.3.0 to warn people when they were using features that were going to be withdrawn in future versions. And it is possible to suppress them by adding an instruction to your php.ini file.

However, if that is what they're talking about, it's evidence that they don't know what they're doing, since that's not a bug. The warnings are completely intentional. And anyway, I don't see how this could contribute to the 500 Internal Server Errors that you're reporting.

Maybe somebody else will see a connection, but it sounds to me as though they're trying to apply a solution that worked for them to solve a different problem, without actually knowing what the real problem is here. And just spraying around solutions without a proper diagnosis of the problem can be very dangerous.

[Reneetje]

I don´t understand either. I translated exactly what they wrote in Dutch;
----------------------------------------------------------
In PHP-versie 5.3.3 fatal php errors were not shown. This because of two things: A bug in the FastCGI-error han##dler, which resulted in a 500 inter##nal error showing, and by a wrong advise from Microsoft about the changes in the global php.ini-file (which describes the showing or NOT showing of these errors).

By changing two configurations (display_errors, log_errors) fatal errors are shown again, but also PHP notices. These can be hidden with a php.user.ini–file with the following information;

error_reporting = E_ALL & ~(E_NOTICE|E_DEPRECATED)

That´s their information translatex exactly.
----------------------------------------------------------
René

[kuroi]

I'm unconvinced by their explanation. I don't recall not seeing fatal errors in PHP 5.3.3 - or maybe I just didn't cause any while we were using it here.

But if they were right, then your PHP errors should now be showing and could be addressed.

The trouble with this as a hypothesis is that they have upgraded to 5.3.4 which should solve the problem, and yet seems top have caused it. Also, fatal PHP errors usually cause PHP to stop and don't normally trigger 500 Internal Server Errors.

If they are suggesting that this problem is being caused by Fatal PHP errors, then those errors will be in the error log and thus easy to spot.