Title: Published and Modified date corrupted
Last modified: August 10, 2026

---

# Published and Modified date corrupted

 *  Resolved [worklumo](https://wordpress.org/support/users/worklumo/)
 * (@worklumo)
 * [3 weeks, 4 days ago](https://wordpress.org/support/topic/published-and-modified-date-corrupted/)
 * Description: When a scheduled post is published automatically via WordPress Cron,
   the llms.txt file updates with corrupted dates (-0001-11-30) for Published and
   Modified fields. Clicking “Delete and recreate” in the plugin settings temporarily
   fixes existing posts, but the issue recurs on the next scheduled publication.
 * Expected Behavior: Publication and modification fields should display the actual
   date (YYYY-MM-DD) even during automated cron executions.
    -  This topic was modified 3 weeks, 4 days ago by [worklumo](https://wordpress.org/support/users/worklumo/).

Viewing 3 replies - 1 through 3 (of 3 total)

 *  Plugin Author [Ryan Howard](https://wordpress.org/support/users/ryhowa/)
 * (@ryhowa)
 * [3 weeks, 3 days ago](https://wordpress.org/support/topic/published-and-modified-date-corrupted/#post-18990587)
 * Thanks for reporting [@worklumo](https://wordpress.org/support/users/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.
 *  Thread Starter [worklumo](https://wordpress.org/support/users/worklumo/)
 * (@worklumo)
 * [3 weeks, 3 days ago](https://wordpress.org/support/topic/published-and-modified-date-corrupted/#post-18990598)
 * 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!
 *  Plugin Author [Ryan Howard](https://wordpress.org/support/users/ryhowa/)
 * (@ryhowa)
 * [3 weeks, 3 days ago](https://wordpress.org/support/topic/published-and-modified-date-corrupted/#post-18990622)
 * 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.

Viewing 3 replies - 1 through 3 (of 3 total)

You must be [logged in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fwordpress.org%2Fsupport%2Ftopic%2Fpublished-and-modified-date-corrupted%2F%3Foutput_format%3Dmd&locale=en_US)
to reply to this topic.

 * ![](https://ps.w.org/website-llms-txt/assets/icon-256x256.png?rev=3322182)
 * [Website LLMs.txt](https://wordpress.org/plugins/website-llms-txt/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/website-llms-txt/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/website-llms-txt/)
 * [Active Topics](https://wordpress.org/support/plugin/website-llms-txt/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/website-llms-txt/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/website-llms-txt/reviews/)

 * 3 replies
 * 2 participants
 * Last reply from: [Ryan Howard](https://wordpress.org/support/users/ryhowa/)
 * Last activity: [3 weeks, 3 days ago](https://wordpress.org/support/topic/published-and-modified-date-corrupted/#post-18990622)
 * Status: resolved