Closed (duplicate)
Project:
Drupal core
Version:
7.x-dev
Component:
file.module
Priority:
Major
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
5 Oct 2010 at 21:31 UTC
Updated:
6 Nov 2010 at 17:57 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
duellj commentedHaving the same problem. Here's some more info on the error:
Fatal error message:
And here's the args being passed to the function that's causing it to fail:
Comment #2
aspilicious commentedOw btw, there is nothing wrong with the upload just a warning message
Comment #3
rfayProbably same as #935772: The function of the remove image button doesn't work correct
Comment #4
duellj commentedNow that the issue from #3 (and the issue that was a duplicate of) are closed, I'm increasing the priority of this issue. Definitely not a duplicate, problem still persists.
Comment #5
duellj commentedChanging title, this actually happens with all managed_file field types.
Comment #6
seanberto commentedSubscribing. Curious if/how this might be related to: #745590: #managed_file element does not work when #extended not TRUE, or when ancestor element doesn't have #tree=TRUE
Comment #7
duellj commentedDoesn't seem to be related to #745590: #managed_file element does not work when #extended not TRUE, or when ancestor element doesn't have #tree=TRUE, problem happens even when a #managed_file is at the top level of a form.
Comment #8
effulgentsia commentedSubscribing.
Comment #9
Anonymous (not verified) commentedsubscribe, coming from a duplicate report at #951158: Cannot upload default Image (field api).
Comment #10
groschan commentedAfter setting element property #tree to false looks good at first sight.
file.module:360 (function file_managed_file_process):
$element['#tree'] = false;
Except in this case element value won't be saved in form_state['values'].
Comment #11
Anonymous (not verified) commentedanother related issue - #953162: Removing default image from a image field in a content-type -> AJAX HTTP error occurred.
Comment #12
yched commentedThe report in the OP happens precisely in a case (Field instance settings form) where the #managed_file element is *not* at the top level of the $form.
@duellj - or others : can you report other examples of forms where the error happens ?
Until then, marking as a dupe of #745590: #managed_file element does not work when #extended not TRUE, or when ancestor element doesn't have #tree=TRUE
Comment #13
duellj commented@yched:
I get the same error described in #1 for all of the following cases:
Comment #14
aidanlis commented#745590: #managed_file element does not work when #extended not TRUE, or when ancestor element doesn't have #tree=TRUE is a different error message and upon further inspection does not seem to be related.
This bug also prevents uploading default images when using the Image widget in Fields.
This is effecting HEAD as of writing this post.
Comment #15
yched commented[edited out, I was on crack]
Comment #16
ygerasimov commentedSubscribe.
You can find callstack in attached screenshot.
Comment #17
duellj commentedIt looks like they took up this bug in #745590: #managed_file element does not work when #extended not TRUE, or when ancestor element doesn't have #tree=TRUE and the patch in #24 in that issue seems to fix this bug. Marking as duplicate