<p>I haven't yet used the plugin, but I'd try to import the dates into another, custom datetime field (e.g. myImportDate) to see if it's a problem with <code>postDate</code> being a special field (also goes into other tables in the DB, as far as I know). This would be for testing purposes only...</p>

<p>Another hint that might help:<br>
Craft usually saves a datetime in a format like so: "2014-07-31 12:00:00". I've no idea if this is relevant for your plugin though. Same applies for the timezone, as <a href="http://buildwithcraft.com/docs/date-time-fields" rel="nofollow">Craft saves a datetime in UTC</a>. As the plugin uses the <a href="http://buildwithcraft.com/docs/apis/entriesservice#saveEntry" rel="nofollow">saveEntry API</a>, you probably don't have to care about the timezone, but the string format could break it for you.</p>

<p><em>Edit:</em></p>

<p>OK,<code>postDate</code> should be possible and the timezone defined after Craft install should be used to save datetime values. I'd bet it's the unusual "31/07/2014 00:00" format, Simon!</p>

CC BY-SA 3.0
2014-08-01T12:16:50.360Z
2014-08-01T12:28:06.287Z
2014-08-01T12:28:06.287Z
carlcs
<p>Yes, thanks carlcs!</p>

<p>So, as long as your <code>postDate</code> is set to this format "2014-07-31 12:00:00" and NOT your localised version as it appears in the Control Panel, everything works. Thanks to the magic of the import plugin, I can overwrite just the one field.</p>

CC BY-SA 3.0
2016-09-14T17:28:41.303Z
Think I could get a peek at your Import code? Are you formatting this as a string or a date?
Steve Mock
CC BY-SA 3.0
2014-08-01T13:56:12.873Z
2014-08-01T13:56:12.873Z
Simon Clayson
<p>Having much success with the <a href="https://github.com/boboldehampsink/import" rel="nofollow">Import Plugin</a></p>

<p>I've also raised this <a href="https://github.com/boboldehampsink/import/issues/9" rel="nofollow">here</a>, but thought this forum perhaps better.</p>

<p>I'm trying to force through a Post Date on my imports, but nothing is being respected, also, doesn't map automatically. All other fields have imported flawlessly, but PostDate seems to stick with the current date (not the date from years ago I want to be the postDate.</p>

<p>Can I check please?</p>

<p>I have CSV column titled tried a few but thought "postDate" would work best.
Date format, matched "31/07/2014" to the field, and "31/07/2014 00:00" but can't get anything to stick though any method (append, or replace)</p>

<p>Thanks in advance.</p>

<control-panel><postdate><plugin-import>
Import Plugin date format (Post Date postDate)
# Import Plugin date format (Post Date postDate)

(Asked by: username_0 on 2014-08-01)

Having much success with the [Import Plugin](https://github.com/boboldehampsink/import)

I've also raised this [here](https://github.com/boboldehampsink/import/issues/9), but thought this forum perhaps better.

I'm trying to force through a Post Date on my imports, but nothing is being respected, also, doesn't map automatically. All other fields have imported flawlessly, but PostDate seems to stick with the current date (not the date from years ago I want to be the postDate.

Can I check please?

I have CSV column titled tried a few but thought "postDate" would work best.
Date format, matched "31/07/2014" to the field, and "31/07/2014 00:00" but can't get anything to stick though any method (append, or replace)

Thanks in advance.

**Tags:** control-panel, postdate, plugin-import

---

## 2 answers

### Answer by username_1 on 2014-08-01. Score: 3 | Accepted answer

I haven't yet used the plugin, but I'd try to import the dates into another, custom datetime field (e.g. myImportDate) to see if it's a problem with `postDate` being a special field (also goes into other tables in the DB, as far as I know). This would be for testing purposes only...

Another hint that might help:  
Craft usually saves a datetime in a format like so: "2014-07-31 12:00:00". I've no idea if this is relevant for your plugin though. Same applies for the timezone, as [Craft saves a datetime in UTC](http://buildwithcraft.com/docs/date-time-fields). As the plugin uses the [saveEntry API](http://buildwithcraft.com/docs/apis/entriesservice#saveEntry), you probably don't have to care about the timezone, but the string format could break it for you.

*Edit:*

OK,`postDate` should be possible and the timezone defined after Craft install should be used to save datetime values. I'd bet it's the unusual "31/07/2014 00:00" format, Simon!


---

### Answer by username_0 on 2014-08-01. Score: 2

Yes, thanks carlcs!

So, as long as your `postDate` is set to this format "2014-07-31 12:00:00" and NOT your localised version as it appears in the Control Panel, everything works. Thanks to the magic of the import plugin, I can overwrite just the one field.

> **Comments:**
> **username_2**: Think I could get a peek at your Import code? Are you formatting this as a string or a date?  

---

