- Issue created by @abhinesh
- Issue was unassigned.
- Status changed to Needs review
over 1 year ago 2:50pm 9 June 2023 - Open on Drupal.org →Core: 9.5.5 + Environment: PHP 7.4 & MySQL 5.7last update
over 1 year ago Waiting for branch to pass - 🇺🇸United States DamienMcKenna NH, USA
That's an oddity - why would the value be stored in a nested array?
BTW when you upload a patch or create a merge request please set the status to "needs review", that lets others know there's something to look at and triggers the automated test system. Also, please set the "Assigned" field to "Unassigned" when you're finished your work so that others know you're done. Thank you.
- Open on Drupal.org →Core: 9.5.5 + Environment: PHP 7.4 & MySQL 5.7last update
11 months ago Waiting for branch to pass - 🇺🇸United States DamienMcKenna NH, USA
We've run into this problem on a site I have access to, so I can do some debugging to see where the problem comes from.
- Assigned to DamienMcKenna
- Issue was unassigned.
- Status changed to RTBC
11 months ago 7:27pm 17 November 2023 - 🇺🇸United States DamienMcKenna NH, USA
While I think it'd be better to fix this with an update script to correct the configuration, and update the logic on the form to remove empty values from the array, I think this is a good safety fix and resolved the problem for me.
The last submitted patch, 6: gatsby-3365519-6.patch, failed testing. View results →