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

Category:bug» support
Status:Active» Fixed

Field 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:

  • Enable the Translation Field module.
  • Go to the Manage Fields page for the content type the group_content_access field is attached to.
  • Edit the group content visibility field and select the translate tab.
  • Select the translation operation for the language that you want to translate the allowed values into.
  • Select the "Field settings" vertical tab and enter the translated text for each allowed value into the textfields.

Component:Code» Documentation
Status:Fixed» Active

Thx 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?

Issue summary:View changes
Status:Active» Fixed

This is now documented at https://docs.acquia.com/articles/adding-another-language-your-drupal-7-site.

If you enabled the Internationalization module, you can enable translations for many of the structures that make up your website, including blocks, forums, menus, text formats (strings), and variables.

For more information about the Internationalization module, including a list of the included submodules that extend multilingual support to additional entities and structural elements, see the Internationalization (i18n) module on drupal.org.

Status:Fixed» Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.