StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POExtjs file upload request stays on waitMsg
text
Body
copied!<p>Through an ExtJs form I am uploading a file for processing in php (csv file in this matter).</p> <p>The processing all works fine without errors or anything. And as far as I know, all of the other requirement for a proper response are met.</p> <ol> <li>Return message = {success: true}</li> <li>Response header Content/Type = text/html</li> <li>Status = 200 OK</li> </ol> <p>However ExtJs keeps showing my WaitMsg instead of going to my success of failure functions</p> <p>Here is my form:</p> <pre><code>var form = new Ext.FormPanel({ id : 'mailinglist_form_import', labelWidth : 210, fileUpload : true, border : false, url : '/plugin/NewsletterManagement/mailinglist/import', items : [{ xtype : 'fieldset', width : 560, border : false, autoHeight : true, labelWidth : 215, defaultType : 'textfield', defaults : { width : 307, labelStyle : 'font-weight: bold;' }, items : [{ fieldLabel : t('Name') + ' *', name : 'mli_name', allowBlank : false },{ xtype : 'textfield', fieldLabel : t('File') + ' *', name : 'file', inputType : 'file' }] }] }); </code></pre> <p>The button:</p> <pre><code>var saveBtn = new Ext.Button({ text: t("Save"), iconCls: 'pimcore_icon_save', handler: function() { form.getForm().submit({ waitMsg: t('Saving...'), success: function () { var tabpanel = Ext.getCmp("pimcore_panel_tabs"); Ext.MessageBox.alert (t('Message'),t('Data has been saved')); form.getForm().reset(); grid.getStore().reload(); tabpanel.activate(gridTabId); tabpanel.remove(tabId); }, failure: function () { Ext.MessageBox.alert (t('Message'),t('Saving data failed')); } }); } }); </code></pre> <p>The PHP file contains an echo:</p> <pre><code>echo "{'success': true}"; </code></pre> <p>Any help is greatly appriciated.</p> <p>Greetz, XpertEase</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

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