fedebianchi

No, the error came from a custom post status hook that would have been added externally which was not working. It was already solved