i am seeing 2 major issues with the Title module that i am sure must be working (so quite confused they aren't).

1. as per the issue title; the default language (en) Title field seems to sync to whatever the last language is that i edit.
- so in this screenshot: http://screencast.com/t/Jw9Wwmq5, RU was last translation added; therefore EN title has synced to the title added in russian.
- if i edit the EN and put title back, then everything is correct: http://screencast.com/t/IpkPu7baJS
- but if i edit another lang or add a new translation; then EN title syncs again: http://screencast.com/t/UkWizGK0A2Dk

why is EN Title field syncing to other lang versions of the field?

CommentFileSizeAuthor
#6 2433249-6.patch564 bytesLeksat
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

liquidcms’s picture

it is working however on a more vanilla site.. ughh!!

liquidcms’s picture

gge’s picture

I'm having the same problem. Did you find any fix?

Thanks!

liquidcms’s picture

in the end i simply grabbed my backup db (prior to trying to set up ET) and started over. i did minimal setup this time; simply enabled et and title and disabled i18n sync. the node i was working with was more messed up now than first time. i deleted it and tried a new node.. and it seemed to work. everything has been well so far now with numerous bundles and both new content and pre-existing content.

in the end, no solid answer as to why this wasnt working. if i were to guess; and looking a little at the code in title and some of the issues posted which related to this; i think there are still some small issues with how Title does things. in most cases it works correctly but i think possible for it to be confused and then it isnt capable of correcting the situation and content remains corrupted.

seanr’s picture

Priority: Normal » Critical

The fix in #1269076: Translated title_field replaces node->title with translated value seems to be causing this. Why is title_entity_presave getting langcode as en, when the translation I'm editing is es? It looks like it's getting the site language, not the form language. This is a huge bug as it's destroying content.

Note, I'm using entity translation with language detection via subdomain.

Leksat’s picture

Status: Active » Needs review
FileSize
564 bytes

I believe this issue is what I've been looking for.

My STR were:
- at node/add/page create a node in German language with title "DE"
- add German (CH) translation with title "DE-CH"
- visit the Translate tab
Expected result: German translation preserves "DE" title.
Actual result: German translation has "DE-CH" title.

Attached patch fixes the issue to me.

plach’s picture

Priority: Critical » Major
Status: Needs review » Needs work

I'm sorry, #6 makes the whole if/else block pointless as it's equivalent to calling entity_language(). Demoting to major, since it seems this is not affecting every site installation...

plach’s picture

Status: Needs work » Closed (duplicate)
Related issues: +#2267251: Do not rely on "content language" in hook_entity_presave()

@catch rightly pointed out that this is likely a duplicate of #2267251: Do not rely on "content language" in hook_entity_presave().