This problem may be similar to some other creation date related issues I've seen posted.

I've got a view filtering nodes by Post Date, and also displaying the Post Date field. I create a node today, save it, and then go back and change the Authored On date to sometime in the past. The view displays my custom date correctly in the content, but still filters the node as if it were created today. Clearing the views cache and the site cache has no effect.

The database shows that the node's created date was updated correctly, so suspecting a caching issue, I tried creating a new node and editing the Authored On date before saving for the first time. Sure enough, this was a successful workaround, but I'd still like to solve this so users are free to edit the field.

Comments

bethhauck’s picture

Anybody have any thoughts on this? My current workaround is the Date module, but it would be nice if nodes didn't have to have two separate date fields on them (ie. the "real" authoring information and the separate Date field).

Dave Reid’s picture

Status: Active » Postponed (maintainer needs more info)

This really has nothing to do with token.module from what I can tell? Is this a Views issue?

Dave Reid’s picture

Status: Postponed (maintainer needs more info) » Fixed

Status: Fixed » Closed (fixed)

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