Answers.Body: <p>Setting <code>enabled = 1</code> will not alter your postDate.</p>
  
  <p>If you were to set a postDate in the future, the entry would simply not show up (by default).
  However, if you'd want enabled entries with a future postDate to show up in your template results, use:</p>
  
  <pre><code>{% set futureEntries = craft.entries.status('pending') %}
  </code></pre>
  
  <p>If you do not use the <code>status</code> criterium, it will default to <code>live</code>, which is all enabled entries with a postDate in the past. So, it all depends on how you display the entries, not so much on how you save them.</p>
  
  <p>Also, see <a href="http://buildwithcraft.com/docs/templating/craft.entries#status" rel="nofollow">this Craft docs information on status</a>.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-11-20T07:39:32.097Z
Answers.LastActivityDate: 2014-11-20T07:39:32.097Z
Answers.UserDisplayName: Paul
Body: <p>I have a front end form where I set have</p>
  
  <pre><code>&lt;input type="hidden" name="enabled" value="1"&gt;
  </code></pre>
  
  <p>I also need to set the postDate to a date in the future. Does setting enabled = 1 reset the postDate in all cases? Or should I just forego the enabled form field altogether in favor of Setting postDate?</p>
  
Tags: <frontend>
Title: Does setting Enabled = 1 override postDate in front end forms?
ThreadText: # Does setting Enabled = 1 override postDate in front end forms?
  
  (Asked by: username_0 on 2014-11-20)
  
  I have a front end form where I set have
  
  ```
  <input type="hidden" name="enabled" value="1">
  
  ```
  
  I also need to set the postDate to a date in the future. Does setting enabled = 1 reset the postDate in all cases? Or should I just forego the enabled form field altogether in favor of Setting postDate?
  
  **Tags:** frontend
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2014-11-20. Score: 2 | Accepted answer
  
  Setting `enabled = 1` will not alter your postDate.
  
  If you were to set a postDate in the future, the entry would simply not show up (by default).
  However, if you'd want enabled entries with a future postDate to show up in your template results, use:
  
  ```
  {% set futureEntries = craft.entries.status('pending') %}
  
  ```
  
  If you do not use the `status` criterium, it will default to `live`, which is all enabled entries with a postDate in the past. So, it all depends on how you display the entries, not so much on how you save them.
  
  Also, see [this Craft docs information on status](http://buildwithcraft.com/docs/templating/craft.entries#status).
  
  
  ---
  
  