Hello!
As you can see here:
http://drupal.org/node/1676084
and here:
http://drupal.org/node/1549150
Entity Translation support was dropped in i18n-1.7. Nowadays we can't use Multilingual settings (namely "Set current language as default for new content", "Require language (Do not allow Language Neutral)" and "Lock language (Cannot be changed)") for Entity Translation-powered node types. Are there any plans to reintroduce that functions outside i18n? Maybe there is something in latest -dev (with all that brand-new system in) I should check?
| Comment | File | Size | Author |
|---|---|---|---|
| #5 | et-lock_language-1679736-5.patch | 3.92 KB | plach |
| #3 | et-lock_language-1679736-3.patch | 3.5 KB | plach |
Comments
Comment #1
plachNo, there is nothing about it in the current dev. My original plan was to use the i18n-provided options excluding synchronization. I guess we may simply want to enable the good ones again in ET.
A patch would be welcome.
Comment #2
plachMany parts of this should have been covered by #1280546: Introduce a language selection widget for every entity. Is there anything left out?
Comment #3
plachAfter reading more carefully the OP, it seems only the Lock language option was left out, and here it is. You can find it in the entity translation settings.
Comment #4
renat commentedI was going to close this issue, as the latest ET -dev provides Multilingual settings as standalone module and plays nice with i18n-1.7. Great work!
But patch from #3 doesn't work fine - when we apply it to ET -dev (2012-Sep-30), we can now "Prevent language from being changed once the entity has been created". But it'll prevent us from language selection even when we create entity - language widget is inactive. Clean Drupal 7.15 install with latest -devs of ET and Title.
Comment #5
plachSorry, I tested #3 only with already existing entities :)
This one should work.
Comment #6
renat commentedPatch from #5 works just fine, it's code looks good for me, so marking RTBC.
Comment #7
plachCommitted and pushed, thanks.