Closed (works as designed)
Project:
Entity Translation
Version:
7.x-1.x-dev
Component:
Documentation
Priority:
Major
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
8 Oct 2013 at 09:46 UTC
Updated:
17 Jan 2019 at 01:23 UTC
Jump to comment: Most recent
Comments
Comment #1
plachWould enabling Multilingual content and disabling language selection work? Didn't try that.
Comment #2
gaëlgI enabled Multilingual content and its dependency Content translation. I changed nothing else (in the "Publishing options > Multilingual support" part of the content type settings, I let "Enabled, with field translation"). I can now translate content type names.
But it breaks the multilingual system I set. For example, a node written in french (french selected in the language select) appears on the english version of the site. Before, I had what I wanted, i.e. "English translation unavailable". I also have no more Edit tab upon my node (I don't know why at all, it might be unrelated).
It's not very surprising as two modules try to handle the same thing. You explained there that ET and MC are architecturally incompatible.
So this is maybe more of a feature request? If so, I can try to help. I guess it would simply need to do in ET exactly what MC do to make content type names translatable.
Comment #3
plachNo, sorry, ET has nothing to do with translating user-entered strings. If the workaround does not help, not even after disabling language selection, I guess we need a feature request to decouple content type string translation from node translation in the i18n project.
Comment #4
gaëlgThis definitely makes sense to me. Issue created: #2108063: Decouple node type strings translation from node translation. Thank you.
Comment #5
plachNo problem :)
Comment #6
gaëlgActually, this seems to be not that simple. @plach: could you please read this? https://drupal.org/node/2108063#comment-7963147
I can see 3 options:
- support ET compatibility with Node Translation and Multilingual Content, and try to fix any encountered problems such as #1669494: Selecting language in new node and saving, keeps node language neutral. Of course I could try to help for any bug I would face if I finally enable both modules on my project.
- make ET implement all features of Multilingual Content, which includes content type translation.
- get i18n maintainers agreement for decoupling content type translation.
For the time being, I personally use my decoupling patch. So this problem is not especially mine nor especially urgent, I just mean to move things forward for all users.
Comment #7
plachThanks for taking the time to summarize the situation.
I think ET and the language selection feature of Multilingual content are architecturally not compatible, since that filters out nodes by language and an ET-translated node does not have a "single language" from this POV.
Given @Jose's answer, I think we should try and identify what is actually causing troubles beyond language selection. If the latter is disabled, things should work or at least it should be possible to make them work.
I'd keep replicating content type translation in ET as the very (very very) last option.
Comment #8
gaëlgAllright. Thanks for the quick answer. I will enable both modules and submit/reopen issues for encountered bugs. To avoid new misunderstandings, can you clarify what you mean by "Language selection feature"?
For me, i18n language selection is disabled for a content type when "Enabled, with translation" is not the selected choice in the "Publishing options" part of the content type settings. This result in all options disabled in the "Multilingual settings" part. But I might have missed some other setting.
Comment #9
plachI did some testing, as I never actually enabled Multilingual content in D7 sites, and I realized that the feature I am referring to as language selection is now provided by the Multilingual select module, which is incompatible with ET. Apperently Multilingual content should be fully compatible with ET or at least it should be possible to make them work together.
Hence the way forward is definitely enabling both ET and Multilingual content and fixing any bug you may encounter. For instance you might need to reopen #1669494: Selecting language in new node and saving, keeps node language neutral.
Comment #9.0
plachUpdated issue summary
Comment #10
gaëlgThis is clearer now. I enabled ET and Multilingual content, and good news: it looks like I cannot reproduce the bugs I had, especially this one: https://drupal.org/node/1669494 (at least for the moment and in my use case). Thank you again, this was a documentation issue and it's fixed!
Comment #11.0
(not verified) commentedUpdated issue summary.
Comment #12
kopeboyI am sorry guys to reopen this but I didn't get how I should translate content types labels/settings when configured to be translated with Entity Translation.
While Field translation works together with ET, Content translation doesn't.
For example, I'm using Italian as my default language, with detection = URL prefix (nothing for italian, en/ for English).
If I create a node and try to translate while still in Italian language interface, the link is (en/node/xxx/edit/add/it/en) and I get a redirect loop.
If I manually input the path to be /node/xxx/edit/add/it/en I can add the translation, but then when I visit my node and click on the English link for the interface translation (link is en/node/xxx from node/xxx) I get the redirect loop.
I noticed that to get this working, the "Source language" setting at admin/config/regional/i18n/strings must be the opposite of the Language you select in the add node form for the content you are creating :/ weird and of course unusable.
Also, if I visit the translated node path when the node hasn't been translated yet, I get a "Page not found", while ET should provide me a fallback right?!
All in all, if this won't fix, I think you should really help to modify this page of the handbook https://www.drupal.org/node/1280910
This is advising something which doen't work (at least in my case?).
Comment #13
kopeboyAny updates?
If I am doing something wrong, this documentation needs some work, otherwise it is a bug.
Comment #14
creact commentedSame exact problem here. Unable to translate content type names.
Comment #15
stefanos.petrakisResponding to #12:
The issue discussed here is:
which has been resolved since, Multilingual content now plays well with ET, see #1662884: i18n_node_type_enabled is incompatible with Entity Translation (field translation) type. ET has nothing to do with translating strings (incl. content type names/settings), see #2107219-3: How to translate content type names?, you only need a recent version of Multilingual content (i18n_node) for that to work together with ET.
The rest of the problems you are having are not related to this issue.
And the documentation, albeit minimal, is accurate in what it states.
Responding to #14:
Same here, plus, unless you provide some more info, this is unrelated to ET.
Comment #16
casperone commentedI am looking for some direction and guidance on translating the name of a content type. I am new to i18n and have the impression NOT using Content Translation was best.
I have been using Entity Translation for all English/Spanish needs and now cannot find a solution to translate a Content Type Name.
I tried enabling Multilingual Content and this caused the Translate tab to disappear when Adding Content, it also caused a some of my pages Spanish translated pages to have a strikethrough on the translation switcher and the translated page was no longer available.
Can anyone provide some help?
Comment #17
stefanos.petrakis@casperone: This is really not an Entity Translation issue, as explained in the comments and this issue is actually closed, please don't
re-openpost further comments here. If you feel this needs special attention, open a new ticket.I did try very quickly to see what the problem may be, but I couldn't see anything wrong.