Hi all, I'm willing to make my site in Zope. I see several benefits from it. And I will use it at my own server... but, unfortunately, our hospital wants to place some pages also on another server.... and yes.... they don't want to use Zope... :-(((. So is it possible... To convert my Zope pages to some plain html files? e.g. a page which inherits the header and footer of a parent folder --> in webpage they will be combined to one page... Is this possible? It will help me a lot. Then I can continue to design my pages in Zope. And later on, confice other webservers to use Zope. But until then I can give them plain easy html-pages.... Thanks in advance, Tom.
The standard answer is to use a html-mirror script or program which asks the Zopeserver for all pages recursivly. less /MY/INSTALL/Python-1.5.2b2/Tools/webchecker/websucker.py a nearby solution :-) or wget HTH __Janko Tom Deprez writes:
Hi all,
I'm willing to make my site in Zope. I see several benefits from it. And I will use it at my own server... but, unfortunately, our hospital wants to place some pages also on another server.... and yes.... they don't want to use Zope... :-(((.
So is it possible... To convert my Zope pages to some plain html files?
e.g. a page which inherits the header and footer of a parent folder
--> in webpage they will be combined to one page...
Is this possible?
It will help me a lot. Then I can continue to design my pages in Zope. And later on, confice other webservers to use Zope. But until then I can give them plain easy html-pages....
Thanks in advance,
Tom.
_______________________________________________ Zope maillist - Zope@zope.org http://www.zope.org/mailman/listinfo/zope
(For developer-specific issues, use the companion list, zope-dev@zope.org - http://www.zope.org/mailman/listinfo/zope-dev )
If the only thing you are using Zope to accomplish is the "Web Object" style of assembling static HTML displays, the easiest solution might be to simply use a web site mirroring program to "copy" your site. Unfortunately, this restricts you to a very limited subset of the Power of Zope. On Thu, 8 Apr 1999, Tom Deprez wrote:
I'm willing to make my site in Zope. I see several benefits from it. And I will use it at my own server... but, unfortunately, our hospital wants to place some pages also on another server.... and yes.... they don't want to use Zope... :-(((.
So is it possible... To convert my Zope pages to some plain html files?
e.g. a page which inherits the header and footer of a parent folder
--> in webpage they will be combined to one page...
Is this possible?
It will help me a lot. Then I can continue to design my pages in Zope. And later on, confice other webservers to use Zope. But until then I can give them plain easy html-pages....
I'm willing to make my site in Zope. I see several benefits from it. And I will use it at my own server... but, unfortunately, our hospital wants to place some pages also on another server.... and yes.... they don't want to use Zope... :-(((.
So is it possible... To convert my Zope pages to some plain html files?
Zope is highly scriptable, so wouldn't it in theory be possible to write something that let's you "publish" your site to say, an FTP server, as static files? I'm really new to Zope and don't know Python (yet) and am trying to get my mind around this. I spent some time using Frontier and before it went hog wild into dynamic publishing, it was basically a really nice templating tool (Ok, it was more than that, but for web developers....). You created all your pages and lots of embedded code and other objects in your Frontier database, which is similar to the Zope DB. Then you did a "publish site" on your tree in the database. The program rendered a series of static HTML pages and images and whatever else you had onto your hard drive which you could then upload via FTP. With version 5 and now 6, Frontier has moved to something that is more like Zope. But couldn't Zope move backwards a bit and work like Frontier does for those who need it? I can see quite a few uses for this. Zope is your development tool, but not your delivery mechanism. This would be really useful because now I can use Zope for more clients and more situations. Something like this could be useful for other tasks as well. Such as automatically taking content from a Zope site and sending to somewhere else (mail, ftp, andother WebDAV server, CVS, etc). I'm quite sure it can be done, but I don't know if it already has, but if not, I don't have enough Zope knowledge to even attempt it. _______________________________________________________________ karl fast fast@lights.com
In article <Pine.LNX.4.05.9904082320410.29143-100000@northern.lights.com>, Karl Fast <fast@lights.com> wrote:
Zope is highly scriptable, so wouldn't it in theory be possible to write something that let's you "publish" your site to say, an FTP server, as static files?
You wouldn't even need Zope's scriptability to do this. Something like "wget" would do. Just point it at the main page, and it will mirror everything to a local filesystem.
Zope is highly scriptable, so wouldn't it in theory be possible to write something that let's you "publish" your site to say, an FTP server, as static files?
You wouldn't even need Zope's scriptability to do this. Something like "wget" would do. Just point it at the main page, and it will mirror everything to a local filesystem.
Hmm, but isn't the big problem with all of this that zope doesn't use your standard .html, .gif, etc. extensions for it's URL's. This is something kind of bothers me a bit. Suppose I have a site and I want to move it to Zope to make it easier to manage. But I have a lot of people who visit my site and may have bookmarked various pages. I don't want my URL's to break because that means lost eyeballs, and depending on what I'm doing, lost business. Now I understand I can make zope respond to things like /index.html or /News/hello.gif, but doesn't this require some tricks. I mean, names like file.html isn't "the zope way", is it? So to use things like "wget" or curl or something like that, I need to do some pretty careful planning before I get started. Am I right, or is my zope newbie status simply out of control here <g>.
On Fri, 9 Apr 1999, Karl Fast wrote:
Hmm, but isn't the big problem with all of this that zope doesn't use your standard .html, .gif, etc. extensions for it's URL's. [snip]
I was wondering why the ORB couldn't try to resolve the . in the name as an _ by default?? This way index.html would retrieve index_html, foo_gif would be foo.gif as a URL and everyone would be happy! ------- Jordan B. Baker -- jbb@spyderlab.com weaving the web @ http://www.spyderlab.com
participants (6)
-
jhauser＠ifm.uni-kiel.de -
Jordan B. Baker -
Karl Fast -
Richard Wackerbarth -
Tom Deprez -
tsarna＠endicor.com