Forums
(@mark-young)
2 years, 3 months ago
Hey Jack,
The latest version 3.2.20 should have this fix corrected for you.