Re: ISO 2UTF-8

--- "Dr. Frank Hoffmann" <fh@...> wrote:
>
> HINT:
> the secure path should take all the version steps via the latest
> builds from 2.1/2.2/2.3/2.8/2.9./2.10;

ok. Let's describe an insecure shortcut:
2.0 /  2.3 / 2.10.3 -18 / 2.10.5-21

    * Intermediate 2.3 did the UTF-8-conversion.
    * Omitting intermediate 2.10.3 -18 leaded to errors in the folder
structure (wrong sequence of subfolders after ZEXP import).
    * Actual (stable?) release  zms-2.10.4-20 failed completely. See
below. So we decided to take 2.10.5-21
The websites in question:

    * www.vordach-fabrikverkauf.de <http://www.vordach-fabrikverkauf.de>
    * www.folienschweissgeraete.com
<http://www.folienschweissgeraete.com>
    * www.mofix.com <http://www.mofix.com>

Template Set:  Modified ZMS template set #21

Source instance:  ZMS 2.0 Build #116m, Zope 2.6.1, python 2.1.3 on
FreeBSD (freebsd4))

Target instance:  ZMS 2.10.5-21, Zope 2.10.5-final, python 2.4.4 on
debian linux 4.0 (etch) including additional Products (e.g. ZMySQLDA for
MySQL 5).

1st try:

ZEXP-Import directly from source into new target.  Partially successful:
failure concerning iso2utf8-conversion.

2nd try (via intermediate zms 2.2):

Upgrade to zms-2.2.0-b28 on source instance  with old Zope/Python (Zope
2.6.1, python 2.1.3). Failure. Incompatible Python-Version:  cannot find
module pyexpat in zms/_builder.py and other modules. Upgrading python on
the old system was not possible.

3rd try (via intermediate ZMS: 2.3.2 and 2.10.3):

Luckily, we had another client (ZMS  2.3.2-b45 build #122 , Zope
2.7.3-0, python 2.3.4, freebsd4). That did the utf-8-conversion. Steps:


    1. Imported via ZEXP in ZMS: 2.3.2-b45  (Build #122), Zope 2.7.3-0,
python 2.3.4, freebsd4) success: Updated object-model from build #116m
to #122. iso2utf8-conversion was ok!!!
    2. Exported to new ZEXP
    3. Blank target Instance: Zope 2.10.5-final, python 2.4.4,
zms-2.10.3-18_1 + import from ZEXP. success: --> Synchronized
object-model from build #122 to #129b!, Synchronized object-model from
patch #122 to #129b!
    4. Intermediate (failing!) step: Upgraded to zms-2.10.4-20: (Site
Error: global name 'REQUEST' is not defined (Module
Products.zms._confmanager, line 89, in initCSS NameError: global name
'REQUEST' is not defined)
    5. Removed zms-2.10.4-20, Upgraded to zms-2.10.5-21. success:
Synchronized object-model from patch #129b to #129f!


Remaining problems to be solved after above upgrade steps:


(a) Zope Event Log:

try: result = render_blocks(self._v_blocks, md)
   File "/opt/zope-2.10.5/lib/python/DocumentTemplate/DT_Util.py", line
196, in eval
     return eval(code, d)
   File "<string>", line 1, in <expression>
NameError: name 'lang' is not defined

workaround: added to standard_html_header
<dtml-call "REQUEST.set('lang','ger')">

(b) Teaser did not work properly (All Teasers were being rendered in
complete sub-hierarchy)
workaround: removed bodyContent_Teaser from the template set; obviously,
teaser rendering comes from zms directly.

(c) KeyError: 'ZMS_COMMON'
workaround: added to standard_html_header
<dtml-call
"REQUEST.set('ZMS_COMMON','%s/common'%getHome().absolute_url())">

(d) KeyError: 'ZMS_ROOT'
workaround: added to standard_html_header
<dtml-call
"REQUEST.set('ZMS_ROOT','%s/content'%getHome().absolute_url())">

Hermann Husen