[Zope] ZSyncer and bobobase_modification_time

Andy McKay andym@ActiveState.com
Tue, 10 Jul 2001 12:34:42 -0700


For all those who were having problems with ZSyncer and
bobobase_modification_time, I believe its because there isnt a
bobobase_modification_time for broken products. So if you have any broken
products, fix them (on both ends) and ZSyncer should work fine.

I'll throw this patch into ZSyncer soon.
Is there a sure fire if telling if an object is "broken"?

In the meantime heres the patch:

--- OldZSyncer.py       Tue Jul 10 12:32:38 2001
+++ ZSyncer.py  Tue Jul 10 12:30:17 2001
@@ -210,7 +210,8 @@
         # go find the folder, then iterate through the subject
         for ob in self.restrictedTraverse(string.split(folders,
'/')).objectValues():
             # we dont to sync ZSyncers, that way leads much confusion
-            if ob.meta_type != 'ZSyncer':
+            if ob.meta_type != 'ZSyncer':
+                if ob.meta_type[:14] == 'Broken Because': continue
                 o = {}
                 o['id'] = ob.getId()
                 o['path'] = ob.getPhysicalPath()

Cheers.
--
  Andy McKay.