Re: Be careful deleting Special Objects!

Peter Zechmeister's message saved me the day ;-))
For people like me who wanted to know more about the "messing around
in _globals.py" here how it worked for me:
.../Products/zms/_globals.py
Line 645
    d = (t[0],t[1],t[2],0,0,0,t[6],t[7],t[8])
replace with 
    d = 0,0,0,0,0,0,0,0,0
Restart Zope, clear trashcan and undo changes to _globals.py

Regards,
M. Neuhoff



--- In [email protected], Peter Zechmeister
<peter.z.nogroupwise@...> wrote:
>
> I've had a serious problem:
> 
> Suddenly I was not able to get into a ZMS Node any more. I got an error:
> 
>   Module Products.zms.zms, line 826, in updateVersion
>   Module Products.zms.zmstrashcan, line 163, in run_garbage_collection
>   Module Products.zms._globals, line 653, in daysBetween
>   Module Products.zms._globals, line 646, in stripDateTime
> IndexError: string index out of range
> 
> After messing around in _globals.py a little bit, I got the node running
> again.
> The thing, which had caused the problem was, that I experimented a lot
> with special objects and deleted some of them again. But I overlooked,
> that there where still some instances of them in the trash. These
> zombies caused the error.
> 
> In previous versions ZMS took care of existing instances if you wanted
> to delete a special object, even in trashcan. It seems that in
> zms-2.11.0_27 there is a gap concerning this.
> 
> Regards
> PeterZ, JKU
>