Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>Just to verify is the <code>post_max_filesize</code> set to a high level? Because according to php.net:</p> <blockquote> <p><strong>If the size of post data is greater than post_max_size, the $_POST and $_FILES superglobals are empty.</strong> This can be tracked in various ways, e.g. by passing the <code>$_GET</code> variable to the script processing the data, i.e. <code>&lt;form action="edit.php?processed=1"&gt;</code>, and then checking if <code>$_GET['processed']</code> is set.</p> </blockquote> <p>Something to consider.</p> <p>for more info see <a href="http://php.net/manual/en/ini.core.php" rel="noreferrer">this link</a> and scroll down to the <code>post_max_filesize</code> section</p> <p><strong>UPDATE</strong></p> <p>In my experience if you're getting a WSOD it's usually do to <code>error_reporting</code> and <code>display_errors</code> being turned off OR the <code>memory_limit</code> being reached. In the script at the top I usually set the <code>memory_limit</code> to 1024M to verify that isn't the problem and the turn on <code>error_reporting</code> and <code>display_errors</code>... so put this before the file upload:</p> <pre><code>error_reporting(E_ALL); // or E_STRICT ini_set("display_errors",1); ini_set("memory_limit","1024M"); </code></pre> <p>That normally gets rid of the WSOD and gives you and error to work with.</p> <p><strong>UPDATE</strong></p> <p>Have you tried taking off the <code>@</code> error suppression in front of all your functions to see they are producing a specific error? Also what are you execution and input timeouts? and Can you verify what headers are being sent? (make sure it is <code>Content-Type=text/html;</code>)</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload