Early Bird Registration for DrupalCon Portland 2024 is open! Register by 23:59 PST on 31 March 2024, to get $100 off your ticket.
Here's an attempt at a clear message for users when overriding legacy title fields, based on a brainstorm at Montreal Drupal i18n sprint.
Comment | File | Size | Author |
---|---|---|---|
#15 | title-better_replace_field_description-1280962-15.patch | 3.78 KB | mvc |
#8 | title-better_replace_field_description-1280962-8.patch | 3.78 KB | mvc |
#6 | title-better_replace_field_description-1280962-6.patch | 3.03 KB | mvc |
better_replace_field_description.patch | 2.99 KB | mvc | |
Comments
Comment #1
plachComment #3
13rac1 CreditAttribution: 13rac1 commentedApplies with fuzz. +1 to the changes.
Comment #4
plachbetter_replace_field_description.patch queued for re-testing.
Comment #6
mvcreroll for latest dev.
Comment #8
mvctrying to fix related test
Comment #9
RogerBI 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.
Comment #10
plachI agree with @RogerB.
Moreover usually operation links are a single word, otherwise it may be confusing when they are displayed next to other operations.
Comment #11
mvc@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.
Comment #12
plachHonestly 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.
Comment #13
mvcI 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.
Comment #14
plachSounds good to me.
Comment #15
mvcComment #16
plachSorry 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!