This is something we're running into in a big site with lots of imports and other actions happening outside of manual editing of nodes. Somehow nodes can get into a state which saves a new revision, but does not fix the current state it is in. So next cron-run, it saves another revision with the incorrect state.
When there's a failure, the scheduler-hooks does not revert the state back to the previous state like the scheduler-module does with the timestamp-field.
Create a node which is published and has an unpublish-on and -state set. Set the node to that state elsewhere (could be batch update in a view, or manually in database) and run the scheduler:cron.
The node now has an unpublish-on value but no unpublish_state value.
Move the code that clears out the state-value inside the try/catch inside the hooks and add a case-check for then it should (un)publish to the current state.
-
-
-
-
Active
2.0
Code
Thanks @spadxiii for the MR.
Can you check what the behavior is on the 3.x branch, and open a new MR there. When complete, we can use MR49 for back-porting to 2.x