- Issue created by @SirClickALot
- 🇬🇧United Kingdom SirClickALot Somerset
Any chance we can get this addressed?
Right now, we are blocked by the issue and have had to remove all uses of the module which is a great shame.
This might also be the right time to release a D11-compliant version too since the time has come to move to D11 ;-)
- Status changed to Fixed
5 months ago 5:42am 28 August 2024 - 🇬🇧United Kingdom SirClickALot Somerset
UPDATE
This turned out to be a error with Field Group which this patch fixes for now so I'm going to close tis issue. - Status changed to Active
5 months ago 8:59am 28 August 2024 - 🇬🇧United Kingdom SirClickALot Somerset
Re-opened after this conversation comment: https://www.drupal.org/project/field_group/issues/3465611#comment-15746950 🐛 Field Group 3.5 WSODs on Drupal 10.3 Needs work
- Status changed to Postponed: needs info
about 2 months ago 10:29am 3 December 2024 - 🇩🇪Germany Antonnavi Berlin
Hello Nick Abbott (sirclickalot),
I just tested latest DEV module version with latest stable Field Group 8.x-3.6 module version. I can not reproduce this issue.
Test again and if this issue still presented - please provide an instruction how to reproduce (including core/modules versions). - 🇬🇧United Kingdom SirClickALot Somerset
Hi @antonnavi,
You're right, I can confirm that whatever was causing this in the past, the combination of Field Group 8.x-3.6 and Field Group Popup 8.x-1.9 all works perfectly well now for me.
Thank you