This is a problem of having two buttons in one form. The field is required, but
only needs to be required for one of the buttons. But we fill in a date
automatically for the user, so it's almost never a problem. This edge case only
happens if the user first deletes a value from one of the datetime fields, then
changes his mind and hits publish now.
I'm resolving this, but it's good that you mentioned it, because in the future
someone may find the issue and thus this explanation.
This is a problem of having two buttons in one form. The field is required, but
only needs to be required for one of the buttons. But we fill in a date
automatically for the user, so it's almost never a problem. This edge case only
happens if the user first deletes a value from one of the datetime fields, then
changes his mind and hits publish now.
I'm resolving this, but it's good that you mentioned it, because in the future
someone may find the issue and thus this explanation.