Once the entity is Publish and unpublish time via a cron run, it updates the publish_on and unpublish_on field, with entity's field value.
Which might not be the exact time when the cron has run, and hence creating a discrepancy in time set for Publish and unpublish time.
This discrepancy, impacts the analytics of number of entities being published/unpublished in a given time frame.
Schedule an entity to be publish at 10:00 AM, and schedule the cron to run at 11:00AM every day.
Let the cron run.
Though the content gets published at 11:00AM, the entity would say that it got published at 10:00AM, which is not correct.
This incorrect data, impacts the analytics of number of entities being published in a given time frame.
Update the publish_on and unpublish_on field with the current timestamp, when the cron invokes publish/unpublish functions.
Patch Schedule Manager.
N/A
N/A
N/A
Closed: duplicate
2.0
Code
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
This feature is now being worked on in ✨ Don't alter 'changed' time Active so closing this one as a duplicate, even though it was older. The proposed patch in #2 modifed the scheduled dates, which is the wrong way round and definitely not what we want to do.
Thank you neerajsingh for raising the issue and starting the patch, even though this is not how we will do it.