Closed (won't fix)
Project:
Drupal core
Version:
8.0.x-dev
Component:
translation.module
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
29 Nov 2012 at 02:19 UTC
Updated:
29 Jul 2014 at 21:35 UTC
Part of meta #1853522: [META] (Re)introduce Views data integration for core modules. From the 8.x-3.x branch of Views.
| Comment | File | Size | Author |
|---|---|---|---|
| translation.patch | 15.26 KB | xjm |
Comments
Comment #1
lars toomre commented@xjm: Throughout this patch, shouldn't 'Definition of' be 'Contains'? Also ' id ' strings should be ' ID '.
Comment #2
xjm@Lars Toomre, this patch is not new code. It is taken verbatim from the 8.x-3.x version of Views, as stated in the summary, and has been uploaded as merely a starting point to reintroduce the integration.
Comment #4
andyceo commentedtranslation.patch queued for re-testing.
Comment #5
dawehnerDoes this actually still make sense if we have entity_translation?
Comment #6
dawehnerComment #7
tstoecklerNo, this would be a total waste of effort. #1952062: Remove legacy translation module in favor of content translation is the way to go. I don't know if we want to mark this postponed or directly won't fix or duplicate or whatever.
Comment #8
dawehnerThanks! Let's go with the simplest one.