User Tools

Site Tools


tutorials:image_upload_problems:start

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
tutorials:image_upload_problems:start [2012/03/27 19:03]
jonyo [Standard Uploader Debugging Messages]
tutorials:image_upload_problems:start [2014/09/25 16:55] (current)
Line 41: Line 41:
 This means that the uploader did not get back any meaningful error messages, such as "wrong file type" or an error code as mentioned in the previous section.  To narrow down the possible causes of this, attempt to upload the same file **using the Legacy Uploader**: This means that the uploader did not get back any meaningful error messages, such as "wrong file type" or an error code as mentioned in the previous section.  To narrow down the possible causes of this, attempt to upload the same file **using the Legacy Uploader**:
  
 +  * Do you have basic authentication on the directory you are using the software on?  If so remove it for a test.  The flash uploaded does some behind the scenes communication with the server to hide any errors from direct client view and basic authentication can corrupt that communication.
   * If the Legacy Uploader produces a //white screen// or PHP Fatal Error: There was a PHP error such as running over the memory_limit, a timeout error, or something like that which stopped the rest of the script from continuing.  You will need to make sure that PHP error logging is turned on, and look within the php error_log file for the error, or if the legacy uploader displays a Fatal Error that would also point to the problem.   * If the Legacy Uploader produces a //white screen// or PHP Fatal Error: There was a PHP error such as running over the memory_limit, a timeout error, or something like that which stopped the rest of the script from continuing.  You will need to make sure that PHP error logging is turned on, and look within the php error_log file for the error, or if the legacy uploader displays a Fatal Error that would also point to the problem.
   * If the Legacy Uploader works but the standard uploader does not:   * If the Legacy Uploader works but the standard uploader does not:
-    * The most common culprit is "mod_security" blocking access.  You can try turning off mod_security, or contact your host to adjust the mod_security configuration to allow Flash-based uploads to work((This was first reported in [[http://geodesicsolutions.com/geo_user_forum/showthread.php?t=8644|this forum post]])).  Your host will need to look at the mod security logs to find the reason for the block, then adjust the configuration so that it no longer blocks based on that "criteria"((We have found that what configuration changes are needed will vary from server to server, the most common problem is a red flag thrown by the user-agent used by Adobe Flash Player uploads)).  With most hosts, mod_security can be turned off by adding these 2 lines to your **.htaccess** file at the top: <code>SecFilterEngine Off+    * The most common culprit is "mod_security" blocking access.  You can try turning off mod_security, or contact your host to adjust the mod_security configuration to allow Flash-based uploads to work((This was first reported in [[http://geodesicsolutions.com/geo_user_forum/showthread.php?t=8644|this forum post]])).  Your host will need to look at the mod security logs to find the reason for the block, then adjust the configuration so that it no longer blocks based on that "criteria"((We have found that what configuration changes are needed will vary from server to server, the most common problem is a red flag thrown by the user-agent used by Adobe Flash Player uploads)).  If you just want to turn it off real quick to see if that fixes it, with most hosts, mod_security can be turned off by adding these 2 lines to your **.htaccess** file at the top((You may still want to find a more "permanent" solution if this is the cause, by talking to your host.  Note that for some hosts, adding the lines to the .htaccess file is the only solution.)): <code>SecFilterEngine Off
 SecFilterScanPOST Off</code> SecFilterScanPOST Off</code>
     * It could be the server "sent" the information back just fine, but the response is being inadvertently blocked by certain types of software running on the computer.  It could be a software firewall, ad-blocking or JS blocking software installed, or it could be a virus scanner that has "Internet Security" built in that might be blocking it from working.  You would need to check for any such software that might block things from loading on your computer, and temporarily disable them one by one, until you find the one that is stopping it from working.     * It could be the server "sent" the information back just fine, but the response is being inadvertently blocked by certain types of software running on the computer.  It could be a software firewall, ad-blocking or JS blocking software installed, or it could be a virus scanner that has "Internet Security" built in that might be blocking it from working.  You would need to check for any such software that might block things from loading on your computer, and temporarily disable them one by one, until you find the one that is stopping it from working.
tutorials/image_upload_problems/start.1332874994.txt.gz · Last modified: 2014/09/25 16:55 (external edit)