Active
Project:
Multiupload Imagefield Widget
Version:
7.x-1.0
Component:
Code
Priority:
Critical
Category:
Bug report
Assigned:
Reporter:
Created:
30 Nov 2012 at 09:41 UTC
Updated:
7 Feb 2013 at 04:34 UTC
Jump to comment: Most recent
I.e.
My filters:
1. Resolution between 640x480 and 1024x768
2. File size 2MB
I upload 18 files, 2 of them has resolution smaller than 640x480, and 5 - bigger than 1024x768.
After uploadding files i get list of 11 uploaded files and 7 form element for files which dont uploaded or cahnged (fixed resolution).
If list has following structure:
field_images[0]
field_images[4]
field_images[5]
and form elemnts
field_images[1]
field_images[2]
field_images[3]
MFW save only one first image.
if list:
field_images[4]
field_images[5]
and form:
field_images[0]
field_images[1]
field_images[2]
field_images[3]
MFW save nothing.
On the attached pictire - result after uploading images
Comments
Comment #1
ACD commentedI have the same problem, but, in fact it saves nothing (even those files which meet the requirements). They are shown as "uploaded" files in form (like in your screenshot) and also added to file_managed table, but when you click save - the files won't be added to file_usage table and will be deleted from file_managed during Cron run.
Also, another big annoyance is that when you try to upload unsuitable files widget duplicates "upload file" form element as many time as unsuitable files you have.
So, these problems are related. I think, the best solution is to save those files which meet the requirements and show only ONE "upload file" form element beneath them.
Comment #2
JeroenKool commentedSame here, one file fails (on requirements or otherwise) and the whole upload session is gone. They do show in the node before save, but after save they are gone.
Comment #3
chadmkidner commented+1 experiencing this issue. Thanks @divined for explaining why the images weren't all staying attached to the node. It was odd to me how I could get multiple images sometimes to stick while other only one or two. The problem now makes sense, any luck toward how to fix?
Comment #3.0
chadmkidner commented1
Comment #4
reeller_sk commentedAny update on this issue? I'm still experiencing it.