Index: eventrepeat.module
===================================================================
RCS file: /cvs/drupal/contributions/modules/eventrepeat/eventrepeat.module,v
retrieving revision 1.46.2.3
diff -u -r1.46.2.3 eventrepeat.module
--- eventrepeat.module	22 Jan 2007 16:47:23 -0000	1.46.2.3
+++ eventrepeat.module	31 Jan 2007 15:54:29 -0000
@@ -1,5 +1,5 @@
 <?php
-// $Id: eventrepeat.module,v 1.46.2.3 2007/01/22 16:47:23 seanfuller Exp $
+// $Id: eventrepeat.module,v 1.46.2.2 2007/01/22 16:37:50 seanfuller Exp $
 
 // TODO: Update this section
 
@@ -1929,14 +1929,19 @@
 
       //now we need to run a check to see if this sequence should be closed.  run an update request based on the new
       //last rendered value.  if no dates are returned, then close the sequence
-      $dates_to_render = _eventrepeat_render_nodes($repeatpattern['rid'], NULL, TRUE, FALSE, FALSE);
-
+      $dates_to_render = _eventrepeat_render_nodes($repeatpattern['rid'], NULL, $update = TRUE, FALSE, FALSE);
+      $update = FALSE;
+      // The next three lines are rolled back from before #93256
+      if (!$dates_to_render) {
+        db_query("UPDATE {event_repeat} SET repeat_last_rendered = %d WHERE rid = %d",
+          $repeatpattern['repeat_end'], $repeatpattern['rid']);
+      // #93256 - The change below was causing a duplicate of the event you were editing so it was rolled back.
       // If there are no dates to render, set the last rendered date to the
       // end date, but only do this if the end date is not 0. If it is 0,
       // then the update line above will have already set the end date to the
       // date we ended on. This will keep us from starting over on repeat patterns
       // that don't have repeat expiration dates.
-      if (!$dates_to_render && $repeatpattern['repeat_end'] != 0) {
+      //if (!$dates_to_render && $repeatpattern['repeat_end'] != 0) {
         db_query("UPDATE {event_repeat} SET repeat_last_rendered = %d WHERE rid = %d", $repeatpattern['repeat_end'], $repeatpattern['rid']);
       }