Hi all,

I'm experiencing some issues with the auto Publish At / Unpublish At functionality in Umbraco version 7.2.6

The Publish At function fails to make the page available after the datetime has passed. The backoffice registers the page as published, but with the "Oops: this document is published but is not in the cache (internal error)" message. This is fixed when someone manually fires the 'Republish Entire Site' function which then makes the page accessible.

The Unpublish At function also registers the page as unpublished in the backoffice after the set datetime but the page is still accessible on the website until someone manually fires the 'Republish Entire Site' function, then the page is unpublished properly and inaccessible.

I've tried a number of workarounds to no avail, including adding ContentServicePublished / ContentServiceUnPublished events that try to 'Republish Entire Site' on auto pub/unpublish. I've listed the code below:

    protected override void ApplicationStarted(UmbracoApplicationBase umbracoApplication, ApplicationContext applicationContext)
    {
        base.ApplicationStarted(umbracoApplication, applicationContext);
        ContentService.Published += ContentService_Published;
        ContentService.UnPublished += ContentService_UnPublished;
    }
    void ContentService_Published(global::Umbraco.Core.Publishing.IPublishingStrategy sender, PublishEventArgs<IContent> e)
    {
        bool isAutoPublish = false;
        foreach (var item in e.PublishedEntities)
        {
            if (item.ReleaseDate.HasValue && (item.ReleaseDate.Value - DateTime.Now).TotalMinutes < 10)
            {
                isAutoPublish = true;
            }
        }
        if (isAutoPublish)
        {
            umbraco.cms.businesslogic.web.Document.RePublishAll();
            umbraco.library.RefreshContent();
        }
    }
    void ContentService_UnPublished(Umbraco.Core.Publishing.IPublishingStrategy sender, PublishEventArgs<IContent> e)
    {
        bool isAutoUnpublish = false;
        foreach (var item in e.PublishedEntities)
        {
            if (item.ExpireDate <= DateTime.Now)
            {
                isAutoUnpublish = true;
            }
        }
        if (isAutoUnpublish)
        {
            umbraco.cms.businesslogic.web.Document.RePublishAll();
            umbraco.library.RefreshContent();
        }
    }

I realise 'umbraco.cms.businesslogic.web.Document.RePublishAll();' is obsolete but I had to try it seeing 'umbraco.library.RefreshContent();' wasn't working for me (in Azure).

I also noticed is that the .ReleaseDate property is always null, making it very difficult to determine whether an item was published manually or automatically published via the Publish At function. Is there another way to determine the auto published nature of the item in this context?

Steps to recreate all of the above issues:

1. In the backoffice, create a page node anywhere, populate it with any misc content, then hit Save and Publish. Visit the URL to see the page live.
2. Back in the backoffice, select an Unpublish At datetime for a few mins from now.
3. Wait it out and hit the expected URL for a while after the scheduled datetime, the page should still be incorrectly accessible as described above. Refresh the backoffice to see that Umbraco registers the page as unpublished, yet the page still renders.
4. Click 'Republish Entire Site' and try the page again, it should be properly unpublished.
5. Create a new node/page and just hit Save this time, not Save and Publish. Hopefully you can determine the expected URL, it'll help to test.
6. Set a Publish At datetime to a few mins from now. Hit the expected URL to see the page correctly not load or exist.
7. Wait it out and hit the expected URL for a while after the scheduled datetime and see if the page loads. Did the page load?
8. Check in the backoffice to see that the node is registered as published but doesn't resolve on the site. You may see the "Oops: this document is published but is not in the cache (internal error)" message displayed.
9. Republish the entire site again and access the page, it should load fine now.

I hope to find a solution to these issues as scheduled content are integral. I'd even accept a hack job / workaround at this point seeing I've already invested much into this project build.

Looking forward to hearing from anyone.