- Issue created by @malcomio
- last update
over 1 year ago 29,459 pass - @malcomio opened merge request.
- Status changed to Needs review
over 1 year ago 5:53am 10 August 2023 - π¬π§United Kingdom malcomio
The warning can be prevented with the change in https://git.drupalcode.org/project/drupal/-/merge_requests/4574, but I don't know if there are any other effects of this field not being set.
I suspect that the proper fix may be in update hooks somewhere.
- Status changed to Needs work
over 1 year ago 5:29pm 10 August 2023 - πΊπΈUnited States smustgrave
Thank you for reporting
So typically with these kind of issues we need to determine why this key isn't set. Could be masking a large problem.
- π¬π§United Kingdom stefank
Hi all,
Attaching a patch for D10 as well, in case anyone also needs it. Should apply cleanly using composer.
- First commit to issue fork.
- π¬π§United Kingdom oily Greater London
Created new 11.x branch, hid old branch.
- π¬π§United Kingdom oily Greater London
I grepped 'description_field_required' in core and it does not exist. However the code in the related issue #2320877 adds a key named 'description_field_required'.
@malcomio, Is it possible that whenever you encountered the warning message in the issue description that the site contained code that added that key. e.g. in a contributed module, composer patch or custom module?
Logically the only other way (I can think of) that that key could appear purely as a result of core code would be if it is dynamically generated eg by concatenating a string with a string from a variable. Then grepping 'description_field_required' would return nothing.
If the key is created outiside core eg in a contrib module then this is not a core issue and it can safely be closed.