isp support have now resolved the issue, this was their reply for reference:
This is an sql-mode issue, the mode defines what SQL syntax should be supported and what kind of data validation should be performed. In this situation, what is happening is that the script is attempting to insert or update a row with the integer entry taking on either the default value (e.g., of 0 or NULL) or the next AUTO_INCREMENT value.
But MySQL is not interpreting this action as valid due to its SQL_MODE being in STRICT mode, so we have disabled it and restarted the MySQL service.
they also rolled it back to MySQL 5.55 (from 5.6)