If you are having issues uploading photos, there can be a number of factors, but the most common issue is Not enough memory allocated to PHP to process large photo files or post max size or upload max size are too low.
The file size of the photos you are uploading and the dimensions of the file both play a factor when it comes to processing the photo on the server. If it is too large, there may not be enough memory allocated to the PHP to process the file. If you try to upload or process photos and nothing shows , get a fatal error, a 500 internal server error, or an error related to allocating memory, this is probably the reason why.
To increase the PHP memory, you will need to edit your sy-config.php file. In your Sytist admin, click on Settings in the main menu, then under the left menu click edit config file.
Look for these lines and increase the values to these if they are not already at these values:
This will try to allocate more memory to the PHP. You can also try 1024M for the memory_limit.
But there may be hard limits set by your hosting that won't allow you to go over a certain amount and if that is the case, you may want to contact your hosting company and see if they can increase these PHP values for you in the php.ini file .
Hosting with Godaddy and getting I/O errors?
An I/O error (Input / Output) can be caused by your hosting company having a limit on how much input and output (meaning uploading / downloading ) for a certain period of time. If you are getting this error, you should check with your hosting company and see if they can raise the I/O limit.
This seems to only happen with certain people hosting at godaddy and is an issue with the godaddy hosting.
403 or I/O Error only on certain images
A 403 or I/O error is usually generated by Mod Security on the server. So there is something about those images that is triggering Mod Security or some other security on the server, possibly in the meta data in the photos..
Re-exporting or re-saving those image might fix the problem.
You may also want to contact your hosting company and let them know you are getting that error and if they can make an exception for the Mod Security rule it is triggering