The 2026 Drupal Business Survey is open. Your response will help shape the future of the Drupal business ecosystem.Currently if a feature defines a 'field' but not the corresponding node type, features-update (fu) will loose the field instead of suggesting the new one.
This can be reproduced using openpublish and openpublish_article_extra_media feature (the field it defines disappears, but fu on the openpublish_article will add the field to article as node suggests that field).
| Comment | File | Size | Author |
|---|---|---|---|
| #1 | 2000238_features_field_instance_field-1.patch | 2.53 KB | hefox |
Comments
Comment #1
hefox commentedComment #2
hefox commentedTested this via fu and the ui; both recreates changed over to field_instance =)
Comment #3
damienmckennaDuplicate of #1966062: Updating from older version to beta2 doesn't auto-select fields, but this has code so we'll keep it.
Comment #4
hefox commentedBah, I *knew* I'd seen an issue about it, but failed to find it.
Comment #5
Grayside commentedApplied the patch and tried it various ways. I'm not seeing any change in behavior.
Comment #6
hefox commentedMake sure the field exists in the database; the old feature may need to be reverted. I tested this just now with openpublish and node-openpublish_article-field_op_caption
Comment #7
kristen polComment #8
mpotter commentedThis definitely seems to fix the situation in #1966062: Updating from older version to beta2 doesn't auto-select fields where field_instance and field_base are not selected when the feature doesn't export the content type. Doing some more testing, but this is getting close.
Comment #9
mpotter commentedOK, this patch is working well for me in my testing. Committed this to 156ba27. I encourage you to try it if you had missing fields when converting to Features 2.x.
Comment #10.0
(not verified) commentedUpdated issue summary.