If I create a new node of a content type with scheduling turned on and leave "Publish on" and "Unpublish on" blank then save it, the scheduler database will have an entry for this node rather than blank entries. If I pull up the node in Content Management, the fields will be filled in with either a date from yesterday or today, but always in the past. Therefore it will be unpublished when cron runs. if I blank out the fields, save the database entry is not blanked or removed and pulling up the node entry it will be filled in again.

Thanks.

Comments

AjK’s picture

I think this is related to another issue in the issue queue but not quite sure yet (so not marking duplicate yet).

However, there's clearly a bug in the "on submit" handler that's causing these problems. I've temp removed the version 6 download for the time being as it's a) got an obvious problem and b) will just result in more issues being created that I think are related (one and the same underlying reason).

dpearcemn’s picture

Let me know if you want me to test it when you get to it.

Thanks!

temmermon’s picture

Would be finde to have a 6.x-dev version published anyway. If you warn the users with fat letters, you won´t find more issues, I believe.

quattrosoli’s picture

What are the prospects for the latest working version of Scheduler for Drupal 6.x? Setting automatic node publication is a critical component of a website I'm building, and if an update of the module is imminent, I'll wait. Otherwise I'll find another solution.

Or, are there tweaks of the Drupal 6.x core that might result in something comparable? The combination of Triggers and Actions appears to hold some promise, but doesn't seem to enable node publication scheduling right now.

Thanks.

eric-alexander schaefer’s picture

Expect a D6-Version this week.

quattrosoli’s picture

Thanks! That would be great!

eric-alexander schaefer’s picture

Status: Active » Fixed

Fixed in 6.x-1.2rc1

eric-alexander schaefer’s picture

Status: Fixed » Closed (fixed)