Add more field types to Drupal CMS / Core

Created on 19 January 2017, over 8 years ago
Updated 1 July 2025, 6 days ago

It will be a great advantage to move some existing fields type to the Core:
- Currency
- Country
- Address

Actually, most of these fields are maintained at a very low level and the communication (feedback) from maintainers is unbelievable poor - for example, Drupal Currency has unanswered reported issues for more than 4 months.

🌱 Plan
Status

Active

Component

General

Created by

🇬🇧United Kingdom londova

Live updates comments and jobs are added and updated live.
  • Needs product manager review

    It is used to alert the product manager core committer(s) that an issue represents a significant new feature, UI change, or change to the "user experience" of Drupal, and their signoff is needed. If an issue significantly affects the usability of Drupal, use Needs usability review instead (see the governance policy draft for more information).

  • Needs framework manager review

    It is used to alert the framework manager core committer(s) that an issue significantly impacts (or has the potential to impact) multiple subsystems or represents a significant change or addition in architecture or public APIs, and their signoff is needed (see the governance policy draft for more information). If an issue significantly impacts only one subsystem, use Needs subsystem maintainer review instead, and make sure the issue component is set to the correct subsystem.

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 catch

    I think this could use an evaluation of which (if any) of these fields types are in use, or planned to be in use, in Drupal CMS. If they are, and they're otherwise high usage, then we could look at including them in core, but feels unlikely otherwise. There was also a discussion recently in slack, not sure there's an issue yet, about telephone really belongs in core, because a lot of sites have to install one or two contrib modules to make it usable.

  • 🇬🇧United Kingdom catch
  • 🇦🇺Australia pameeela

    I personally have never used the Currency or Country field and their usage is quite low. Address is included in the event recipe, and would be for other relevant recipes. I would be open to the argument that we should ship Address by default, but is there a case for the other two?

  • 🇬🇧United Kingdom catch

    I've also never used the country or currency fields.

    For me personally I would leave the address dependency to specific recipes (and pretty much the same with any other module that's not directly supporting base recipes), because if it's not installed, it can cause composer dependency issues down the line.

  • 🇦🇺Australia pameeela

    OK, that aligns with our general approach to only add modules we actively need rather than adding ones that may come in handy.

Production build 0.71.5 2024