This is the first time I've tried the "Remove at" property under "Properties" but as far as I can see nothing happens when I set a date and a time for a certain page? The page in question is still published after the "Remove at" date and time has passed. I haven't tried this using whole days though, I just set the remove at date fifteen minutes into the future.
The web server is on the same timezone as my desktop computer where I do the settings and I've checked that we have the same time settings (give or take a few seconds).
What happens is that when umbraco starts, it sets up a timer. That timer runs every minute, but the first run happens 10 minutes after umbraco has started. So if you are on a laptop, your application pool might not live for 10 minutes, causing the (un)publishing service to never run.
For testing I changed to timers in the source, and compiled my own version to start running the publishingservice right after the app has started.
Look into a ping service that pings your site say every 9 minutes or so, because I think I remember someone saying if the site is idle for 10 or 11 minutes IIS does something to save resources and I think this screws things up with the timer?? Need someone to back that up though as I may be wrong :S
Remove at - does it work and if so, how?
Hi!
This is the first time I've tried the "Remove at" property under "Properties" but as far as I can see nothing happens when I set a date and a time for a certain page? The page in question is still published after the "Remove at" date and time has passed. I haven't tried this using whole days though, I just set the remove at date fifteen minutes into the future.
The web server is on the same timezone as my desktop computer where I do the settings and I've checked that we have the same time settings (give or take a few seconds).
Or is this the wrong way to use it?
Thanks!
/Thomas Kahn
I am using it, and it is working well here.
What happens is that when umbraco starts, it sets up a timer. That timer runs every minute, but the first run happens 10 minutes after umbraco has started. So if you are on a laptop, your application pool might not live for 10 minutes, causing the (un)publishing service to never run.
For testing I changed to timers in the source, and compiled my own version to start running the publishingservice right after the app has started.
Hi Morten!
It should work for me then. The site is not on a laptop but a big Windows 2008 server and the site has been up and running for days. Strange...
/Thomas
Look into a ping service that pings your site say every 9 minutes or so, because I think I remember someone saying if the site is idle for 10 or 11 minutes IIS does something to save resources and I think this screws things up with the timer?? Need someone to back that up though as I may be wrong :S
Also, check the umbraco log table. There are some big try/catch blocks, but they should log any errors to the db.
is working on a reply...
This forum is in read-only mode while we transition to the new forum.
You can continue this topic on the new forum by tapping the "Continue discussion" link below.