Use field label instead of the "On value" as label not working after update from 1.8 [#2061401]

Since the update the functionality to show the label instead of the value of a boolean field is not working anymore.

This unlike my other bug this one is completely reproducible.

Install a new drupal instance
Install i18n
Setup another language (german in my case)
create a content type with a boolean field
Inside the field set the option "Use field label instead of the "On value" as label"
When adding content for this content type the label of the field will show either empty or with the value of the field for the edition form

If you drush dl i18n-7.x-1.8 and overrite, do a drush cc all and voila,
the label is now shown instead of nothing/the value of the field. Below two images with my testbool field.

Comment	File	Size	Author
#5	Drupal-7-boolean-single-on-off-default-no-values__test-content-type__boolean_field_everything_set_to_default.png	48.3 KB	Sk8erPeter
#5	Drupal-7-boolean-single-on-off-default-no-values__test-content-type.png	33.01 KB	Sk8erPeter
#5	Drupal-7-boolean-single-on-off-default-no-values__EDIT_tab.png	31.28 KB	Sk8erPeter
#5	Drupal-7-boolean-single-on-off-default-no-values.png	49.51 KB	Sk8erPeter
#3	Drupal_i18n_7.x-1.10_boolean_field_label_FIXED_BUT_markup_empty.png	125.18 KB	Sk8erPeter
	Screen Shot 2013-08-09 at 15.55.14.png	48.98 KB	reptilex
	Screen Shot 2013-08-09 at 15.55.45.png	47.19 KB	reptilex

Comments

Comment #1

jose reyero commented 10 August 2013 at 09:28

Priority:

Normal

» Critical

Omg, we broke it again :-(

This is the issue I guess #1904368: [7.x-1.8 regression] Field translation fails in numerous situations

And this is the task for it not to happen again #2061999: Add tests for field translations to avoid regressions (i18n_field.test)

Comment #2

jose reyero commented 10 August 2013 at 09:33

Status:

Active

» Closed (duplicate)

Looking better, this should be already fixed in latest dev, see #2061401: Use field label instead of the "On value" as label not working after update from 1.8

Comment #3

Sk8erPeter commented 23 August 2013 at 21:56

Status:

Closed (duplicate)

» Active

Status	File	Size
new	Drupal_i18n_7.x-1.10_boolean_field_label_FIXED_BUT_markup_empty.png	125.18 KB

I just switched to 1.10 from 1.9, because I had the same problem. The anomaly has really been fixed on the EDIT FORMS (see before, with 1.9: http://i.imgur.com/R5No8hw.png, and after, with 1.10: http://i.imgur.com/MSMcAzl.png), BUT when viewing the result, the '#markup' key is empty, which results in an empty field. Here is an example with the default 1 (On) and 0 (Off) values:

Is it related to i18n updates? I tried it with two Drupals, with more themes, and I experienced the same anomaly when viewing the content. It may be related to other contrib modules too (in this case, I'm sorry for reopening the issue), but I would be grateful if you could check whether it can be caused by i18n. Thanks in advance!

Comment #4

reptilex commented 17 September 2013 at 14:33

Status:

Active

» Fixed

It is now corrected in 1.10.

Comment #5

Sk8erPeter commented 19 September 2013 at 17:56

Status	File	Size
new	Drupal-7-boolean-single-on-off-default-no-values.png	49.51 KB
new	Drupal-7-boolean-single-on-off-default-no-values__EDIT_tab.png	31.28 KB
new	Drupal-7-boolean-single-on-off-default-no-values__test-content-type.png	33.01 KB
new	Drupal-7-boolean-single-on-off-default-no-values__test-content-type__boolean_field_everything_set_to_default.png	48.3 KB

It is now corrected in 1.10.

Have you tested it? :)
Because no, this is not fixed - BUT as I found out, this is not related to i18n, it's related to the core.

This is a screenshot of a brand new Drupal 7.23 standard install, with Bartik enabled, one simple content type, values set to default, "Use field label instead of the "On value" as label" checked; "1" should appear (as a string), but no value gets printed: