When a new node is created, the created timestamp and changed timestamp are not the same. This is because of the function copyFormValuesToEntity in ContentEntityForm.php which copies values only from non-widget fields to the entity when the node is saved. Since 'changed' is a hidden field, even though it has the same timestamp as created until this function is executed , now gets a different time than the created.
I would assume that created and changed times should be the same for new nodes. Thoughts appreciated!
Thanks,
Sukanya
Needs work
10.1 ✨
Used to track the progress of issues reviewed by the Drupal Needs Review Queue Initiative.
It is used to alert the maintainer(s) of a particular core subsystem that an issue significantly impacts their subsystem, and their signoff is needed (see the governance policy draft for more information). Also, if you use this tag, make sure the issue component is set to the correct subsystem. If an issue significantly impacts more than one subsystem, use needs framework manager review instead.
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
This issue is being reviewed by the kind folks in Slack, #needs-review-queue-initiative. We are working to keep the size of Needs Review queue [2700+ issues] to around 400 (1 month or less), following Review a patch or merge request → as a guide.
Tagging for subsystem review to see if this may have been by design?
Can confirm I see the same thing on D10