WordPress.org

Make WordPress Core

Changes between Initial Version and Version 1 of Ticket #49879, comment 2


Ignore:
Timestamp:
04/13/2020 05:34:34 AM (20 months ago)
Author:
Rarst
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #49879, comment 2

    initial v1  
    33The one specific 1901 limit you observe to is caused by a lowest possible negative integer timestamp on 32-bit PHP. It should go away on 64-bit PHP installation, but you would still hit ''other'' limits.
    44
    5 Effectively WP isn’t engineered for working with backdated historical posts. I think it's a valid and interesting use case, but also a very edge case one.
     5Effectively WP isn’t engineered for working with backdated historical posts. I think it's a valid and interesting use case, but also a very niche one.
    66
    7 My personal recommendation, for a private site, is too store historical dates as custom fields and handle them with your own code.
     7My personal recommendation, for a private site, is to store historical dates as custom fields and handle them with your own code.
    88
    99At the moment there is no explicit intention to support or not support them in core.