Forums
(@timexpliciet)
2 years, 6 months ago
This ticket is resolved.After another deploy from local to production the bug seems to be fixed.