On client's request, we enabled translatability on 2 image fields at admin/structure/types/manage/story/fields on a production site with existing 'und' image fields.

For some yet unknown reason the image fields are not visible on their respective node/edit pages.

Screenshot_2874795_1.png

Leaving the confusing impression to content managers there's no image linked to this content.

Considering an update hook at our next deploy to 'rewrite' image field instances to their respective languages when still undefined.
This should imho being avoided and solved within the media module.
Any idea where we could get started ?

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

RAWDESK created an issue. See original summary.

RAWDESK’s picture

Issue summary: View changes
FileSize
338.97 KB
joseph.olstad’s picture

Sounds like you may have some content types using entity_translation, some using content translation and have some shared fields.

To fix this:
it is probably not a media issue, download the latest dev version of entity_translation (beta6) , assuming you already are using it.

Then apply these two patches to beta6 in this order

1) https://www.drupal.org/files/issues/entity_translation-content_and_entit...
2) https://www.drupal.org/files/issues/entity_translation_content_and_entit...

OR instead you could use the latest dev version of entity_translation and then apply this patch by it'self:
2) https://www.drupal.org/files/issues/entity_translation_content_and_entit...

#2870524: Field copy fails with content translation for fields with entity translation enabled

joseph.olstad’s picture

Category: Bug report » Support request
Status: Active » Postponed (maintainer needs more info)
RAWDESK’s picture

Thanks for your feedback Joseph!

We indeed have both entity as content translation module enabled.
But fields (at admin/structure/types/manage/.../fields) are not shared among # content types.

We are on beta5 of entity_translation, but i'll give your suggestion at #3 a try and reply accordingly.

Regards

joseph.olstad’s picture

It is written in the release notes for media 7.x-3.0-beta1 or 7.x-2.4 , for those using entity_translation it is recommended to upgrade to beta6 and apply that patch (or a newer patch).

I'm hoping that entity_translation puts out a new release very soon with that issue fixed. If you can, please make some noise in there, shake up a few trees.

RAWDESK’s picture

Hi Joseph,

Here's some feedback about your applied advisory :
- updated media module from 2.0 rc12 to 2.6
- updated entity_translation module from beta5 tot beta6
- applied both patches on entity_translation :
https://www.drupal.org/files/issues/entity_translation-content_and_entit...
https://www.drupal.org/files/issues/entity_translation_content_and_entit...

Sorry to inform you but the reported symptom still remains.

joseph.olstad’s picture

RAWDESK’s picture

I'll check it on Monday.
Having a hunch this might be the one to solve this.
Thanks!

RAWDESK’s picture

Performed the proposed upgrade (7.x-2.0-beta2 > 7.x-2.1) but still not getting my 'und' file thumbs visible inside node/edit pages.

joseph.olstad’s picture

Status: Postponed (maintainer needs more info) » Active

Hmm.

Chris Matthews’s picture

Version: 7.x-2.0-rc12 » 7.x-2.x-dev
Status: Active » Closed (outdated)
Issue tags: -translatable fields, -thumbnails, -node form

Recent versions of media have resolved most of peoples concerns and is compatible with entity translation, multilingual and various advanced configurations. Due to the high volume of inactive and most often irrelevant issues we are Closing this as (outdated). If for whatever reason this issue is important to you AND you still have issues after checking the media recipe documentation, then let us know and we will review your concerns.

Otherwise, see the recipe documentation for how to configure media and for troubleshooting tips OR refer to the media_dev distribution if you want to see a working media setup.

As mentioned, feel free to make some noise in this issue if you still feel it is important to you or someone else.

Thanks,

Media team