Ok, thanks, yep, hm, I do think that was made, but they might just have missed it. I'll try for myself.

Hi Jonas,

This mechanism is build on top of the internal scheduler, should work oob if your site is running... So make sure the site is pinged once in a while.

Cheers,

Richard

Checklist:

- Server date/time
- Don't click publish when you schedule a document, click save.

Cheers,

Kenny

Also, the scheduler doesn't start until 10 minutes after the appPool starts up.

While we're at it, any recommendations/how to on scheduled publishing from the API?

Thanks,
Harald

You could write a user control which publishes certain pages and then that usercontrol is called from the scheduled tasks. This thread explains in the beginning how to create a scheduled task in umbraco:

http://forum.umbraco.org/yaf_postst8032_Scheduled-Job-Problem.aspx

However, you will encounter the same limitations in that if umbraco has been inactive for a while then someone hits the site the timers are reloaded. Ismail in this thread says that you could schedule a task on the windows server box:

http://forum.umbraco.org/yaf_postst5242_Are-Umbraco-scheduled-tasks-reliable.aspx

Now I remembered to go back and check this, it did work, even with time. Nice!

Thanks 2 all

Now I think I found out what happened here,

the user probably entered the date without time "2010-01-01". If I try that, the date is not being saved att all. When I add time also "2010-01-01 00:00" it is saved alright. Using the date chooser also works fine.

I would like to either add a help text next to publish date (but I can not do that, can I?) or add an event handler to take care of date without time. Possible?

This seems to be something that should be taken care of oob, right? I mean - it shoud be possible to add a date only. Can it be a formatting issue? We enter date in the format yyyy-MM-dd.

Cheers

Jonas

It might be related to the thread culture. I looked at the source once, and there is a lot(!) og .Parse stuff going on, so maybe it cannot parse it without time.

Question is if an Eventhandler would help, since the Document object has a DateTime object representing the value. And if Umbraco cannot parse it into a DateTime, well then it will not help, since you cannot access it.

Thanks for having a look Morten, I find this prb in more installations, would you suggest I add it as an issue in codeplex?

I think adding an issue would be fine. Or event better, finding the line of code in question, and submitting at patch with a better parser :-)

is working on a reply...