Hello,

I installed the module and selected only one "translatable entity type" -- which is "user". All I want to translate are Member names and mission statements.

However, hundreds of unrelated node fields (URLs added as article sources, for instance) were blanked.

I found out the "Users may translate this field" option has got to remain selected for contents to appear. Otherwise, all data seems to be lost (but can be retrieved by clicking on the checkbox).

In any case, make a full backup of your site (which I did...) before trying out this module.

CommentFileSizeAuthor
#7 entity-translation-magicdatareturns.png43.83 KBcommonpike

Comments

mediameriquat’s picture

mediameriquat commented
Title: Blanked fields and fears of data loss » "Per content type" options

OK I nailed it :

If I don't want a particular field (URL) to be translatable in user profiles -- and that same field is also being used in content types such as Article, Page, etc. its contents will simply vanish.

In other words, the "Users may translate this field" option should apply in the context of a particular content type, not the whole site.

This is a feature request, however I feel contents should not vanish when "not translatable", so I'll keep this post as a bug.

mediameriquat’s picture

mediameriquat commented
Title: "Per content type" options » "Per content type" options, otherwise contents will vanish
plach’s picture

plach
he/him
Primary language Italian
Location Venezia
commented
Title: "Per content type" options, otherwise contents will vanish » Field content unavailable after enabling Entity translation
Status: Active » Postponed (maintainer needs more info)

The translatable field property cannot be set per bundle (content type): at least for D7 this is the core behavior we get.

Leaving open to investigate the problem you reported and see if we can come up with a workaround. One thing is not clear to me: did you upgrade a D6 site or did you just enable ET after creating a lot of content?

mediameriquat’s picture

mediameriquat commented

The site was created in D7 from the start.

I enabled ET after creating a lot of content, as a way to translate user profiles with additional fields such as "About this member", "Website", etc.

sos4nt’s picture

sos4nt commented

We've had this problem too. When setting a content type to 'entity translation' all non-translatable fields are expected to be language neutral. Existing content however usually has a language so it doesn't show up afterwards. We've corrected this by manually changing every field's language to 'und' in the database.

plach’s picture

plach
he/him
Primary language Italian
Location Venezia
commented
Status: Postponed (maintainer needs more info) » Closed (cannot reproduce)

Closing the issue. Feel free to reopen if you can provide the steps to reproduce it.

commonpike’s picture

commonpike commented
Status: Closed (cannot reproduce) » Active
StatusFileSize
new entity-translation-magicdatareturns.png43.83 KB

You can set it to 'wont fix' or 'works as designed', but its not closed ?
Its easy enough to reproduce ?

  • install Drupal 7.12, install entity translations 7.x-1.0-alpha1
  • mark a field as untranslatable
  • existing data in fields from nodes that have a language is gone
  • mark it translatable again
  • data returns
plach’s picture

plach
he/him
Primary language Italian
Location Venezia
commented
Status: Active » Fixed

The latest dev should fix this by migrating data when switching translatability.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.