Importing existing flatfile web?
We have here a little web that would be nice to just import to our brand new Zope 2.0 heaven. It's plain html files from a standard Apache system. I've tried Import, but that's obviously for exported objects, not plain files. I've also been at the Add file feature, but that just adds the file... as a file. I should have been as an object as I understand it. Is there a simple way? -- Best regards / Mvh., Steen Suder sysadm kollegie6400.dk GNU - makes me feel better! Ehhh, Linux is GNU, right...?
On Thu, 2 Sep 1999, Steen Suder wrote:
We have here a little web that would be nice to just import to our brand new Zope 2.0 heaven. It's plain html files from a standard Apache system.
I've tried Import, but that's obviously for exported objects, not plain files. I've also been at the Add file feature, but that just adds the file... as a file. I should have been as an object as I understand it. Well, there are basically four ways: 1.) use fsimport.py 2.) use the demo supplied with ZClient, that does the same as a client program. 3.) use ZServer, and FTP access to mirror it with an existing FTP program. 4.) wait 24-48h, I should have an tool ready to do the feat. (Well, at the moment the status for my a bit ambitious website copying tool is: - I'm lacking an argument parser. - I've got only filesystem input and output classes. No problem if the class design is sound. Huge trouble if not. - At the moment it only uses the HREF and SRC attributes of A and IMG. Background images etc. should be trivial. Javascript referenced images are not. Sorry, no concept for this at the moment. - It did work on some fairly complex internal websites here, but YMMV. )
Andreas -- Andreas Kostyrka | andreas@mtg.co.at phone: +43/1/7070750 | phone: +43/676/4091256 MTG Handelsges.m.b.H. | fax: +43/1/7065299 Raiffeisenstr. 16/9 | 2320 Zwoelfaxing AUSTRIA
Hello, I'm checking out Zope, and considering it for some of our websites and projects. While I'm still too new at it to be entirely sure, it looks to me like the dynamic content is put into the database by copying and pasting into the TEXTAREA boxes in the admin interface. I've made dynamic page-posting tools with Perl before, however, and discovered that the HTML components of Netscape Browser (MSIE, too, apparently) have limitations on the amount of data that can be moved via these containers... Does anybody have any more/better information on this, and how it can either be overcome, or else have the control prevent the user from doing something that will result in incomplete transmissions? TIA! ------------------------------ -- Jon S. Jaques --------------- -- Systems Administrator ------- -- Network Publications, Inc. -- ------------------------------
On Thu, 2 Sep 1999, Jon S. Jaques wrote:
I've made dynamic page-posting tools with Perl before, however, and discovered that the HTML components of Netscape Browser (MSIE, too, apparently) have limitations on the amount of data that can be moved via Well, this might be possible, but the practice it seems that real ZOPE sites are usually broken down to smaller components, so nobody was hit with this.
Andreas -- Andreas Kostyrka | andreas@mtg.co.at phone: +43/1/7070750 | phone: +43/676/4091256 MTG Handelsges.m.b.H. | fax: +43/1/7065299 Raiffeisenstr. 16/9 | 2320 Zwoelfaxing AUSTRIA
With an earlier version of Zope (< 1.10.3) we found that some property editing forms lacked the METHOD=POST attribute, which caused the content to be transmitted with GET and hit an even lower browser limitation of URL length. This was fixed in 1.10.3. []s Luciano At 17:46 02/09/99 -0400, Jon S. Jaques wrote:
Hello,
I'm checking out Zope, and considering it for some of our websites and projects.
While I'm still too new at it to be entirely sure, it looks to me like the dynamic content is put into the database by copying and pasting into the TEXTAREA boxes in the admin interface.
I've made dynamic page-posting tools with Perl before, however, and discovered that the HTML components of Netscape Browser (MSIE, too, apparently) have limitations on the amount of data that can be moved via these containers... Does anybody have any more/better information on this, and how it can either be overcome, or else have the control prevent the user from doing something that will result in incomplete transmissions?
TIA!
------------------------------ -- Jon S. Jaques --------------- -- Systems Administrator ------- -- Network Publications, Inc. -- ------------------------------
_______________________________________________ Zope maillist - Zope@zope.org http://www.zope.org/mailman/listinfo/zope
(To receive general Zope announcements, see: http://www.zope.org/mailman/listinfo/zope-announce
For developer-specific issues, zope-dev@zope.org - http://www.zope.org/mailman/listinfo/zope-dev )
Hi, Thanks, everybody, one and all, for all your responses! I wish I had more time tonight to think it through, and, "unfortutunately", tomorrow's my last day before vacation! ;-) Still, though, I'll be considering Zope all the while I'm gone, and will be eager to get back to it once I'm back, in a week. Again, thanks so much for your input, and have a great night! ------------------------------ -- Jon S. Jaques --------------- -- Systems Administrator ------- -- Network Publications, Inc. -- ------------------------------
-----Original Message----- From: zope-admin@zope.org [mailto:zope-admin@zope.org]On Behalf Of Luciano Ramalho Sent: Thursday, September 02, 1999 7:13 PM To: Jon S. Jaques; zope@zope.org Subject: Re: [Zope] Broswer limitations?
With an earlier version of Zope (< 1.10.3) we found that some property editing forms lacked the METHOD=POST attribute, which caused the content to be transmitted with GET and hit an even lower browser limitation of URL length. This was fixed in 1.10.3.
[]s Luciano
At 17:46 02/09/99 -0400, Jon S. Jaques wrote:
Hello,
I'm checking out Zope, and considering it for some of our websites and projects.
While I'm still too new at it to be entirely sure, it looks to me like the dynamic content is put into the database by copying and pasting into the TEXTAREA boxes in the admin interface.
I've made dynamic page-posting tools with Perl before, however, and discovered that the HTML components of Netscape Browser (MSIE, too, apparently) have limitations on the amount of data that can be moved via these containers... Does anybody have any more/better information on this, and how it can either be overcome, or else have the control prevent the user from doing something that will result in incomplete transmissions?
TIA!
------------------------------ -- Jon S. Jaques --------------- -- Systems Administrator ------- -- Network Publications, Inc. -- ------------------------------
_______________________________________________ Zope maillist - Zope@zope.org http://www.zope.org/mailman/listinfo/zope
(To receive general Zope announcements, see: http://www.zope.org/mailman/listinfo/zope-announce
For developer-specific issues, zope-dev@zope.org - http://www.zope.org/mailman/listinfo/zope-dev )
_______________________________________________ Zope maillist - Zope@zope.org http://www.zope.org/mailman/listinfo/zope
(To receive general Zope announcements, see: http://www.zope.org/mailman/listinfo/zope-announce
For developer-specific issues, zope-dev@zope.org - http://www.zope.org/mailman/listinfo/zope-dev )
participants (4)
-
Andreas Kostyrka -
Jon S. Jaques -
Luciano Ramalho -
Steen Suder