Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.I generated 500 nodes of content using Devel Generate after checking boxes for all content types. I selected "1 month ago" in response to the question "How far back in time should the nodes be dated?" All 500 items were stamped with the current date and time as if I had answered "Now". I am running Drupal 8.4.4 on a drupalvm local host. Both Devel and Devel Generate modules are enabled.
I feel reluctant to report this as a bug as I am using Devel Generate for the first time and may just have missed some documentation or a clue somewhere but I have spent over an hour searching for answers and did not locate any similar issues. The purpose of the date and time stamping seems fairly obvious so I assume I should see articles etc. with dates spread out over the last month and not all within the last minute or two. My apologies if I'm overlooking something.
Comments
Comment #2
jonathan1055 CreditAttribution: jonathan1055 as a volunteer commentedHi tedf,
Thanks for reporting this. After generating the content, what date were you looking at for the timestamp? On the /admin/content page it shows the 'updated' date, and you are correct that these are all the current time of generation. However, if you edit one of the items you will see in 'Authoring Information' that the 'Authored On' is set randomly back over the period selected.
I agree that this can be confusing as the 'updated' date could (and possibly should) be set to match the back-dated creation date.
Things have moved on since you reported this at 8.x-1.x so can you try again at 8.x-3.x and confirm if you see the same as I do. Then we can work on a solution if one is required.