We have deployed Zope withs static mirroring like this a few times. You can use wget, as Oleg suggested, to generate the static pages. We have optimized this approach by making Zope build export lists, which are special DTML generated index pages with HREF links to all newly modified documents. Then we direct wget with 1 level of recursion to this export list, and it then fetches just what was changed. Another feature: when the export list renders itself it records the time in a property so that when it is rendered again it knows that only documents modified after that time need to be listed. Regards, Luciano Mike Blake wrote:

Hi!

First of all: We have a client that (because of lame internal policy) will not be able to install zope on the final server. However, they _do_ want zope as a publishing solution for a web that will be practically nothing but dtml docs, images, and folders. They're only intested in accessing the web interface to modify text in custom zclass product interfaces we will make for them.

Provided that there are no complicated methods integrated into the zope structure, is it possible to generate a navegable static html version of a zope hierarchy?

Our idea is to let them access our server to manage and edit content and to give them a publish option (written in python or perl) that generates the html and ftps the site to a remote, non-zope webserver.

The day that the client wants a more dynamic site with searching and such, we would discuss installing zope again on the remote server.

Please give me your thoughts on this workaround solution.

thanks, -- [morcilla@ketden.com chikoon]$ whoami Mike Blake

_______________________________________________ Zope maillist - Zope@zope.org http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )