Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.Hi, I think it would be useful an option on fields' edit page to specify if showing the help text before or after the field value. Now the help text position is fixed below the field (and I can't find any module which adapts it), but in certain situation it helps more if it's above. For example on a subscription checkbox where the explanation is important to be red before checking for accepting.
Edited:
This is a potential duplicate of #314385: Make position of #description configurable via the API. Read there for background discussion.
| Comment | File | Size | Author |
|---|---|---|---|
| #10 | field-description-before-1325488-8.patch | 6.29 KB | penyaskito |
| #8 | field-description-before-1325488-7.patch | 5.96 KB | penyaskito |
| #7 | field-description-before-1325488-1.patch | 4.01 KB | penyaskito |
| #1 | field-description-before-1325488-0.patch | 3.97 KB | penyaskito |
Comments
Comment #1
penyaskitoI had a look at it and made a kickoff patch for starting work on this. Let's see what the community thinks about this feature and the patch itself. The patch doesn't add the option to the UI yet, but gives the option settings throught hook_element_alter(). Tests needed too.
Comment #2
penyaskitoComment #3
mandreato CreditAttribution: mandreato commentedI've just installed your patch. It seems not hurting normal behaviour.
So, is next step to add an option to UI ?
Comment #4
penyaskitoYep. But I'm not sure where this option should remain.
My first thought is another column in admin/structure/types/manage/toc/display, but not sure if this should be a global setting of the field instead.
Comment #5
xjmThis is an interesting suggestion. I can recall wanting to be able to change this in the past.
Do we necessarily need a UI option for this? I would probably support adding the property to FAPI, but changes to the UI require more deliberation. Maybe we could decide whether to add the property to FAPI first, and then open a followup issue to add a UI option for it?
Also, note that the Drupal 8.x patch will need to be rerolled, because the core directory structure for Drupal 8 has now changed. (For more information, see #22336: Move all core Drupal files under a /core folder to improve usability and upgrades). Of course, we still need tests as well.
If you need help rerolling this patch, you can come to core office hours or ask in #drupal-gitsupport on IRC.
Comment #6
xjmComment #7
penyaskitoPatch rerolled.
Comment #8
penyaskitoLet's see if these tests pass.
Comment #10
penyaskitoFixed the tests. The xpath expressions were wrong in the assertions.
Comment #12
penyaskitoThis seems to be an undeterministic test of statistics failing (see #1346772: StatisticsLoggingTestCase->testLogging() fails with clean URLs in some environments). Retesting.
Comment #13
penyaskito#10: field-description-before-1325488-8.patch queued for re-testing.
Comment #14
Bojhan CreditAttribution: Bojhan commentedPlease see, http://drupal.org/node/314385
I dont think we should add a UI option for this, I understand the usecase - but its perfectly fine for contrib to start using this first.
Comment #15
penyaskitoThis is a potential duplicate of #314385: Make position of #description configurable via the API. Read there for background discussion.
Comment #16
yoroy CreditAttribution: yoroy commentedDuplicate indeed
Comment #16.0
yoroy CreditAttribution: yoroy commentedAdded reference to a issue with more description.