To reproduce:

1. create node and publish it manually.
2. edit node, set date to be published on to some time in the past.
3. node is immediately unpublished, and only republished when cron is run.

This is a problem, since there may be edits to an already published node. The work-around is to clear that "Published on" date field, but it's not very intuitive or user friendly.

Instead, on submit the module should check to see if the scheduled date is in the past, and if it is, immediately publish it, or leave it published if it already is published.

CommentFileSizeAuthor
#3 scheduler-module-190860-3.patch959 bytesskiminki

Comments

Leeteq’s picture

Leeteq commented

Subscribing.

AjK’s picture

AjK commented
Version: 5.x-1.8 » 5.x-1.11
Status: Active » Needs review

Please test this patch and if it works for you I'll do a release (Note this patch is against release version DRUPAL-5--1-11, version of this issue altered to reflect that).

skiminki’s picture

skiminki commented
StatusFileSize
new scheduler-module-190860-3.patch959 bytes

Ok, the patch by AjK (comment 2) almost worked for me. However, the timezone shift must be adjusted, because time() returns unix timestamp in GMT and publish_on is localized (GMT + timezone seconds). Here's an additional patch.

skiminki’s picture

skiminki commented
Status: Needs review » Fixed

Committed scheduler-module-190860-3.patch in CVS. http://drupal.org/cvs?commit=112682

I'm going to mark this fixed. Please reopen this issue (or submit a new one) if the problem persists.

skiminki’s picture

skiminki commented
Status: Fixed » Closed (fixed)

In 5.x-1.13.