Comments on: Drupal Published Date equals Effective Date fix

By: liquidcms

liquidcms — Thu, 10 Sep 2009 04:44:18 +0000

ok, don’t whine if ya ain’t gonna fix it…

sadly only for Drupal 5 right now; but took a look at this and made a new module called Published which adds a published field (via a table) into the node object.

admin configurable to let it reset if node goes back to unpublished and then to published again, plus can me manually overriden by user with perm to edit (same as std Authored date field (which is really $node->created).

i’ll try to get this up on d.org as an official project sometime this week.

By: liquidcns

liquidcns — Wed, 09 Sep 2009 17:28:19 +0000

Ideally i think a module with a custom table for node published timestamp would be a more generic solution (or add it to core). The reason i say this is we have a very similar requirement in that we need to list items based on when they were published; and not have them show at top of lists with a simple typo fix – BUT, we still need to preserve created time as we use it for billing purposes.

By: Kwint

Kwint — Sat, 25 Jul 2009 11:42:07 +0000

To bad the workflow module doesn’t hook into the rules module..

But I love this workaround. Have a workflow with 8 states setup, with actions that are triggered on a workflow change. Based on the triggered action a rule (yours! changes (or doesn’t) the creation time!

Thanks again for this post, this thing was really bugging me since we do a lot of “timed publish”, “reviewing” and “updating” on our site.

By: Tadej Gregorcic

Tadej Gregorcic — Fri, 08 May 2009 07:40:04 +0000

not unchanged actually equals “updated”, and this is a choice because on our site, content gets taken offline and back online and we don’t want it to appear in “new items” if it was unchanged.

By: rudders

rudders — Fri, 08 May 2009 06:50:27 +0000

This is very cool but way do I need the “NOT unchanged content is published rule”??