Steps:

  1. enable field translation for a content type
  2. make at least one field in the content type translatable (Content types > Publishing options > "Enabled, with field translation")
  3. enable "Taxonomy term" as a translatable type at admin/config/regional/entity_translation
  4. add content of the type in step #1, adding tags
  5. save content
  6. observe error: "EntityMalformedException: Missing bundle property on entity of type node. in entity_extract_ids() (line 7647 of /home/pressflow/includes/common.inc)."

Note: either 1) disabling "Taxonomy term" as a translatable type or 2) changing all content type fields to not be translatable allows the new content to be saved without error.

Note: a warning is given when enabling Taxonomy terms as translatable for the first time: "The entities of type Taxonomy term do not define a valid path scheme: it will not be possible to translate them."

Seems like a common use case for Entity Translation, so it might be interference with another module of ours. But, has anyone seen this or is able to reproduce?

thank you!

Comments

plach’s picture

Version: 7.x-1.0-beta2 » 7.x-1.x-dev
Status: Active » Postponed (maintainer needs more info)

This might be a duplicate of #1851118: Incorrect ET Handler set in node/add form when inserting new taxonomy term. Please try the latest dev and see whether the problem is still there.

ethanethan’s picture

Status: Postponed (maintainer needs more info) » Closed (duplicate)

Indeed, -dev doesn't have this issue. We'll look into using 1851118 as a patch.

thanks

ethanethan’s picture

Issue summary: View changes

specified how to make a content type field-translatable