Thanks for reporting @worklumo
The fix is out now in 8.5.7
When the plugin could not read a post’s date, it was storing an empty value in its cache table, and MySQL turns that into a zero date, which prints as -0001-11-30. It now refuses to store a date it cannot read, and refuses to print one.
After you update, entries still showing the bad date will stop showing it on the next rebuild. The real dates come back the next time each post is saved, or straight away if you run “Delete and recreate” once more.
If a post you schedule after updating still comes out wrong, it would help to know whether that post was created by hand in the editor or by another plugin such as an importer or an auto poster. I have not been able to reproduce this on a stock WordPress, so that would tell me where to look next.
I schedule manually posts! But these posts are auto pushed by external script, using WP API, usind an WP Editor User. Maybe this is the scenario!
Once you’re on 8.5.7 the dates should come back correct rather than just stop being corrupted. The plugin now reads the date straight off the post record when the normal call fails, and that bypasses whatever was interfering.
After you update and rebuild, if the Published and Modified lines show real dates, we’re good. If they come back empty instead, let me know and that would point at the date stored on the posts themselves.
