Re: Import Error - No module named zmsgraphic

Thorsten Weber <[email protected]> Tue, 11 Oct 2011 10:54:19 +0200
Newsgroups gmane.comp.cms.zms.devel
Message-ID <[email protected]>
Yes, i hab also problems with new teaser objects with latest built when i initiated the core objects:
 as far as i have seen, the new zpt objects broke encoding in combination with german umlaute.
-> zope runs in utf-8 mode (sitecustomize.py, rest-input, rest-out and zpublisher-encoding = utf-8)

i thought maybe the string \042 in pagetemplate was guilty for that .... 
but replacing against chr(042) did not did the trick ... 
so I reimported "old" dtml-templates too.


btw: is downgrading to prior zms version possible? 
maybe something went wrong when upgrading to newer zms build (object changes in ZMSGraphic?) ?!


I wonder how to migrate to zope2.12 when even import to zope1.10 breaks ...
but i can give it a try ...

a pity that you can't remember how you solved that ... !
would be a precious info for migration process to new zope version!


kind regards,  
Thorsten Weber



Am 11.10.2011 um 10:07 schrieb Niels Dettenbach:

> Am Montag, 10. Oktober 2011, 20:19:06 schrieben Sie:
>> i can very this. By trying to update from Zope 2.10.12 / ZMS 2.13  to  Zope
>> 2.10.13 / ZMS 2.13 and the   same error message appear. But i haven't found
>> a solution yet, maybe someone else can help?
> 
> Had a similiar problem some weeks ago but did not reaaly remember how i solved 
> it.
> 
> However i can give you some tips which may (!) help in these cases:
> 
> 
> - make shure you are using same Zope and ZMS version (major, minor) numbers - 
> i.e. zms 2.12 with zope 2.12 and 2.10 with 2.10 aso...
> 
> - for ZMS 2.13 i currently still use Zope 2.12 as Zope 2.13 gaves me several 
> errors (not shure how far the actual 2.13 is stable with actual Zope 2.13):
> 
> ZMS: ZMS2 2.13.4.1651 (Build #134c)
> ZOPE: (2.12.14, python 2.6.6, linux2)
> PYTHON: 2.6.6 (r266:84292, May 25 2011, 10:58:51) [GCC 4.5.2]
> 
> - install PIL (Python Imaging) reachable from your ZMS - you may try it from 
> a fresh ZMS instance for testing purposes
> 
> 
> Furthermore i had upgrade problems with current ZMS 2.13 (ZMS2 2.13.4.1651 
> (Build #134c)) in context of Teasers (may be related to my own work on 
> Teasers) - i solved that by reinstalling a former working Teaser 
> (Container/Element) within the upgraded instance for now.
> 
> hth
> 
> best regards,
> 
> 
> Niels.
> 
> -- 
> ---
> Niels Dettenbach
> Syndicat IT&Internet
> http://www.syndicat.com/