Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.When trying to edit field storage settings for a field with data, the error message appears:
There is data for this field in the database. The field settings can no longer be changed.
However, the form can still be submitted - there should be some validation to prevent this, or the form should be disabled.
| Comment | File | Size | Author |
|---|---|---|---|
| #1 | field_ui-storage-2349601-1.patch | 6.55 KB | malcomio |
Comments
Comment #1
malcomio CreditAttribution: malcomio commentedComment #3
swentel CreditAttribution: swentel commentedActually some field types will throw errors (IIRC options will do) - but you're right, this is a really confusing screen.
#1854990: Warning about global fields needs better words (follow-up to Adding new fields leads to a confusing "Field settings" form) is a related issue and I know there's another one in the queue that tries to deal with changing the cardinality because that will actually lead to data loss - I'll try to look it up as soon as possible.
Comment #4
swentel CreditAttribution: swentel commentedAlso related - #1266748: Changing cardinality lower than highest existing delta causes data loss upon save
Comment #5
mgiffordThis still a concern in D8? Unassigned issue too.
Comment #18
LendudeI think it is well established behaviour now that you can actually still change these settings, and I would be against changing this behaviour.
The message is misleading though, and it should be changed, and we have #1854990: Warning about global fields needs better words (follow-up to Adding new fields leads to a confusing "Field settings" form) for that.
So I'm going to close this, but feel free to re-open this if you think we still need to change something here.