Answers.Body: <p>If the entry is not already published, just set the <code>Post Date</code> to a date in the future. </p>
  
  <p><a href="https://i.sstatic.net/aNOdn.png" rel="noreferrer"><img src="https://i.sstatic.net/aNOdn.png" alt="Future Post"></a></p>
  
  <p>That will set the entry to what Craft calls <code>Pending</code>. On the entry's index, the status indicator will be orange (instead of green).</p>
  
  <p><a href="https://i.sstatic.net/XvJlj.png" rel="noreferrer"><img src="https://i.sstatic.net/XvJlj.png" alt="Future Entry"></a></p>
  
  <p>If the entry is already currently published, no. That'd be a <a href="https://github.com/craftcms/cms/issues/864" rel="noreferrer">feature request</a>. I agree, it would be great to be able to "publish over" the current edition (say for a contest or what not). If you set a draft's entry to a future date, Craft will un-publish the entry and set the status to pending.</p>
  
  <p>You could work around this in Twig though. Say you want to have the entry change on 11/10. Set up a new Draft, name it <code>Will Go Live on 11/10</code> (or whatever). Then in your template:</p>
  
  <pre><code>{% if now|date('U') &gt; "2015-11-10"|date('U') %}
  
  {% set theDrafts = craft.entryRevisions.getDraftsByEntryId(entry.id) %}
  
  {# keep the "old" entry around just in case #}
  {% set oldEntry = entry %}
  
          {%for i in theDrafts %}
  
              {# look for the specific draft and set if it exists #}
  
              {% if i.name == "Will Go Live on 11/10" %}
                  {% set entry = i %}
              {% endif %}
  
          {% endfor %}
  
  {% endif %}
  
  {# template as normal #}
   ...
  </code></pre>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-11-04T01:49:34.607Z
Answers.Text: Thank you for your response. The latter is the use case I am looking for... especially for single entries.
Answers.UserDisplayName: Taylor
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-11-03T23:19:00.183Z
Answers.LastActivityDate: 2017-06-05T21:26:16.477Z
Answers.LastEditDate: 2017-06-05T21:26:16.477Z
Answers.UserDisplayName: RitterKnight
Body: <p>Is there a way to schedule a <strong>draft</strong> of a entry to go live?</p>
  
Tags: <entry><draft>
Title: Schedule a draft to auto publish?
ThreadText: # Schedule a draft to auto publish?
  
  (Asked by: username_0 on 2015-11-03)
  
  Is there a way to schedule a **draft** of a entry to go live?
  
  **Tags:** entry, draft
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2015-11-03. Score: 9
  
  If the entry is not already published, just set the `Post Date` to a date in the future.
  
  [![Future Post](https://i.sstatic.net/aNOdn.png)](https://i.sstatic.net/aNOdn.png)
  
  That will set the entry to what Craft calls `Pending`. On the entry's index, the status indicator will be orange (instead of green).
  
  [![Future Entry](https://i.sstatic.net/XvJlj.png)](https://i.sstatic.net/XvJlj.png)
  
  If the entry is already currently published, no. That'd be a [feature request](https://github.com/craftcms/cms/issues/864). I agree, it would be great to be able to "publish over" the current edition (say for a contest or what not). If you set a draft's entry to a future date, Craft will un-publish the entry and set the status to pending.
  
  You could work around this in Twig though. Say you want to have the entry change on 11/10. Set up a new Draft, name it `Will Go Live on 11/10` (or whatever). Then in your template:
  
  ```
  {% if now|date('U') > "2015-11-10"|date('U') %}
  
  {% set theDrafts = craft.entryRevisions.getDraftsByEntryId(entry.id) %}
  
  {# keep the "old" entry around just in case #}
  {% set oldEntry = entry %}
  
          {%for i in theDrafts %}
  
              {# look for the specific draft and set if it exists #}
  
              {% if i.name == "Will Go Live on 11/10" %}
                  {% set entry = i %}
              {% endif %}
  
          {% endfor %}
  
  {% endif %}
  
  {# template as normal #}
   ...
  
  ```
  
  > **Comments:**
  > **username_0**: Thank you for your response. The latter is the use case I am looking for... especially for single entries.  
  
  ---
  
  