Add the possibility to use a field without setting the node bundle

Created on 18 July 2019, over 5 years ago
Updated 8 June 2023, over 1 year ago

I noticed that the module explicitly requires a bundle and a field but does not allow to set more than one bundle field combination.
To enhance the functionality I have created a patch which allows setting the field for all node bundles.
The same functionality applies to the patch I submitted earlier for taxonomy terms.
I will add an updated patch there shortly.

✨ Feature request
Status

Needs review

Version

1.0

Component

Code

Created by

πŸ‡³πŸ‡±Netherlands thomasdik

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 States danflanagan8 St. Louis, US

    I really want this feature too.

  • Status changed to Needs review over 1 year ago
  • πŸ‡ΊπŸ‡ΈUnited States danflanagan8 St. Louis, US

    Here's a patch that allows choosing a bundle or choosing "Any bundle". It seems to be working for me and I don't think it introduced any BC problems.

  • πŸ‡ΊπŸ‡ΈUnited States danflanagan8 St. Louis, US

    Here's a few screenshots.

    Bundle selected:

    "Any bundle" selected

    A minor UX bug unfortunately is that the empty option label doesn't make sense on the field select.

    That would be easy to fix. I'm not interested in doing that until there's review though.

Production build 0.71.5 2024