Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Commons 3.4 is much better when it comes to translation, but there seems to be an oversight related to exported fields. Example from profiles/commons/modules/commons/commons_groups/commons_groups.features.field_base.inc
'settings' => array(
'allowed_values' => array(
0 => 'Use group defaults',
1 => 'Public - accessible to all site users',
2 => 'Private - accessible only to group members',
),
'allowed_values_function' => '',
),
'translatable' => '0',
I guess you guys know the correct solution so I haven't spent any time creating a patch.
Comments
Comment #1
Devin Carlson CreditAttribution: Devin Carlson commentedField settings are translated using the Field Translation module (a sub module of the Internationalization module) which is included in Commons 3.4.
To translate the allowed values:
Comment #2
hansfn CreditAttribution: hansfn commentedThx for the detailed explanation - really. However, I'm opening this again and changing it to a documentation issue, since I can't see that this is documented. Or isn't https://docs.acquia.com/commons/develop/translate the right place to look?
Is there any way to make these strings exportable/extractable so they are available for translation on localize.drupal.org?
Comment #3
Devin Carlson CreditAttribution: Devin Carlson commentedThis is now documented at https://docs.acquia.com/articles/adding-another-language-your-drupal-7-site.