dave

Yah, I'm going to let them know how I solved it. Small web-hosting company of the client's choice. They're quick to reply to e-mails at least.

@SiNNut That succeeded in changing the local values in my phpinfo() and it didn't crash the site. Thanks! Still having an issue with some uploads, but that's probably a topic for another thread.

Thanks Tom. I've tried various combinations of things in php.ini, and as I mentioned even an empty php.ini. I went ahead and tried just post_max_size and upload_max_filesize as you suggested and got the same result as always. It doesn't seem to matter what's in it, the site just doesn't work if there's a file named php.ini in the web root.

I've got a user that's having trouble uploading images. So I take a look at my phpinfo.php and see that post_max_size is set to 8M. Figuring the user is trying to upload large images I decide 8m is too small. Simple problem, right? So I toss a php.ini file in the web root. post_max_size = 32M max_execution_time = 300 If I do that, phpinfo() tells me all is well, but my Processwire site stops working entirely. Whether I try to view the homepage or go to /processwire/ all I get is: <h1>Internal Server Error</h1> <p>The server encountered an internal error or misconfiguration and was unable to complete your request.</p> <p>Error has been logged. </p> Setting $config->debug to true doesn't give me any more info on the error, and nothing shows up in my cPanel's Error Log. If I delete every line in php.ini and just leave a blank file, the error still occurs. So it seems like I can't have a php.ini at all. I asked my hosting company if they had another way of changing the post_max_size and they just went ahead and threw another php.ini in there and crashed the site again. Any ideas?