Closed (fixed)
Project:
Scheduler
Version:
6.x-1.7
Component:
Code
Priority:
Minor
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
25 Aug 2010 at 16:14 UTC
Updated:
10 Oct 2010 at 11:40 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
dolly nyc commentedI'm having the same problem. Nodes are not unpublishing as scheduled.
Comment #2
eric-alexander schaefer commentedI have no idea. If cron is running correctly the node should be unpublished. If the first chance for unpublishing passes without unpublishing (e.g. db connection problem) it should be unpublished at the next run.
Could you please check the logs (/admin/reports/dblog) after a cron run. Are there any errors reported or any other messages regarding the node?
Comment #3
nancydruI haven't seen any errors reported on that node. Other nodes have successfully unpublished since then. I'm going to guess that someone went back in and re-published it after it was unpublished, but that was so long ago that the log is of no use (that's why #893272: Add revision when working a node would be really useful).
Comment #4
eric-alexander schaefer commentedIf the node still contains the unpublish date, it *must* be unpublished at the next cron run. If it is not unpublished, there is something wrong. Can you get me the node-table row of that node?
Comment #5
nancydruHmm, it is unpublished now, but still listed in the Scheduler table:
Node
Scheduler
Comment #6
eric-alexander schaefer commentedNodes that are unpublished keep their unpublish_on date. This happens if a node scheduled for unpublishing are unpublished manually.
What do you think, should the unpublish_on date be cleared on manual unpublishing? Is there a use case for keeping it?
Comment #7
nancydruThe problem that we have at my customer's location is that the admins see that still listed on the "scheduled" page and get worried that something is wrong. I don't think it's so much a matter of the node keeping its dates as it is that the list keeps showing it. But then, that's probably the same table, isn't it? In that case, yes, I would clear it (however, if you consider revisions, I would not create a new revision for that.)
Comment #8
eric-alexander schaefer commentedIt's in the same table. You could edit the node(s) and clear the unpublish_on field.
Comment #9
eric-alexander schaefer commentedNote to self:
cron unpublishing:
- no limit on status=1
- unpublish nodes that are still published (status=1)
- delete
This way all nodes with unpublish_on value are removed from the scheduler table.
We could have the same problem with nodes scheduled for publishing that are published manually...
Comment #10
nancydruThat sounds like a good idea. It also sounds like a simple change to the query should do it.
Comment #11
eric-alexander schaefer commentedPlease test the attached patch
Comment #12
nancydruHopefully tomorrow; I have a busy evening.
Comment #13
eric-alexander schaefer commentedHave you had time to look into this?
Comment #14
nancydruThe patch looks right, but, no, I haven't tried it yet.
Comment #15
eric-alexander schaefer commentedhttp://drupal.org/cvs?commit=427608
Comment #16
nancydruThanks, and I forgot to tell you it worked fine for me.