It turns out this has likely already been fixed in the 1.25 branch (by me) but the fixes are awaiting a 1.25.7 release.
Keeping the ticket open to track the issue and ensure that it's definitely dealt with.
It turns out this has likely already been fixed in the 1.25 branch (by me) but the fixes are awaiting a 1.25.7 release.
Keeping the ticket open to track the issue and ensure that it's definitely dealt with.