You are here: » Home » News » Archive » 01/05 ZMS 2.3

How to update ZMS 2.3

Author: Frank Hoffmann, Jürgen Klein, 2005/01/06

From ZMS-Version 2.2 on the character encoding UTF-8 is used. For this reason some issues are to be recognized when updating to ZMS2.2+/Zope2.7+. Regularly, the ISO-Latin Code must be substituted by HTML entities within templates and special objects. Also some CSS adaptations are to be done, especially concerning the ZMS teaser element. Find here a short list of the most important steps when updating.

Setup a new system/computer with Zope 2.7.2/3 resp. an active instance (Note: Zope 2.7+ is working wih instances)^*
Copy and paste the current ZMS 2.3.2#45+ http://sourceforge.net/projects/zmspublishing/ into the directory 'lib/python/Products/' of the Zope installation
Copy and paste those Zope products that were used on the live system up to now
Copy the Data-fs of the live system into the var-directory of the newly installed Zope instance
A. TEST UPDATE: Call the ZMS content objects/masters; by this an independent processing of all contents starts on UTF-8
Change maually all umlauts/special characters within the DTML templates (even SpecObjs) to HTML entities (so that they can be displayed correctly acc. to UTF-8)
Fine tuning of CSS, esp. of the teaser element
Fix a date for the change
Save the updated templates and CSS
Freeze the editorial work and make a final copy of data.fs in the update system
B. FINAL UPDATE: again do a content update processing and replace the templates with the revised templates, if necessary fine tuning of the content
Delete/update ZCatalog
Shift the IP/ports

^*Example
Zope installation: /home/zope27
Here products can be installed that will be available in all instances
Zope-Instanz: /home/Zope
Here products can be installed that will be available in this instance

Annotation

Alternatively to the update at a second computer you may also install a second Zope at the same computer which is running on another port (e.g. 8090); in this case only the port is to be changed finally when shifting.

Tip

When pages are divered by an Apache Webserver problems with the mod_proxy-Modul by Apache may occur.

From ZOPE 2.7 on ZOPE delivers a modified 304 message. (The server code 304 in HTTP log means 'Not Modified'). In opposite to former Zope versions, the file header now is delivered with this message only, but no longer the file itself.
This is correct by ZOPE, however it cannot be correctly processed by Apache mod_proxy.
mod_proxy substitutes the whole file in spite of server code 304 'Not modified'. Since Zope delivers only the header of the file with 304 Code 'Not Modified' but not the file itself, mod_proxy writes an uncomplete file in the cache. Logical consequence: the file (graphics incl. spacer etc.) cannot be displayed correctly.

Proceeding

1.) Comment out message 304 in the ZOPE source code.
App/ImageFile.py: #RESPONSE.setStatus(304)
OFS/Image.py: # RESPONSE.setStatus(304)
As a consequence, Zope delivers the file newly with each call. The page itself already is delivered quickly via Apache, however. By means of this workaround ZOPE has to do more work in the background without affecting the performance.

2.) Make use of Apache version 2.0. With this Apache version the problem does not occure.