To be consistent with the rest of the node form it seems logical that the parent items should be localized using form language and NOT the interface language. This proved harder to fix than anticipated, and the solution involves some code duplication (from menu.module) and re-processing of menu items, but it was the best I could come up with. If there are better approaches suggestions are warmly welcomed.

CommentFileSizeAuthor
#3 entity_translation-node-form-menu-items-form-lanuage-11182951-3.patch3.66 KBgnucifer
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

gnucifer created an issue. See original summary.

gnucifer’s picture

gnucifer CreditAttribution: gnucifer commented
Issue summary: View changes
gnucifer’s picture

gnucifer CreditAttribution: gnucifer commented
FileSize
entity_translation-node-form-menu-items-form-lanuage-11182951-3.patch3.66 KB
candelas’s picture

candelas CreditAttribution: candelas as a volunteer commented

@gnucifer, did you see that they are asking for a module co-maintainer? I wish I had the knowledge... :)

gnucifer’s picture

gnucifer CreditAttribution: gnucifer commented

@candelas Thanks, but I believe I would be a pretty poor maintainer since I am neglecting my own projects as it is. :) I have huge respect for all the active drupal maintainers out there. If I have issues with a module I tend to upload patches for my fixes, but I would not have the time to actively persue other issues. :/

candelas’s picture

candelas CreditAttribution: candelas as a volunteer commented

@gnucifer, thanks for your honesty :)

plach is working to release the 7.x-1.0
Maybe you can take a look to test one of the few issues that are left #1624830: Plan for Entity Translation 7.x-1.0 release
He really needs somebody to co-maintain since he is working a lot in the Drupal 8 multilingual system.
Have a good weekend :)