Hi @thefoyfoy,
We take full responsibility for it, and I’m sincerely sorry for the disruption it caused you.
For transparency: we’ve released 7.5.3.1, which fixes the issue, and we’re reviewing our release/QA process so that a mistake like this doesn’t reach production again.
I understand if you’ve already moved on, but if you ever decide to give Complianz another try, we’d be glad to have you back. Either way, thank you for the honest feedback, it’s fair, and we’re taking it seriously.
Best regards,
Antonio
I updated my site this morning, and it caused a fatal site error. I then got things working again and noticed that another update had been released. I tried it, and it caused the same error.
