[drupal-devel] [bug] Make node_save() recursion-aware
chx
drupal-devel at drupal.org
Thu Aug 18 04:57:16 UTC 2005
Issue status update for
http://drupal.org/node/27007
Post a follow up:
http://drupal.org/project/comments/add/27007
Project: Drupal
Version: cvs
Component: node system
Category: bug reports
Priority: normal
Assigned to: jvandyk
Reported by: jvandyk
Updated by: chx
Status: patch (code needs work)
If there would be a little comment why this is needed, then I'd +1 it
heartily.
chx
Previous comments:
------------------------------------------------------------------------
Tue, 19 Jul 2005 02:14:16 +0000 : jvandyk
Attachment: http://drupal.org/files/issues/node_serialized2x.patch (664 bytes)
node_save() saves a node, then calls insert or update hooks. These hooks
may run functions that, in turn, call node_save().
This all works fine except that if a revision is being created, the
revision gets serialized twice -- once on the original node_save() call
and once on the callback's node_save() call.
The attached two-line patch simply inserts a boolean variable called
rev_serialized to keep track of whether the serialization has already
been done.
I'd like to see cvs and 4.6 patched.
This patch is necessary so I can release actions and workflow for 4.6.
Background: http://drupal.org/node/24326
------------------------------------------------------------------------
Tue, 19 Jul 2005 18:36:23 +0000 : Dries
I don't like this patch. It's a hairy fix. There must be a better way
to avoid recursion in first place.
------------------------------------------------------------------------
Thu, 18 Aug 2005 01:26:21 +0000 : moshe weitzman
gosh, this a two line change with zero performanhce impact. seems like a
useful and minimally invasive fix for our current dilemma. we'll remove
it once a better fix comes around. is a shame to hold back
workflow/actions for such a minor issue. any others want to comment or
suggest a different solution?/
More information about the drupal-devel
mailing list