Closed (fixed)
Project:
Drupal Commons
Component:
Code
Priority:
Major
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
31 Oct 2012 at 08:59 UTC
Updated:
10 Jan 2013 at 17:30 UTC
If you need to build a multilingual community based on Commons, you'll probably use entity translation to translate your content and not content translation.
Why? Think about groups or events, where you only want to have one node. Or machine-translated comments to enable multilingual discussions.
Therefore it would be a benefit to include the title module (http://drupal.org/project/title) in Commons and replace all titles with an entity field and take care of it in all views build so far.
This would make it smarter or enable multilingual communities to follow updates on Commons more easily. Otherwise each Commons update would result in a huge amount of rework.
Comments
Comment #1
horncologne commented+1
Comment #2
ezra-g commentedLooks like the solution here is to add http://drupal.org/project/entity_translation to Commons.
Also, marking #1835688: Event registration type field not translatable as a duplicate.
Comment #3
slowflyer commentedTo solve this issue, both modules should be added to Commons
Comment #4
ezra-g commentedLet's add Title but stick with the core Translation module which is more mature (Entity translation is currently in Beta and only used on ~5,000 sites vs Core translation module which is available on all Drupal sites) and supported by services such as http://drupal.org/project/lingotek.
Comment #5
slowflyer commentedAdding title for now is fine!
There is a discussion going for modifying the core comments module to work correct with entity translation, which should be solved first.
Comment #6
ezra-g commentedTitle module is now added to the Commons make file. Thanks!
http://drupalcode.org/project/commons.git/commitdiff/f786695?hp=d1a0f9d5...