Closed (fixed)
Project:
Plupload integration
Version:
7.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
23 Jan 2012 at 19:04 UTC
Updated:
9 Apr 2014 at 03:53 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
slashrsm commentedCan you describe which errors you encounter while having multiple Plupload elements on a form? I tested it on a node form with 2 image fields with Mupload widgets and I was unable to reproduce any issues caused by the fact that there are multiple widgets on a form.
Comment #2
nbucknor commentedOnly the first Mupload widget would submit correctly if you try to submit the form without clicking upload on each of the widgets. My patch tests to see if all widgets have completed their uploads before submitting the form. Previously the form would submit once the first widget has completed its upload.
Comment #3
slashrsm commentedOh... sorry. Now I get it...
It looks like it works and fixes the bug. Could you add Drupal.t() around strings?
Comment #4
nbucknor commentedPatch with Drupal.t()
Comment #5
annblack commentedI hit the exact same issue and had created a local fix. However, I like nbucknor's fix better. Thanks! I re-spun the patch so that it can be applied on top of beta4. It would be great if the fix can be integrated in.
Comment #6
slashrsm commentedCommited to 7.x-1.x: http://drupalcode.org/project/plupload.git/commit/710e33f
Thanks!
Comment #7
slashrsm commentedPrevious commit caused an unnecessary popup saying "Please wait while your files are being uploaded." on every submit. This should be removed by this commit: http://drupalcode.org/project/plupload.git/commit/3407285
I also think that errors currently do not work OK, if we have multiple errors on multiple plupload elements at the same time. It looks like the last error will overwrite all the previous ones. Since this should be fixed I mark this as "needs work".
Comment #8
nbucknor commentedI agree that error reporting with multiple plupload elements needs a lot of work. In my patch, I had a list of errors indexed by each element and separated by linebreaks. Somehow that got mangled in your commit to dev.
See below:
Comment #9
slashrsm commentedYou mean like this?
Comment #10
nbucknor commentedyup, but notice it should be index+1 instead of index1 for the text replacement bit.
errors += Drupal.t("@index: You must upload at least one file.\n",{'@index': (index+1)});Comment #11
slashrsm commentedCommited: http://drupalcode.org/project/plupload.git/commit/83e675a
Thanks!
Comment #13
liquidcms commentedwas this actually fixed? i have 1.1 and i cannot get 2nd plupload field to work - if i drag/drop an img to that field it simply displays the img full screen and if i drag an img into the first plupload field it adds it to both fields (as ready for upload).
Comment #14
liquidcms commentedtried the 1.x-dev as well and also does not work
Comment #15
slashrsm commentedThis is included in 7.x-1.1. This patch was mostly about error handling and making form aware of more Plupload elements.
The issue you report might be Plupload's issue. Have you checked their issue queue?
Comment #16
liquidcms commentedhmm.. ok, to be honest i took over dev on this project and didn't realize that plupload was an ext library - although on your project page you state:
i guess that is not correct? i need to d/l plupload myself and perhaps i do not have the latest.
Comment #17
liquidcms commentedi checked and i had version 1.5.1.1 of plupload lib; not sure which version i am supposed to have but i grabbed latest (1.5.6) and it does not help the issue.
Comment #18
slashrsm commentedHave you searched their issue queue?
Will correct the text on project page.
Comment #19
liquidcms commentednot much in their queue. i started using the mupload module which i think also uses plupload and it seems to work.
Comment #20
slashrsm commentedMupload dpends on this module. :) Could you check your code once again? Maybe you have to change ID's of your elements to prevent collisions.
Comment #21
slashrsm commentedComment #22
liquidcms commentedmy code? i have not added any code anywhere.
Comment #23
slashrsm commentedWhat module were you using in #13?
Comment #24
liquidcms commentedlol.. i'm confused. i was using this module - that's why i posted against this project.
Comment #25
slashrsm commentedThis is API module. You have no use from it unless you write your own code or use another module that depends on it. See project page for list of those.
Comment #26
liquidcms commentedahh, sorry, i see now (as i mentioned, were are not the original designers of this site) - the plup module is the one creating the widget - so likely that module which has the issue.
thanks for sticking with this.. :)
Comment #27
liquidcms commentedand sure enough, upgrading to the latest -dev of Plup fixes the issue.
Comment #28
slashrsm commentedGreat :)