Closed (duplicate)
Project:
Entity Translation
Version:
7.x-1.x-dev
Component:
Base system
Priority:
Major
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
24 Jan 2013 at 15:23 UTC
Updated:
25 Jan 2013 at 16:37 UTC
Steps:
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
Comment #1
plachThis 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.
Comment #2
ethanethan commentedIndeed, -dev doesn't have this issue. We'll look into using 1851118 as a patch.
thanks
Comment #2.0
ethanethan commentedspecified how to make a content type field-translatable