Hi Mikael

This should be working without any problems in 4.0.3 out of the box as usual.

Can you provide us with anymore information?

/Jan

I just realized that the server was using PM / AM time and the Umbraco user is using danish settings (24 hour time) so this might be the problem.

I will know a little later.

Nope that was not the solution.

This is a fresh install of 4.0.3 on a Windsows 2008 server.

I installed the Creative web starter package.

If i edit a page and set the publish date Time to be today, and a few minutes from now, the page is not published at the set time.

What else can i have done wrong ?

After a lot of hairpulling and searching i still haven't figured out why my pages can't be set to publish at a specific time.

Are there any pitfalss i have overlooked ?

You have to publish the page for it to be publicly accessible at the given time. The system unfortunately does not run a "timer" mechanism where your page changes from "unpublished" to "published" at the specified time - to do so would involve us creating some kind of background Windows service to poll every minute or second and update the database accordingly, and we ain't doing that (although if you want to have a go you're more than welcome to).

Hit the "Save and publish" button and try and access the page via it's given URL. It should be unavailable until the time specified in "Publish at".

Hope this helps.

Benjamin

Benjamin> If you publish the page it _will_ be accessible no matter what the Publish At is set to.

Mikael> The timer that starts the publishing runs in the background and will not start untill 10 minutes after the app pool has started up. So you might need to keep your app pool alive for a while to see the publishing working.

Sometimes the publishing will crash because it relies on the httpcontext, which might not be available at the given time.

Hmm just double checked eventlogs and Umbraco log and nothing special there as far as i can see.

Its Umbraco 4.0.3 running on Windows 2008 R2 (64 bit) server.

My 4.0.2.1 installation on my Vista labptop works perfrctly, publishing pages at the times i set.

Could someone with a 4.0.3 install of Umbraco please help me confirm that setting a publish date/time some time in the future and then saving the page, actually results in the page being published. Just so i can rule out a problem in Umbraco, and concentrate on my server.

I don't have acces to any other 4.0.3 installations right now so it would be a big help for me.

Thanks

Mikael

Hi Mikael,

I just tried it, it doesn't publish on my server either. Can you check the umbracoLog table? In my table, there's an error listed that it could not publish the page.

HTH,

Peter

I just test on my server with a 4.0.3 installation/Windows 2008 Server and it worked for me. Is it not even working when you set it 1 or 2 minutes in advance because your app pool would not have closed since I am guessing you would have to save it in order to update the Publish at time. Make sure you are looking at the 'Last Edited' time on the properties page as that time will be the server time. So, for example my server is 5 hours behind me and the 'Last edited' time when i saved it to publish at is at 8:57 even though it is 1:57 where I am at and i set the publish at time for 8:58 in order to test it 1 minute from the current time.

Mikael: Is it a clean install of 403 or is it an upgraded version from a previous one?

I tested on a 403 which I upgraded from 303 yesterday.

Peter

My install is clean.

A freash install on a freshly installed Windows 2008 server, the server is not running anything else.

I have this in the umbracolog in the DB:

<!-- /* Font Definitions */ @font-face {font-family:"Cambria Math"; panose-1:2 4 5 3 5 4 6 3 2 4; mso-font-charset:1; mso-generic-font-family:roman; mso-font-format:other; mso-font-pitch:variable; mso-font-signature:0 0 0 0 0 0;} @font-face {font-family:Calibri; panose-1:2 15 5 2 2 2 4 3 2 4; mso-font-charset:0; mso-generic-font-family:swiss; mso-font-pitch:variable; mso-font-signature:-1610611985 1073750139 0 0 159 0;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {mso-style-unhide:no; mso-style-qformat:yes; mso-style-parent:""; margin:0cm; margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:12.0pt; font-family:"Times New Roman","serif"; mso-fareast-font-family:Calibri; mso-fareast-theme-font:minor-latin;} .MsoChpDefault {mso-style-type:export-only; mso-default-props:yes; font-size:10.0pt; mso-ansi-font-size:10.0pt; mso-bidi-font-size:10.0pt;} @page Section1 {size:612.0pt 792.0pt; margin:3.0cm 2.0cm 3.0cm 2.0cm; mso-header-margin:35.4pt; mso-footer-margin:35.4pt; mso-paper-source:0;} div.Section1 {page:Section1;} -->

Error publishing node: System.TypeInitializationException: The type initializer for 'umbraco.cms.businesslogic.datatype.controls.Factory' threw an exception. ---> System.NullReferenceException: Object reference not set to an instance of an object.     at umbraco.BusinessLogic.Utils.TypeFinder.FindClassesOfType[T](Boolean useSeperateAppDomain)     at umbraco.cms.businesslogic.datatype.controls.Factory.Initialize()     --- End of inner exception stack trace ---     at umbraco.cms.businesslogic.datatype.controls.Factory..ctor()     at umbraco.cms.businesslogic.datatype.DataTypeDefinition.get_DataType()     at umbraco.cms.businesslogic.property.Property.MakeNew(PropertyType pt, Content c, Guid versionId)     at umbraco.cms.businesslogic.Content.createNewVersion()     at umbraco.cms.businesslogic.web.Document.PublishWithResult(User u)     at umbraco.cms.businesslogic.web.Document.Publish(User u)     at umbraco.presentation.publishingService.CheckPublishing(Object sender)

But the log entry timestamp is about 35 minutes later than the publish at time i set for the node.

Arrgh, sorry for the cut and paste crab in my prevous post.

Smells like this known issue.

http://umbraco.codeplex.com/WorkItem/View.aspx?WorkItemId=24993

Relates back to the part where the code relies on a current httpcontext when there might not be one.

I have previously put my own debug stuff in the source code and written to the eventlog when the checkpublishing method runs. This might help you identify the problem in your particular setup.

Thanks.

Will check that codeplex issue.

Mikael

is working on a reply...