Can't edit taxonomy terms with image fields

Subscribing (not confirming)

Subscribing

Subscribing

Big scary issue!

I noticed that the 're-oder' icon shows up on the file field. I'm guessing some CSS/JS selectors are not working properly for this field type... Probably due to a non-generic concept of handling taxonomy fields.

This changes made it work for me. the problem lies with file_field_widget_submit function, that assumes the image field is in the $form, not in $form['term_data']. i have added a modified version of the function into taxonomy manager module, and altered the image fields to use it instead of the original one.

i hope i made the patch right, i never committed a patch before.

Subscribing.

Also, when clicking "UPLOAD" button, I get the following error:

Warning: Invalid argument supplied for foreach() in file_field_widget_submit() (line 760 of (...)/www/modules/file/file.field.inc).
Warning: array_values() expects parameter 1 to be array, null given in file_field_widget_submit() (line 767 of (...)/www/modules/file/file.field.inc).
Notice: Undefined index: field_test_image in file_ajax_upload() (line 270 of (...)/www/modules/file/file.module).
Notice: Undefined index: #suffix in file_ajax_upload() (line 279 of (...)/www/modules/file/file.module).

Subscribing

Thanks for the OnkelTem's patch!

This issue has had "critical" status for almost a year, is it anywhere near RTBC?

I did a lot of debugging and testing, including patch from #7. Nevertheless I couldn't really get it working, there were always some parts broken.
Thus I decided to hide file fields on the term data form in the meanwhile and link them to the original taxonomy form.
To really get it working (without huge hacks) we would either need a different form architecture of the Taxonomy Manager or different file fields.

So actually it's a workaround to avoid having to fix it? That is ok for now as long as this actually means that the scary behaviour reported in #1 is not happening anymore: "taxonomy manager will delete or mix up your images".

Please confirm that that bug has been removed with the latest -dev version.

yep. It worked in my scenario, further testing is of course always welcome.
As explained in my previous post, fixing this is really really hard and that's why I decided to go with the workaround.

Fix is included in the latest dev and beta3.

ok, so even though the workaround has been implemented, the core issue here is a wontfix for now. Adjusting accordingly, could help make it easier to find it back later also.

hm, well, on second thought it is not entirely correct to make it a wontfix either, what do you think?