Closed (fixed)
Project:
Scheduler
Version:
8.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
13 Jan 2017 at 19:37 UTC
Updated:
15 Jul 2017 at 14:45 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
apupiales commentedThe attached patch is a posible solution
Comment #3
jonathan1055 commentedHi apupiales,
From your patch it looks likes your problem is only when the node is being published immediately, that is - when a past date is entered and the config option for dates in the past 'publish immediately' is selected. Is that correct?
Given that we have 'PRE' versions of the events for both of the cron actions, I can see that it might be helpful to also have a 'PRE' event for the immediate action. I had not considered this before, but it makes for a complete set of events.
Thanks for the patch, I will test it. As this is a feature not really a bug I have changed the issue status.
Jonathan
Comment #4
jonathan1055 commentedI have modified the API test to cover the new PRE_PUBLISH_IMMEDIATELY event.
Comment #6
jonathan1055 commentedThanks apupiales. I have credited you on the commit.