Imported data has "changed" timestamp reset to current though configured otherwise [#2839976]

When i import via paste code using json data exported from VBO; the new nodes do get the proper created dates; but all nodes have changed date reset to current date.

Yes, the "Changed time (Last updated date/time) " setting for this node type is not set to be reset.

Comment	File	Size	Author
#4	node_export-changed_reset_despite_config-2839976-4.patch	609 bytes	Ronino
#2	Screen Shot 2018-07-09 at 1.37.11 PM.png	37.57 KB	anmolgoyal74

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Comment #1

29 December 2016 at 20:24

liquidcms created an issue. See original summary.

Comment #2

anmolgoyal74 CreditAttribution: anmolgoyal74 at OpenSense Labs for DrupalFit commented 9 July 2018 at 08:09

Status:

Active

» Needs review

File	Size
Screen Shot 2018-07-09 at 1.37.11 PM.png	37.57 KB

I tested this case, everything is working as required.
If the "Changed time (Last updated date/time) " setting for node type is not set to be reset, the last updated time is same as in the node.
See the screenshot attached.

If you are still facing the issue, Please describe the steps to reproduce the error.

Comment #3

gaurav.kapoor CreditAttribution: gaurav.kapoor commented 8 August 2018 at 10:26

Status:

Needs review

» Closed (outdated)

Comment #4

Ronino CreditAttribution: Ronino as a volunteer commented 7 August 2019 at 12:20

Title:	imported data has changed date reset to current	» Imported data has "changed" timestamp reset to current though configured otherwise
Version:	7.x-3.1	» 7.x-3.x-dev
Status:	Closed (outdated)	» Needs review

File	Size
node_export-changed_reset_despite_config-2839976-4.patch	609 bytes

I think this occurs if there are dependencies to be handled like field collection items in my case.

There are multiple occurrences of where node_save() instead of the custom version node_export_save() is used, leading to the "changed" timestamp being reset when the node is saved again after dependencies have been handled.

My patch fixes this in node_export_dependency_node_export_after_import_alter() and all changed timestamps are kept for me now. I didn't change the other occurrences of node_save() though as I couldn't test that code.