Currently emitted energy is recorded at the time of occurrence. In the 8.x code I see uncommented code that suggests that the time stamp at which an energy is emitted could be set to an other value, for example in the past or in the future.

@tcmug, What is the use case you had in mind when you wrote this code?

CommentFileSizeAuthor
#3 radioactivity-emission-time-2677688-3.patch1.62 KBSutharsan
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Sutharsan created an issue. See original summary.

tcmug’s picture

tcmug CreditAttribution: tcmug commented

IIRC it was for finer control of the granularity - now everything is tied to when cron is run. It may be beneficial for a site to run cron once per day and still let the decay be natural.

Best place to handle this would be the REST endpoint script and not the widget itself as the timestamp will be cached.

Sutharsan’s picture

Sutharsan CreditAttribution: Sutharsan commented
Status: Active » Reviewed & tested by the community
FileSize
radioactivity-emission-time-2677688-3.patch1.62 KB

Remove references to this issue.
Cleaning-up unused code.
Restore request time in entity query in RadioactivityProcessor::updateField.

Sutharsan’s picture

Sutharsan CreditAttribution: Sutharsan commented
Status: Reviewed & tested by the community » Fixed

  • Sutharsan committed fc8da79 on 8.x-3.x 
    Issue #2677688 by Sutharsan: Use case for alternative emission time

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.