OK, here's the deal. I've implemented image gallery nodes in D7 the straight-forward way, i.e. create node type 'gallery' and add an imagefield with unbounded number of values. Nice markup via Views/EVA, done.

Now, to make the image upload convenient, I tried the following ways and got the respective results:

Multiupload Filefield Widget: The uplaod goes through, images appear on server side, but php runs out of memory while computing the ajax response for the upload.

Plupload widget: Upload works, but side crashes on save. I get lot's of visible json instead of the saved side.

Plupload via Fielfield Resources: Upload goes through, after that no visible response. On save, I get a long list of copy/rename error messages above the actual side.

The problems are present for pure file fields, on a otherwise pure D7 installation, so image processing is off the table as well as memory polluting modules (up to the ones mentioned above, appearently).

So the question is, why is it so memory consuming to compute a not so lengthy ajax response? The side shall collect several galleries containing each around 200-400 pics, so a nice way to bulk upload those jpgs would be great.

1 Answer 1


For completeness, the only stable way I found (and it's still not perfect, though) is to use plupload in combination with block_upload to get a PLUpload widget on the content site once it is created. It still is not the perfect workflow, but it currently allows me to dump 100s of photos/files into one filefield. Using PLUpload during node creation didn't work, btw.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.