List items with user-filled placeholders

Created on 18 July 2012, over 12 years ago
Updated 7 June 2023, over 1 year ago

Hi, I am about to set up a chemical site which has to tag product nodes with so-called R-phrases and S-phrases. While the R-phrases look just innocent and feasible by means of pure taxonomy or list, the S-phrases contain items that need further precisioning on the instance level. So, for example we have an S-phrase like:
S47 Keep at temperature not exceeding ... °C (to be specified by the manufacturer)
For one node this could be 60°C, for another could be 90°C. Thus, in node edit form, we would have to have a list of S-phrases, which for certain values enabled a textfield to enter the placeholder value.
Some other phrases, like:
S23 Do not breathe gas/fumes/vapour/spray (appropriate wording to be specified by the manufacturer)
might need another list, rather than a textfield (although, for a start a textfield could do as well).

Such a placeholder would need a hint/description so to instruct user what kind of info they should enter.

Now my question is whether you'd see any interest to implement such a feature in that module. As you see, it is not an abstract problem, still - the number of users would rather be small.
I'd understand if you said, "no, sorry, too much on my to-do list", but considering your name as a good Drupal module brand, I chose to ask first.

Feature request
Status

Closed: won't fix

Version

1.0

Component

Code

Created by

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • 🇬🇧United Kingdom joachim

    > For one node this could be 60°C, for another could be 90°C.

    I'd use two fields.

    One field specifies the phrase, e.g. ' S47 Keep at temperature not exceeding ... °C (to be specified by the manufacturer)'.
    The other field specifies the temperature, maybe as a numeric field.

    Then glue them together in the theme output. Or use Computed Field to glue them together.

    I don't think this is something we'd implement here. It goes far beyond the module's use case.

Production build 0.71.5 2024