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.
MenuLinkContent::baseFieldDefinitions() has a couple $field->setSetting('default_value', $foo).
That doesn't work, 'default_value' is not a field setting, this should use setDefaultValue() instead.
Comment | File | Size | Author |
---|---|---|---|
#4 | interdiff.txt | 1.52 KB | yched |
#4 | 2418117-MenuLinkContent_default_value-4.patch | 1.52 KB | yched |
#1 | 2418117-MenuLinkContent_default_value-1.patch | 1.29 KB | yched |
Comments
Comment #1
yched CreditAttribution: yched commentedPatch
Comment #2
dawehnerAlright :)
Comment #3
yched CreditAttribution: yched commentedComment #4
yched CreditAttribution: yched commentedAdded the one that slipped in #2417423: Re-process the user-entered-paths for custom menu links when there is a menu rebuild
Comment #5
Wim LeersThanks, yched!
Comment #6
BerdirI thought it might be a duplicate of #2417809: link and shortcut have baseFieldDefinition settings that do not do anything: default_value max_length, but that already got in. RTBC +1 :)
Comment #7
webchickCommitted and pushed to 8.0.x. Thanks!
Comment #10
YesCT CreditAttribution: YesCT commentedI'm curious why we couldn't have a test that would have caught this.