Hi.

I have not been able to reproduce the issue.

I have created 2 articles, I have visited only one of them. In this way I have one article with hits = 0 and another one with hits > 0.

In both cases, when I used "Save as Copy" a new article was created, and the message "Article saved." appeared.

I have tried in Chrome and Firefox.

I have tested this item ✅ successfully on a5588af

To reproduce:

Edit an article.
Go to Publishing tab.
Use browser's inspector to change the value of Hits to empty string.
Click Save button.

I have tested this item ✅ successfully on a5588af

Followed the procedure given by BertaOctech

RTC

Indeed this is the fastest way to reproduce the error.
I have only described in which case it occurred on my side ... it is not systematic as I specified.

I made the most obvious correction but for me there is clearly a problem in the form validation process on the server side.
Since the field is defined as an integer, even without a default value, it should be initialized to 0 no matter what, '' is not an integer.

Maybe there is an hidden error in the integer definition filter.

I think if this happens for this field, then all forms with none initialized integer should be reviewed.

This error is no need to be reproduce for this patch but...

I checked the category hits field and the default to 0 is present.

If you remove the default of the field 'hits' (category or article) and follow the @Quy instruction, you will get the error.
You can also enter a string instead of an integer and the string will be convert to empty string.
Incorrect integer value: '' for column 'hits' at row 1

This kind of error must not happen on the server side validation because everybody can make a form like he want, specially with the API

The form validation does not make its job if a value is set to string for an integer with no default, the default should be 0 on all case or the form is not valid

Thanks!