Re: AW: Problems updating from 2.9.4 to 2.10.4b20

Stefan Seifert <[email protected]>
Newsgroups gmane.comp.cms.zms.devel
Organization Atikon EDV & Marketing GmbH
Message-ID <[email protected]>
Der ZMS-developers,

we are currently preparing an upgrade of our ZMS installation hosting about 
400 websites from 2.3.2-b57 to 2.10.5-15 and frankly, it's quite some mess. 
Not as much the upgrade itself, but figuring out how to do it and which 
intermediate versions we have to use (and porting our custom patches, some of 
which were posted to this list but not accepted into the official version, to 
the new version, but that's another story). We settled for 2.8.1-a52, 
2.9.4-41 and then 2.10.5-15 and it seems to work fine. That's why the 
following message confuses me a little:

On Sunday, 02. March 2008, Dr. Frank Hoffmann wrote:

> http://bscw.hoffmannliebenberg.de/pub/bscw.cgi/d294466/zms-2.10.3-18_1.tar.
>g z
> IMPORTANT NOTE:
> Migrations of ZMS instances prior to 2.10.3-19 have to be done with this
> version because later versions do not automatically convert meta_type
> ['ZMSRubrik'] to ['ZMSFolder'] !!

Grepping for ZMSRubrik in the ZMS code reveals only two lines difference 
between 2.10.3-18_1 and 2.10.5-15:
zms.py: 'ZMSRubrik':{           'obj_class':ZMSRubrik,
zms.py:                         'obj_attrs':ZMSRubrik.__obj_attrs__ },

Are these lines responsible for the meta_type conversion?

And while I'm at it: any other hints for a safe upgrade path?

Many thanks in advance,
-- 
Stefan Seifert

a t i k o n   e d v   &   m a r k e t i n g   gmbh
webdesign     grafikdesign     softwareentwicklung
__________________________________________________

a-4020 linz        salzburger straße 205
tel:               +43(0)732/611 266-37
fax:               +43(0)732/611 266-20
mailto:            [email protected]
web:               www.atikon.com
firmenbuchnummer:  199780w 
firmenbuchgericht: landesgericht linz
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.