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.
currently contextual filters for 'Content: Created date' accepts date in various forms (e.g. : CCYYMMDD, YYYYMM, ...) except timestamp, please add timestamp too with ability to accept timestamp range:
1339584000-1339584334
Comments
Comment #1
Kimberley_p CreditAttribution: Kimberley_p commentedsubscribing
Comment #2
sepehr.sadatifar CreditAttribution: sepehr.sadatifar commentedsubscribing
Comment #3
dawehnerThis seems to be a feature request for the date module.
PS: There is no reason on earth anymore to "subscribe" to issues.
Comment #4
sepehr.sadatifar CreditAttribution: sepehr.sadatifar commentedhow silly of my to comment subscribe to my own post which I was 'following' in first place :)
tnx for issue attributes's fixes.
Comment #5
leymannxI'm subscribing anyways. Just to express my strong wish for this feature.
Comment #6
devad CreditAttribution: devad commented+1 My vote for this feature. (Adding 'Content: Updated date' to subject as well)
I would like to be able to pass 'Content: Updated date' timestamp argument to view pane to force Custom cashe to Re-cache view pane if node is updated. I have managed to do that for block view without 'Content: Updated date' timestamp argument as described here: #2559607: Re-Cache view if node is updated. But for view panes having 'Content: Updated date' timestamp would be great.
Comment #7
devad CreditAttribution: devad commentedComment #8
bibo CreditAttribution: bibo commentedI would also really have preferred to simply use a timestamp for views argument, because it makes timezone handling Universally trivial. It'a not too hard to use the argument default with PHP code, but why doesnt this work out of box..