Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Take a look at these two posts in the uploadify forum on how to handle errors</p> <p><a href="http://uploadify.com/forum/viewtopic.php?f=5&amp;t=12" rel="noreferrer"><em>onError to display what's happening</em></a> and <a href="http://uploadify.com/forum/viewtopic.php?f=5&amp;t=14" rel="noreferrer"><em>Upload script error reporting</em></a></p> <p>there is a lot of useful info in there ..</p> <p><strong><em>Update</em></strong></p> <p>The following seems to do the trick for me ..</p> <pre><code>'onComplete': function(a, b, c, d, e){ if (d !== '1') { alert(d); } else { alert('Filename: ' + c.name + ' was uploaded'); } } </code></pre> <p>coupled with this version of the uploadify script</p> <pre><code>&lt;?php if (!empty($_FILES)) { $tempFile = $_FILES['userfile']['tmp_name']; $targetPath = $_SERVER['DOCUMENT_ROOT'] . $_REQUEST['folder'] . '/'; $targetFile = str_replace('//','/',$targetPath) . $_FILES['userfile']['name']; move_uploaded_file($tempFile,$targetFile); switch ($_FILES['userfile']['error']) { case 0: $msg = ""; // comment this out if you don't want a message to appear on success. break; case 1: $msg = "The file is bigger than this PHP installation allows"; break; case 2: $msg = "The file is bigger than this form allows"; break; case 3: $msg = "Only part of the file was uploaded"; break; case 4: $msg = "No file was uploaded"; break; case 6: $msg = "Missing a temporary folder"; break; case 7: $msg = "Failed to write file to disk"; break; case 8: $msg = "File upload stopped by extension"; break; default: $msg = "unknown error ".$_FILES['userfile']['error']; break; } } if ($msg) { $stringData = "Error: ".$_FILES['userfile']['error']." Error Info: ".$msg; } else { $stringData = "1"; } // This is required for onComplete to fire on Mac OSX echo $stringData; ?&gt; </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POUploadify: show error message from HTTP response
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USGabriele Petrioli
    1. USGabriele Petrioli
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThere doesn't seem to be a way to get at the HTTP response body. Thus providing more useful error messages from the server into the output is useless, since you can't display them.
      singulars
      1. PO
      1. UShopla
    2. COadded a version that works for me..
      singulars
      1. PO
      1. USGabriele Petrioli
    3. COOk, I see it now... Only onComplete has access to the response body. onError has not but that is where I have been looking, since I wanted to show extra information, you know, *in case of errors*. But apparently onComplete also fires for errors? Thus allowing us to get at the response body. Why the developer of Uploadify didn't just pass the response to the onError function as well is beyond me...
      singulars
      1. PO
      1. UShopla
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

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