Early Bird Registration for DrupalCon Portland 2024 is open! Register by 23:59 PST on 31 March 2024, to get $100 off your ticket.
there should be some more textfields in the expert-field-template to make it look more important and expert-ish
for this reason there could be a pre and suffix field
I need this to put a zip code and a city name on one line divided by one space
Comment | File | Size | Author |
---|---|---|---|
#6 | Screen Shot 2013-10-11 at 23.53.03.png | 176.64 KB | yannickoo |
#5 | ds.field-ui.1529730-5.patch | 3.08 KB | Angry Dan |
field-zemplate-expert-field-prefix-suffix-mockup.png | 91.86 KB | loominade |
Comments
Comment #1
swentel CreditAttribution: swentel commentedLet's move that to #1388008: Allow custom attributes on DS field wrappers + affixes
Comment #2
swentel CreditAttribution: swentel commentedGoing to wait with this one - field group is a better and easier option actually to get this working.
Comment #3
loominade CreditAttribution: loominade commentedI recently have the problem that i want to have a suffix like
<br />
and
after a field and only if it is outputted. i think this cant be achieved using fieldgroupsComment #4
aspilicious CreditAttribution: aspilicious commentedThis is not going to change in Drupal 7.
Comment #5
Angry Dan CreditAttribution: Angry Dan commentedI needed this so I wrote a patch (it's against 2.4, because that's what I have installed but it might apply against -dev)
It just provides two big textareas - one for prefix and one for suffix so that you can put whatever you like in there - either to add a single tag at the end or to wrap a field in whatever markup you choose.
Comment #6
yannickooI would put them in an extra key because this is kinda confusing.
A textarea, really?
Here is screenshot of the patch from #5.
Comment #7
aspilicious CreditAttribution: aspilicious commentedThis is now officially a duplicat of #2076897: Prefix/suffix
Comment #8
Angry Dan CreditAttribution: Angry Dan commentedyannickoo, my use of #prefix and #suffix for wrapping an element is commonplace, both in Drupal and in DS and although I wouldn't normally do this across elements as I have done here, I was duplicating a practice used elsewhere in the same function for consistency. For that reason I'd suggest a separate issue and patch to change all usages of the practice, as irritating as that may sound.
And yes, really a textarea. Maybe with less rows, but definitely a textarea. That form is far too compacted as it stands - the classes and attributes fields are far too squashed in already.