• Resolved TravisR

    (@travisr)


    Seeing File Up failures with files approximately 2MB or larger. Configured max size in the plugin is 16MB. Server is configured for a maximum post\upload size of 32MB. Observed so far on both Safari and Chrome.

    The failure results with the message “Sorry about that, but <filename> could not be uploaded”. I turned on debugging and observed an error of “Undefined index: nonce in …/wp-content/plugins/file-away/lib/cls/class.fileaway_management.php on line 23”. I then added some further debugging to that section of the code and observed that when the failure occurs, only the ‘upload_nonce’ field is present in the POST array (a success shows all POST fields). Looking at management.js line 1507 on, I see that ‘upload_nonce’ is the first field and that the second is the file itself, so it seems to me that something like a 2MB limit is being imposed, so that the rest of the POST array is being discarded. The ‘nonce’ field is then not present in the received data, causing the observed error. Does this seem correct, or do you see other possible explanations?

    Any ideas on why a 2MB limit would be imposed despite all settings appearing correct in the PHP configuration? I’m raising this with my web host in parallel, but wanted to see if you had any insight. Thanks.

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author thomstark

    (@thomstark)

    Do you have SSL enabled on the backend but not the front end, or vice versa?

    Thread Starter TravisR

    (@travisr)

    I am running SSL, but I am not aware of any missing configurations. The site and base URLs in WordPress are https, FORCE_SSL_ADMIN is set in wp-config, the base URL on your plugin is set to https, and there’s an HTTPS redirect in .htaccess. The value of fileaway_mgmt.ajaxurl is showing https. Is there something in particular that you think I might have missed?

    Note that I have since confirmed this issue separate from your plugin (e.g., also in WordPress media uploads), so if I may borrow from George Costanza – it’s not you, it’s me. But if you have any ideas, I’ll take them. The host hasn’t been helpful thus far. Thanks.

    Thread Starter TravisR

    (@travisr)

    FYI, the host has helped me resolve this. As I understand it, there was some sort of security filter in place that was being triggered by the content-length header. Thank you for you help.

Viewing 3 replies - 1 through 3 (of 3 total)

The topic ‘Upload failures’ is closed to new replies.