This is a follow-up in response to #1188388-49: Entity translation UI in core comment 49 item 3

Problem

It's hard to find the location of the setting to enable translation on fields. Following a pattern of showing a hint as to the value of a setting in a collapsed fieldset or in a vertical tab, the entity translation ui can be improved.

proposed resolution

Improve UI by adding hint to field collapsed global settings like: GLOBAL SETTINGS: Number of values (1), Field translation (disabled)

Remaining tasks

Implement showing the setting hint in the collapsed field set.

User interface changes

Suggested change: http://drupal.org/files/s06-AddHintInCollapsedGlobalFieldSet-2012-10-03_1523.png

Open, the field set (already) looks like
http://drupal.org/files/s05-EnableTranslationOnBodyField-2012-10-03_1521.png

API changes

No API changes/additions that would affect module, install profile, and theme developers.

Comments

YesCT’s picture

Title: add hint to field collapsed global settings: GLOBAL SETTINGS: Number of values (1), Field translation (disabled) [Follow-up] » add hint to field collapsed global settings: GLOBAL SETTINGS: Number of values (1), Field translation (disabled)

adding to the list of follow-ups at #1836086: [meta] Entity Translation UI improvements

YesCT’s picture

Version: 8.0.x-dev » 8.1.x-dev

Drupal 8.0.6 was released on April 6 and is the final bugfix release for the Drupal 8.0.x series. Drupal 8.0.x will not receive any further development aside from security fixes. Drupal 8.1.0-rc1 is now available and sites should prepare to update to 8.1.0.

Bug reports should be targeted against the 8.1.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.2.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.1.x-dev » 8.2.x-dev

Drupal 8.1.9 was released on September 7 and is the final bugfix release for the Drupal 8.1.x series. Drupal 8.1.x will not receive any further development aside from security fixes. Drupal 8.2.0-rc1 is now available and sites should prepare to upgrade to 8.2.0.

Bug reports should be targeted against the 8.2.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.3.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.2.x-dev » 8.3.x-dev

Drupal 8.2.6 was released on February 1, 2017 and is the final full bugfix release for the Drupal 8.2.x series. Drupal 8.2.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.3.0 on April 5, 2017. (Drupal 8.3.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.3.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.4.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.3.x-dev » 8.4.x-dev

Drupal 8.3.6 was released on August 2, 2017 and is the final full bugfix release for the Drupal 8.3.x series. Drupal 8.3.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.4.0 on October 4, 2017. (Drupal 8.4.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.4.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.5.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.