It looks like the ContentService.Published/Publishing events are misnomers since they don't fire when content is published using a Scheduled Publish ("Publish at"). This is a major issue for us because there is logic that needs to run regardless of how a piece of content is published. Am I mistaken or is there another way to hook into this process?
Not sure this will completely answer your question, but thought I'd provide some thoughts.
Umbraco is simply a website with built in functionality for publishing. What I mean by saying that is that the website needs to be "awake" for the publishing functionality to work. So typically most sites, the application pool will go to sleep after a period of inactivity and therefore the publishing will only occur when the site is next accessed.
So if you have critical events that need to occur then for peace of mind it might prove a better option to integrate server based events, or third party scheduling for the critical tasks.
Alternatively if you have the ability, then set your app pool to not go to sleep to ensure any publishing functionality works.
Does Umbraco have a Scheduled Publish event or a way to hook into this process?
It looks like the ContentService.Published/Publishing events are misnomers since they don't fire when content is published using a Scheduled Publish ("Publish at"). This is a major issue for us because there is logic that needs to run regardless of how a piece of content is published. Am I mistaken or is there another way to hook into this process?
Kind Regards, Sahid Miller
Hi Sahid
Not sure this will completely answer your question, but thought I'd provide some thoughts.
Umbraco is simply a website with built in functionality for publishing. What I mean by saying that is that the website needs to be "awake" for the publishing functionality to work. So typically most sites, the application pool will go to sleep after a period of inactivity and therefore the publishing will only occur when the site is next accessed.
So if you have critical events that need to occur then for peace of mind it might prove a better option to integrate server based events, or third party scheduling for the critical tasks.
Alternatively if you have the ability, then set your app pool to not go to sleep to ensure any publishing functionality works.
Hope this helps in some way
Nigel
Hi Sahid
Another way is to write own publisher, you can use the task schedule package for scheduling and write own method that will publish nodes
https://our.umbraco.com/projects/backoffice-extensions/url-task-scheduler-for-v7/
Thanks,
Alex
Hi Sahid
Share with the community how did you manage to solve the issue?
is working on a reply...