It should be possible to specify the language of a feeds target when translating with entity translation.

CommentFileSizeAuthor
#5 entity_translation_feeds-2553201-5.patch2.53 KBnlambert
entity_translation_feeds.patch1.7 KBnlambert

Comments

nlambert created an issue. See original summary.

damienmckenna’s picture

damienmckenna
Location TN, USA
commented
Status: Active » Needs review

Thanks for putting that together, I'll try to review it soon.

BTW, please try to remember to change the issue status to "needs review" after uploading a patch, that'll trigger the testbot.

nlambert’s picture

nlambert commented

Good point thanks.

Actually, I'm going to submit a new patch. I've been looking at these issues:

#2529538: Generic entity language support.
#1183440: Multilingual Feeds - Make field import language-aware

nlambert’s picture

nlambert commented
Status: Needs review » Needs work
nlambert’s picture

nlambert commented
Status: Needs work » Needs review
StatusFileSize
new entity_translation_feeds-2553201-5.patch2.53 KB

Actually the other issues don't necessarily apply since metatag isn't a field that can be configured to be translatable.
I'm wondering if we shouldn't check to see if the bundle isn't configured to be translated with Entity Translation before adding the :et: targets to the mappings form.

damienmckenna’s picture

damienmckenna
Location TN, USA
commented
Status: Needs review » Needs work

@nlambert: I'd vote for doing the additional check.

steva1982’s picture

steva1982 commented

Hi,
any news about this issue?
Thanks

bluegeek9’s picture

bluegeek9 commented
Status: Needs work » Closed (outdated)
//www.flaticon.com/free-icons/thank-you Thank you for your contribution!
Unfortunatly Drupal 7 is no longer supported. We encourage you to upgrade to a modern version of Drupal.

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.