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.
Problem/Motivation
Right now, the migrated field group settings are changed when the corresponding entity (form/view) display configuration entity is re-saved on Field UI.
Proposed resolution
Migrate well-prepared field group settings that do not change when the entity (form/view) display is re-saved.
Remaining tasks
* Create a patch
* Add a functional test which ensures that field group settings do not change.
* Update the test fixture with proper test data (e.g. a tab should have a *tabs parent etc.)
User interface changes
API changes
Data model changes
Comment | File | Size | Author |
---|---|---|---|
#20 | field_group-ensure_migrated_config_isnt_changed_on_form_resave-3177722-20.patch | 33.16 KB | omkar.podey |
Comments
Comment #2
huzookaComment #3
huzookaComment #4
Wim Leers🤔 Is this what causes the field group configuration that gets added to the
Entity(View|Form)Display
to be restructured/reformatted to ensure that subsequent saves via the UI do not cause things to change anymore?IOW, is this what you meant by
?
🤔 Why are these obsolete? An
@see
would be helpful here!{@inheritdoc}
🤓
👍 Aha, so this first checks the configuration of multiple view displays and form displays post-migration, then navigates to the admin UI for each, resaves it through the UI, and verifies they do not get overwritten.
Comment #5
huzookaComment #6
huzookaRe #4:
Comment #7
Wim Leers🚢
Comment #8
nils.destoop CreditAttribution: nils.destoop as a volunteer and at iO commentedEverything seems to be ok. I had to re-apply the patch, just a quick check if tests are still ok:
Comment #9
Neslee Canil Pinto@nils.destoop the tests are failing at #8 , setting to NW.
Comment #10
huzookaTest should be updated for #2998778: Make responsiveness for vertical/horizontal tabs configurable
Comment #11
huzookaBTW, why this
width_breakpoint
setting is not in the default configuration? (Or why it is not nullable?..)Comment #12
omkar.podey CreditAttribution: omkar.podey at Acquia commentedChecking kernel tests , functional test results with fixes.
Comment #13
omkar.podey CreditAttribution: omkar.podey at Acquia commentedUpdated and making some values default to pass assertions.
Comment #14
omkar.podey CreditAttribution: omkar.podey at Acquia commentedFixed coding standard errors.
Comment #15
omkar.podey CreditAttribution: omkar.podey at Acquia commentedComment #16
huzookaI have only two nits, #1 and #2:
Unneeded trailing whitespace. Although I would not touch this comment (because it is not related to the task),
if you want to do it anyway, let's break it before 'array.'.
See point #1 above. The char limit is 80.
👍 These are the only major differences - the default value of
show_empty_fields
wasn't added to the default context settings of Tab and Tabs in #1482958: Allow field_group with empty fields to be displayed via setting (4 month ago).Comment #17
omkar.podey CreditAttribution: omkar.podey at Acquia commentedRemoved whitespaces.
Comment #18
omkar.podey CreditAttribution: omkar.podey at Acquia commentedComment #19
omkar.podey CreditAttribution: omkar.podey at Acquia commentedfixed comments.
Comment #20
omkar.podey CreditAttribution: omkar.podey at Acquia commentedFixing comments again.
Comment #21
huzooka#20 is RTBC.
Comment #23
nils.destoop CreditAttribution: nils.destoop as a volunteer and at iO commentedThx, this has been committed to dev