Way to export nodes and hold onto the created and changed dates for the import?

There is a setting at admin/settings/node_export on the D6 site to prevent the 'created time' from being reset. It is not possible to prevent the resetting of the changed/updated time, though.

This is due to the node_save() function in drupal. Yes we do have the option to create our own version of node_save(), and it looks like that might have to be something considered in the future.

yeh alright, I have put a version in dev which *might* let you override the changed date/time. It uses a custom version of node_save, this could be the first step to doing a few more things we've wanted to do.

Did you untick the reset of 'changed date' in the node export settings at admin/settings/node_export?

works for me

[I'm reactivating this issue so as not to create a duplicate, but if this was incorrect I apologize.]

I'm upgrading drupal from 5.x to 6.x, and I'm using Node Export to transfer nodes from the old site to the new site. Specifically, I'm using the bulk export feature ("Export nodes") from the admin/content/node page.

However I'm having trouble with the "Authored On" date.

First, let me say that I've made sure to UNCHECK the "Created time" and the "Changed time" settings in admin/settings/node_export for each node type that I'm importing into the 6.x site.

If I view the imported nodes in admin/content/node the nodes show up in the proper order.

But here's the problem the node itself displays the date I imported the node, not the "Authored On" date (the same is true if I edit the node and scroll down to the "Authored on" field ). Also, my views are also using the imported date. And views doesn't appear to have a "authored on" field.

Any help would be appreciated.

JV

You have not identified any bugs. You have not convinced me your problem is with Node Export. You don't even seem to have a good strategy for checking whether the value was saved correctly, such as through debugging the node object, manually reading the database, or comparing the values of a subsequent export. It's called "node: post date" in views.

And don't change the fricken issue settings. Bloody hell.

danielb,

I didn't mean to tick you off. I apologize, and if you'll read my post a little closer, I think you'll find I wasn't sure what the proper procedure was.

But you responded very quickly and I definitely appreciate your help. Based on your suggestions, I will now do what I can to figure out where the problem is and will post a new issue at that time.

Thanks,

JV

Hi jvinci and danielb,

I'm actually having the same issue. I've just exported about 40 nodes using the Node Exporter. When I import them into my new site, both the Created and Changed Dates in the database (and in the UI) are for today's date, which isn't accurate. I can see in the .export file that it does save these dates, yet somehow it's not using them when importing the nodes into the new site.

Is anyone still having issues with having "Change time" unticked and the node "Last Updated" date being reset to the date of import?

I have node export configured so the content type I am importing should not reset the "Last Updated" date on import. The date is being reset anyhow.

Can someone help?