Several types of fields are not being handled correctly when file is embedded in the WYSIWYG

This is happening because when media.format_form.js line 48 sets the initial value for the Tag field, it doesn't understand that the Tag field is actually a multiple value field, not just a regular text field. Therefore, if there is no value in the field, it says, duh, I'll set this to an empty string value in the string that is generated for the filter, instead of an empty array.

<p>[[{"fid":"5","view_mode":"default","fields":{"format":"default","field_file_image_alt_text[und][0][value]":"","field_file_image_title_text[und][0][value]":"","media_description[und][0][value]":"","field_tags[und]":""},"type":"media","attributes":{"class":"file media-element file-default"},"link_text":"foo.jpg"}]]</p>

Should be:

<p>[[{"fid":"5","view_mode":"default","fields":{"format":"default","field_file_image_alt_text[und][0][value]":"","field_file_image_title_text[und][0][value]":"","media_description[und][0][value]":"","field_tags[und]":{}},"type":"media","attributes":{"class":"file media-element file-default"},"link_text":"foo.jpg"}]]</p>

This error cascades all the way down through many layers until Taxonomy ultimately complains about it.

Added an issue to track the fix for this: #2062721: Add a white list of file fields that can be overwritten when the file is added in the wysiwyg

Marking as a duplicate of #2062721: Add a white list of file fields that can be overwritten when the file is added in the wysiwyg

This is not actually a duplicate. The referenced issue has a patch that just creates the whitelist. Whether Term reference is selected in the whitelist or not it does not appear as a field in the media browser for an image embedded via the wysiwyg.

The point of this issue to add the capability to override term references properly, not just to get rid of the error by not allowing the term references to be overridden.

This patch fixes the issue in the cases that I've tested, which are: single value fields of the types: term reference, entityreference, checkbox, and list (integers, strings, etc.). I suspect that it may not work with autocomplete widgets, but I have not tested that.

I should clarify: #9 above only works for single-value fields.

Hmm, #9 may not be working. Let me investigate some more.

False alarm, I guess something else was going on. Switching back to needs-reivew.

I haven't tested it too much, but here is a slight expansion to support multi-value fields, at least for select lists.

committed to dev 7.x-2.x