Problem/Motivation

In #3399970: Umami content is all created in the same second we realised that all Umami content is created in the same second, which is not very realistic.

Could we add something like a timestamp offset to default content imports, so that content can be spread out a few hours/days back as it gets imported? Would have to be a special key which then gets applied as an offset to the creation time.

Steps to reproduce

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

Release notes snippet

Comments

catch created an issue. See original summary.

thejimbirch’s picture

Component: recipe system » default content system
phenaproxima’s picture

This, to me, feels more like a contrib thing than a core thing. It would be easy enough to implement using the new PreEntityImportEvent. But I'm not sure this is something core should be in the business of providing; its job is to provide reliable APIs for default content, and this doesn't feel like something that needs to be in our API.

So my inclination here is to close this as a won't fix.

Version: 11.x-dev » main

Drupal core is now using the main branch as the primary development branch. New developments and disruptive changes should now be targeted to the main branch.

Read more in the announcement.