I just stumbled upon this as well. As a quick fix have completely removed the check whether the unpublish field is in the past, because I don't see the point of it.
Without the check everything works fine. Also if the date is in the past and the node is published it will be unpublished by the cronjob like it should.So in my opinion this check should be completely removed, or made optional just like with the publish date field.
- 🇬🇧United Kingdom jonathan1055
Hi Paul Dudink
completely removed the check whether the unpublish field is in the past,
I think you may have mis-read the details of this issue. The problem is not the validation with unpublish date , it is about the unpublish date not being earlier than the publish date.
You may have a valid reason for wanting that check removed, but it is not what this issue is about. There is an issue #3122973: Allow unpublish_on dates in the past → which might be relevent and you are welcome to post there instead.