Closed (won't fix)
Project:
Drupal core
Version:
6.x-dev
Component:
node.module
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
1 May 2008 at 16:12 UTC
Updated:
2 Jan 2014 at 19:06 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
catchA couple of things
patch is missing -u option (I am deeply shocked)
I think we should have 'created' and 'updated' timestamps for comments, this may be out of scope though.
Comment #2
morbus iffIf the way a patch was generated is a code quality issue, please set this back. Otherwise, pithy.
(And yeah, I agree: created/updated timestamps are out of scope here.)
Comment #3
morbus iffReapplied. This was the first time I had used cvs since I reinstalled the OS, so didn't have a .cvsrc file with the proper diff settings.
Comment #4
moshe weitzman commentedWorks as advertised ... fapi protects us from any unauthorized user sending a timestamp.
Comment #5
dries commentedI'd love to commit this patch but it no longer applies. Needs a quick re-roll.
Comment #6
morbus iffAttached. Sorry for the delay. Set to RTBC after re-roll.
Comment #7
morbus iffComment #8
dries commentedCommitted to CVS. Thanks Morbus.
Comment #9
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.
Comment #10
pasqualleComment #11
nevergoneThis patch only works with Drupal 6.3.
Comment #12
gábor hojtsy6.x patch contained tabs, so fixed those before committing. Will be in next Drupal 6 release, thanks!
Comment #13
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.
Comment #14
cor3huis commentedThe original issue was invalid to begin with, "node_presave" should have been used I bet.
Comment #15
damien tournoud commentedThis is *not* the same issue. This issue was about *comments*.
I not sure I understand what you believe needs fixing in node_save(): by design, you can set $node->created, but not $node->changed, which will always be the timestamp of when node_save() was called.
Anyway, really not the same issue. Please open a different issue (targeted at Drupal 7, we always fix bug in the highest version first) and describe your use case there.
Comment #16
cor3huis commentedTHX
Comment #17
cor3huis commented