On Feb 4, 2005, at 3:31 PM, Roger Oberholtzer wrote:
Or, maybe there is a better way to do this. I have a site that is jumping ship to a non-Zope location, and they want their content...
We have all of our content produced in a large CMF based application, but at the very last minute (or at some point soon afterwards) we had to change the delivery tier to a set of static HTML pages. The initial implementation of that feeds this static delivery tier was done with a spidering application. The way this spider was designed to work was for every Zope URL (http://www.example.com/foo/bar) to create a directory $DOCROOT/foo/bar and then write the content into $DOCROOT/foo/bar/index.html. The zope links would remain the same, but the request for /foo/bar would result in a redirect to /foo/bar/ before returning content. As for the problem you mentioned about missing content. Are you using something like cookie crumbler for authentication? Maybe your spider is not keeping and re-sending the cookies.