Closed (fixed)
Project:
Mupload
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
29 Apr 2011 at 14:39 UTC
Updated:
26 Apr 2012 at 08:57 UTC
I get this notice when adding a node using the Mupload widget:
Notice: Undefined index: display_field in function mupload_field_widget_form() in sites/all/modules/mupload/mupload.module line 114
Comments
Comment #1
avizzino commentedSame problem here...any news?
In my case, when I try to edit the content, it comes combined with a:
Notice: Undefined index: preview_image_style in image_field_widget_process() (line 347 of C:\testsite\drupal\modules\image\image.field.inc).
EDIT1: this notice is repeated as many times as the number of images already loaded. The effect is that none of the loaded images can not be previewed. I also included some file field: No problems or notices with files.
EDIT2:
I am using:
plupload v 1.4.3.2
plupload module v. 7.x-1.0-beta2
mupload: last version to date.
Comment #2
Jiri Volf commentedFirst, big thanks for this module!
Same problem for me, versions:
mupload Thu, 28 Apr 2011 08:10:23 +0000
plupload 7.x-1.0-beta2 2011-Mar-30
plupload library 1.4.2
I enabled the multiple widget on two fields of a content type, one image, the other file. I did not get the second message as avizzino - when I tried to edit/create a node where there wasnt anything uploaded yet
when I tried to edit a node where there was something already, i got it combined with
Notice: Undefined index: insert in function insert_element_process() (line: 170 in /data/web/virtuals/1198/virtual/www/sites/all/modules/insert/insert.module).
in both cases there was just "Add new file(s)" but nothing to click on
update: tried plupload module and latest library from this http://drupal.org/node/1140666
the the plupload window appeared, however, when I uploaded more files, only the first one got saved. The others disappeared after the node was saved. The notice on line 114 remained there.
tried clearing cache, did not help. Tested with firefox 3.6.17 and opera 11.10.
Comment #3
avizzino commented@vlx:
I think we are having a different issue, or you have both mine and some additional ones: in my case, in fact, except for the notice messages and the missing preview of the images already uploaded, I do not have any lack in functionality!
Comment #4
vingborg commentedHmmm ... I'll have to look into this.
Please note that I'm actually using a homegrown patch of the Plupload module: http://drupal.org/node/1140666#comment-4402928
(I'm rolling an official patch Real Soon Now)
czigor, this module is a complete rip off your own module, so you probably know as much about the inner workings as I do ;-)
Comment #5
avizzino commentedAny news? I would really be happy to get rid of this little annoyment and be able to see the preview of loaded images when editing my content.
Thanks for your help!
Comment #6
baby.hack commentedI'm so glad to see something that indicates the ability to upload multiple images in a CCK ImageField in D7.
I'm getting similar issues, though.
I'm Using:
your home-grown patched Plupload module
latest mupload to date,
and plupload library 1.4.3.2
When creating content that uses this widget, in CCK, I get an error on the content creation page with the display_field warning. I am able to use the uploader widget, though.
Saving the content takes me the new node's page, where I get a whole list of errors and warnings, but the images do show up, so the upload works.
There are no preview images shown during node/content creation, but if I go back to edit the content, I can see the previews then, as well as the display_field warning.
These are the warnings I get just after creating content, on the new node's page. I don't these on the node's page after that:
Warning: unlink(J:\wamp\tmp\phpB3F.tmp) [function.unlink]: Permission denied in plupload_handle_uploads() (line 356 of J:\wamp\www\sites\all\modules\plupload\plupload.module).
Warning: unlink(J:\wamp\tmp\phpCC6.tmp) [function.unlink]: Permission denied in plupload_handle_uploads() (line 356 of J:\wamp\www\sites\all\modules\plupload\plupload.module).
Warning: unlink(J:\wamp\tmp\phpE5D.tmp) [function.unlink]: Permission denied in plupload_handle_uploads() (line 356 of J:\wamp\www\sites\all\modules\plupload\plupload.module).
Notice: Undefined index: display_field in mupload_field_widget_form() (line 114 of J:\wamp\www\sites\all\modules\mupload\mupload.module).
Notice: Undefined index: _weight in _field_sort_items_helper() (line 518 of J:\wamp\www\modules\field\field.module).
Notice: Undefined index: _weight in _field_sort_items_helper() (line 518 of J:\wamp\www\modules\field\field.module).
Notice: Undefined index: _weight in _field_sort_items_helper() (line 519 of J:\wamp\www\modules\field\field.module).
Warning: usort() [function.usort]: Array was modified by the user comparison function in _field_sort_items() (line 503 of J:\wamp\www\modules\field\field.module).
Comment #7
TripX commentedTested the module with the result:
Notice: Undefined index: display_field in mupload_field_widget_form() (line 114 of /var/www/web30/html/sites/all/modules/mupload/mupload.module).
... using the patched plupload (sites/all/libraries/plupload) and latest dev-version of mupload.
1. Added an image field
2. node/add/content-type => the message appeared
Comment #8
vingborg commentedThe "display_field" issue is resolved by the latest commit, so if any of you would check it out, I'll be grateful.
The issue reported by baby.hack is moved to #1159722: Undefined index: _weight.
Comment #9
vingborg commentedRe #6: "There are no preview images shown during node/content creation ..."
This is a consequence of the way Plupload works. I'm looking into ways around it, but it will probably depend on patching up the Plupload module.
Re #6: "Warning: unlink(J:\wamp\tmp\phpB3F.tmp) [function.unlink]: Permission denied in plupload_handle_uploads() ..."
This is very likely an issue with your Windows/Apache setup, in particular the permissions for writing to "J:\wamp\tmp\". Can you make the Plupload module to work without Mupload?
Comment #11
milos.kroulik commentedProblem described in #1 wasn't apparently solved so far, so I will create separate issue for it.