Delayed publication [#1862904]

This module adds two fields to nodes of a chosen type or types (a configuration page allows you to choose which types of node are impacted).

The first one (field_real_published) is a simple date field which contains the real published date of the node. It can be modified by a user. This date will be different from the created date (provided by node module).
The second one (field_delayed_publication) is a delayed publication date. You can set it in order to publish the node later. A hook_cron (and its queue) will publish it automatically and set field_real_published with the field_delayed_publication value.
These two fields are grouped in a vertical tab (provided by field_group module).

Delayed publication also provides a bulk update page in order to set field_real_published for all previous nodes, and a view page which list all nodes awaiting publication. On this page, you can select nodes for which you want to force publication (provided by views_bulk_operations).

So this module depends on date, field_group and views_bulk_operations

Project page : http://drupal.org/sandbox/OwilliwO/1858190
Git repository : git clone --recursive --branch master git.drupal.org/sandbox/OwilliwO/1858190.git delayed_publication
Version : Drupal 7.x

Comments

Comment #1

mohs3n71 commented 10 December 2012 at 15:45

Status:

Needs review

» Needs work

hi ,
1 ) it seems that you are working in master branch , you should make a new branch for your module and work on it , some helpful links :
http://drupal.org/node/1127732
http://drupal.org/node/1015226
http://drupal.org/node/1066342
2 ) the README.txt file is missing , add a README file
3 ) automatic review found many problems with your code : http://ventral.org/pareview/httpgitdrupalorgsandboxowilliwo1858190git

please see drupal codding standards : http://drupal.org/node/318

Comment #2

lolandese commented 11 December 2012 at 13:42

Hi,

Can you explain the differences with http://drupal.org/project/scheduler?

Thanks.

Comment #3

owilliwo

Montreal

commented 11 December 2012 at 15:36

Status:

Needs work

» Needs review

OK thanks, i didn't know about PAReview.

Two branches, master and dev.
Added a README file
Review fully OK : http://ventral.org/pareview/httpgitdrupalorgsandboxowilliwo1858190git

Comment #4

owilliwo

Montreal

commented 11 December 2012 at 15:40

My module add a real published field date.

Drupal provide $entity->created, which contains creation date, not publication date.

You create a node, but you choose not to publish it immediatly on March 1st for example.
If you publish it on March 2nd, $node->created will be set to March 1st, although real_published_date will be set to March 2nd.

Comment #5

owilliwo

Montreal

commented 12 December 2012 at 16:23

Given that $node->created may be modified manually by a user (if they have the correct permissions), and given that the Scheduler module functions in exactly the same manner as my module (in fact Scheduler does more things than mine), it seems that field_real_publised_date is no longer useful, as my module...

Comment #6

lolandese commented 12 December 2012 at 20:55

With almost 20.000 modules, finding existing modules and monitoring new ones has become my daily 20 minute routine leading to ever expanding Google docs. One of my docs is keeping track of functionality I don't find, mostly related to existing modules (possible patches) with an occasional "stand-alone" functionality (possible modules). Of this last list often items get deleted because later I run into a module (or combination) that covers it anyway. So far I only found one functionality that was unique, was worth to write a module for and within my capabilities. In fact, most of my humble amount of contributing (every little bit helps) consists of patching, writing (documentation) and reviewing.

I hope this is of some consolation.

Consider changing the status of this issue.

Thanks.