Re: Import Error - No module named zmsgraphic
Rainer Wollthan <[email protected]> Tue, 11 Oct 2011 10:19:51 +0200
| Newsgroups | gmane.comp.cms.zms.devel |
|---|---|
| Message-ID | <[email protected]> |
The Problem ist that only Zope2.13 is available on this Server, and i can't migrate a ZMS from Zope2.12 to Zope2.13 - i also try a complete zexp import, or an "Content Import" but always the same error occur. ZMS: ZMS2 2.13.4.1630 (Build #134c) ZOPE: (2.13.7, python 2.6.6, linux2) PYTHON: 2.6.6 (r266:84292, Dec 27 2010, 00:02:40) [GCC 4.4.5] PIL is installed and work normal Gruß Rainer 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/ Rainer Wollthan [email protected]