Hi All,

I've run into the bug where a writer who does not have access to publish a node can simply put a date in the "Release Date" field and the node will publish at that date/time.  I decided to circumvent this by writing a BeforeSave method that checks if the user is a writer and, if so, sets sender.ReleaseDate back to DateTime.MinValue (it also checks to see a date wasn't already in the doc, so as not to overwrite one a publisher put there). 

    public UmbracoEventExtender()
    {
        Document.BeforeSave += new Document.SaveEventHandler(Document_BeforeSave);
    }

    void Document_BeforeSave(Document sender, umbraco.cms.businesslogic.SaveEventArgs e)
    {

        // Ensuring that a writer cannot save a Release or Expire date for a node.  There is a bug
        // in Umbraco that allows the node to be published when a writer sets the Publish date.
        if (umbraco.helper.GetCurrentUmbracoUser().UserType.Alias == "writer")
        {

            // Checking to see if a publish date had already been set on the node.  We don't want to undo
            // a publish date set by a publisher
            Document doc = new Document(sender.Id);

            if ( doc == null ) {

                sender.ReleaseDate = DateTime.MinValue.ToString();
                sender.XmlGenerate(new System.Xml.XmlDocument());

            }

            else {
                
                if ( doc.ReleaseDate != DateTime.MinValue && sender.ReleaseDate != doc.ReleaseDate )
                    sender.ReleaseDate = doc.ReleaseDate;

                else
                    sender.ReleaseDate = DateTime.MinValue;

            }

        }        

    }

Thing is, it's not working.  I've read that there's also a bug in Umbraco such that the ReleaseDate and other properties get persisted to the database before this code is even hit, making my code useless.  Is there another way around this issue?  This part of the workflow is pretty important.  Is there a way to hide the Release and Expire dates from writers?

Thanks,

Jay