Avoid depending on 'field_' field name prefix for determining bundle fields

Created on 23 August 2019, over 5 years ago
Updated 4 April 2025, 3 days ago

With #1393094: Make the field prefix in Field ui configurable and #2846872: Drop the 'field_' prefix by default and god knows what other issue its not safe anymore to count on the "field_" prefix of the field name to decide whether the field is user defined for a given bundle. Right now I have problem syncing such fields for the taxonomies import.
Here is a patch that needs test. It's not great, but the module appears to be in need for general refactoring, so It's tailored for the current code structure.

🐛 Bug report
Status

Needs review

Version

1.0

Component

Code

Created by

🇧🇬Bulgaria SimeonKesmev

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.

Production build 0.71.5 2024