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

Kimberley_p’s picture

subscribing

sepehr.sadatifar’s picture

subscribing

dawehner’s picture

Project: Views (for Drupal 7) » Date
Version: 7.x-3.3 » 7.x-2.x-dev
Component: Code » Views Argument

This seems to be a feature request for the date module.

PS: There is no reason on earth anymore to "subscribe" to issues.

sepehr.sadatifar’s picture

how silly of my to comment subscribe to my own post which I was 'following' in first place :)
tnx for issue attributes's fixes.

leymannx’s picture

Issue summary: View changes

I'm subscribing anyways. Just to express my strong wish for this feature.

devad’s picture

Title: Contextual filter for 'Content: Created date' in form of timestamp » Contextual filter for 'Content: Created date' an 'Content: Updated date' in form of timestamp

+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.

devad’s picture

Title: Contextual filter for 'Content: Created date' an 'Content: Updated date' in form of timestamp » Contextual filters for 'Content: Created date' and 'Content: Updated date' in form of timestamp
bibo’s picture

I 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..