Updating ZMS

Solution: In principle the update is to be tested in a copy of the current productive system resp. in another Zope instance (on another computer). For this purpose the client folder with templates is copied resp. exported as zexp-file. In the next time the editorial work on the original should be stopped.
The replicated is "configured down" as follows:
1. Empty the trash
2. No Workflow
3. No History
4. Delete media folder
5. Empty the cache
6. Update or empty the index at content/catalog/manage_catalogIndexes and deactivate Catalog-Awareness.

With this "low-level" ZMS a consistent zexp-file can be exported if needed and be placed on another server. (An XML export under ZMS is due to the new output of IDs and thereby caused inconsistency of links when re-importing primarily not suitable for the complete migration).
On the level of the operation system the current zms.zip is unzipped in folder /$myzope/lib/python/Products and then Zope is restarted. A ZMS-internal update routine provides for the poss. adjustment of object definitions.

For distant updates, e.g. from ZMS 1.0 to ZMS 2.0, a stepwise process is recommended (see forum contribution "stepwise updating").

Comment: Please note necessarily the following links.