Re: Import Error - No module named zmsgraphic

Thorsten Weber <[email protected]> Sun, 13 Nov 2011 09:27:53 +0100
Newsgroups gmane.comp.cms.zms.devel
Message-ID <[email protected]>
I downgraded from 2.13.4 to 2.11.4 successfully on Zope 2.10.5 ...  

after calling content node I got this message:
Synchronized object-model from patch #134c to #132e!
I deleted catalog and deactivated workflow
then I did an export to file system
removed instance, packed main_db and restarted instance (just to be sure)
reimport worked without problems
Befoere we experienced some severe problems with zms 2.13 before: 
data fields (proto image) were gone (defined in spec.obj but invisible in custom object)
objects with ZMSTable were no more accessible after edit
zms instance was no more importable/transferable
but i can not say, wether these problems were selfmade (by any chance) or by design.

after all I think it would be a good idea to publish some sort of update path on zmslabs 
or to mark milestone releases for secure version upgrades.


Then again I tested Zope 2.13 (with ZMS 2.11.4) ... as we are interested in zeo improvements by zodb 3.10 => the performance is about 1/3 better :)

I noticed a problem on import with zcatalog/textindexng3:
Importerror: no module named Vocabulary

anyone came across this issue and knows how to solve that?


kind regards,  
Thorsten Weber


Am 11.10.2011 um 11:32 schrieb Niels Dettenbach (Syndicat IT&Internet):

> A downgrading processing to older ZMS versions is afaik not implemented in ZMS but possible in "some" cases where objects are backward compatible it works, but might by a bad idea in general. Usually it is the best idea to hold any working old instance as long as the upgraded one is not tested very well in detail.