Official comment

This thread is closed as the matter was handled in a private support ticket.
The reason for this problem was due to a bug in our 5.3.0 version and it will be resolved in the 5.3.1 release.
Regards,
Mike Rettew
Mag+ Support Team
Comment actions