Node created date changed on node update

Hi, still no news on this bug?

I had a look at the module code and i found that tiptoes was right.
I did a little to change to line 257 of override_modes_options.module as follows:

if (($node->date !== $node->override_authored_on || !empty($node->override_authored_on)) && isset($node->override_authored_on)) {
$node->date = $node->override_authored_on;
$node->created = !empty($node->override_authored_on) ? strtotime($node->override_authored_on) : time();
}

As you may see I just added a parenthesis around the old conditions and then I added "&& isset($node->override_authored_on)"
in this way if the date field wasn't set nothing changes.

I'm testing it on my website and it seems to work correctly.
I would have made a patch but I'm new to drupal and have no idea on how things work here. Just wanted to to add my 2 cents to try to solve this bug. :)

I have the same problem. Thanks Stefano, your solution works for me and I made patch for it.
Please review.

+++ override_node_options.module	2009-09-23 17:18:48.000000000 +0600
@@ -254,7 +254,7 @@ function _override_node_options_apply_ke
+        if (($node->date !== $node->override_authored_on || !empty($node->override_authored_on)) && isset($node->override_authored_on)) {

I think we can just check isset rather than both isset and empty. Wacky ol' PHP!

But also, I wonder if this would be fixed by #644820: Use the same form element names, not new ones.

I'm on crack. Are you, too?

Will be fixed with #644820: Use the same form element names, not new ones.

I have a similar issue (drupal 7):
For one of the content types, most of the time, the node created time is also updated after updating a node!
So this results in node created timestamp and node updated timestamp to be the same after updating node(automatically with a custom module) and the node created time is lost.

Is there anyway to stop this behavior and keep the created timestamp intact?
thanks

I've added testNodeCreateDateDoesNotChange() (see http://cgit.drupalcode.org/override_node_options/commit/?id=191667b) to the tests for this module to try and replicate this by creating a new node, saving it and then comparing the created values.

These tests show that the changed value changes as expected, and that the created value remains the same.

I'd suggest checking your custom code for updating the node for anything that could be causing it.

If you continue to have the issue, please create a new issue advising how to replicate the issue within the above test.

The method has been renamed to testNodeCreatedDateDoesNotChange().