Here's an attempt at a clear message for users when overriding legacy title fields, based on a brainstorm at Montreal Drupal i18n sprint.

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

plach’s picture

Status: Active » Needs review

Status: Needs review » Needs work

The last submitted patch, better_replace_field_description.patch, failed testing.

13rac1’s picture

Applies with fuzz. +1 to the changes.

plach’s picture

Status: Needs work » Needs review
Issue tags: -montreal

Status: Needs review » Needs work
Issue tags: +montreal

The last submitted patch, better_replace_field_description.patch, failed testing.

mvc’s picture

Status: Needs work » Needs review
FileSize
3.03 KB

reroll for latest dev.

Status: Needs review » Needs work

The last submitted patch, title-better_replace_field_description-1280962-6.patch, failed testing.

mvc’s picture

Status: Needs work » Needs review
FileSize
3.78 KB

trying to fix related test

RogerB’s picture

I don't think that the field help text should be defaulted to 'A field replacing node title.' etc. This is information for the end user who is not interested in the internals - it is just the entity title to her.

Just leave these blank.

plach’s picture

I agree with @RogerB.

Moreover usually operation links are a single word, otherwise it may be confusing when they are displayed next to other operations.

mvc’s picture

@RogerB: now that I'm actually using this on a production site, I see that those aren't useful descriptions. I agree that we should drop them.

@plach: how about this:

line 23:
link = Convert
title attribute = Convert %field to a customizable field instance that can be translated.

lines 51-52:
title = Replace %field with a field instance
description = If this is enabled the %field will be replaced with a customizable field that can be translated.

plach’s picture

Honestly I don't see how "Convert" is better than "Replace", probably both are confusing for a user that does not grasp the difference between properties and fields. At least "Replace" is a terminology consistent with the underlying API.

mvc’s picture

I agree that both could be confusing :)

Also, on second thought, it's bad to use "convert" in one place and "replace" in another.

So how about this:

line 23:
link = Replace
title attribute = Replace %field with a customizable field instance that can be translated.

plach’s picture

Sounds good to me.

mvc’s picture

plach’s picture

Status: Needs review » Fixed

Sorry for losing track of this: just committed and pushed #15. I left out the capitalization of the replace link, since the other operation links are lower case.

Thanks!

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

  • Commit 8bff611 on 7.x-1.x, workbench authored by mvc, committed by plach:
    Issue #1280962 by mvc: Fixed Better description of field replacement...