Forums
(@webzaken)
1 year, 6 months ago
We found out the following: This issue only happened since version 1.5.0 (and in version 1.5.1 as well). We just switched back to version 1.4.12 without any issues.