Does the published_date field actually do anything in the mechanics of node retrieval?
From what I can tell it doesn't, and is just a date field to pass around. Would this be better replaced with support for CCK date field?
Does the published_date field actually do anything in the mechanics of node retrieval?
From what I can tell it doesn't, and is just a date field to pass around. Would this be better replaced with support for CCK date field?
Comments
Comment #1
MJH commentedThe published_date can be found in the create-new-node forms and in the view content_distribution_queue as a filter (Content Distribution: Published Date <= now).
I do not really know what it does (all published nodes should have published_date <= now ?!?). All I know is that it was the source for some problems in my case: I had to set the filter to Content Distribution: Published Date <= +2 hours, otherwise the content retriever module didn't find the new nodes that were ready to be distributed. There seems to be a problem with the time zone somewhere (I am on GMT+2).
Comment #2
joachim commentedHuh -- I'd never even noticed it there as a filter.
Still -- that's nothing that couldn't be done with CCK date and a bit of code; though I don't know why we're saving it on the Retriever site.
Comment #3
luketsimmonsHi MJH and joachim,
I had a similar thought about the Content Distribution Published Date field, but then realised that it is useful to schedule a node to publish later on, similar to how Scheduler (http://drupal.org/project/scheduler) works but with regards to when a node can be retrieved, if that is how you have set up your view with the value as a filter.
I found this useful if you have Content Distribution running with cron, as you can set up nodes to be retrieved later on and not just when the next cron job runs (or just when the content is manually retrieved).
I also had issues with this field in terms of the time that was being set and it appears to add an hour every time the node is re-saved. Not sure why though? The value that is set does use the date_default_timezone_get(), which gets the timezone set in PHP (i.e. in php.ini) and not the Drupal Date/Time Settings value, although not sure if Drupal sets a local PHP value itself?
Thanks,
Luke
Comment #4
joachim commentedThis should be farmed out to its own submodule, or even removed if the original client this was developed for doesn't need it any more.