Re: can WC render sites out?
This WebDNA talk-list message is from 1997
It keeps the original formatting.
numero = 10706
interpreted = N
texte = >We're building a big travel/tourism site and want do the whole thing in >WebCatalog but we want WC to write out files to disk so we can serve >them conventionally. Like Frontier's Render Site. Our thinking is >that using a WC database to store each page element will allow us to >build a form that will give secretary-level, password protected control >of the text of each page of the site with very minimum training--a great >selling point, ultimate easy control of the content. However, we've >been pretty frustrated in getting WC sites indexed in directories >because the guts of a WC site stay burried in the database out of the >reach of robots. So, we'd prefer to have WC render the site out every >time the dabase gets edited, overwriting the old files with the newly >rendered pages. This way you get the flexibility of WC and a fully >indexed site. > >Anyone have any ideas on how to implement this or why it makes sense not >to?It makes sense, and it can be done. Here's one feature you will use a lot, it's called [WriteFile]:To write text to an arbitrary text file, put a [WriteFile] context into a template. WriteFile creates a new file if one does not exist already, and erases any existing text if the file was already there. The file should not be a database file that WebCatalog currently has open.Read the html docs for this and lots of other valuable information, too ... :)Sincerely, Ken
Associated Messages, from the most recent to the oldest:
>We're building a big travel/tourism site and want do the whole thing in >WebCatalog but we want WC to write out files to disk so we can serve >them conventionally. Like Frontier's Render Site. Our thinking is >that using a WC database to store each page element will allow us to >build a form that will give secretary-level, password protected control >of the text of each page of the site with very minimum training--a great >selling point, ultimate easy control of the content. However, we've >been pretty frustrated in getting WC sites indexed in directories >because the guts of a WC site stay burried in the database out of the >reach of robots. So, we'd prefer to have WC render the site out every >time the dabase gets edited, overwriting the old files with the newly >rendered pages. This way you get the flexibility of WC and a fully >indexed site. > >Anyone have any ideas on how to implement this or why it makes sense not >to?It makes sense, and it can be done. Here's one feature you will use a lot, it's called
[writefile]:To write text to an arbitrary text file, put a
[writefile] context into a template. WriteFile creates a new file if one does not exist already, and erases any existing text if the file was already there. The file should not be a database file that WebCatalog currently has open.Read the html docs for this and lots of other valuable information, too ... :)Sincerely, Ken
Kenneth Grome
DOWNLOAD WEBDNA NOW!
Top Articles:
Talk List
The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...
Related Readings:
SuperFlush stumped on simple sort (1999)
[shell]? (2000)
Digest for 4/18/97 (1997)
Sort & Shownext (1999)
$Quit, $CloseDatabase corrections (1997)
WC2b15 - [HTMLx]...[/HTMLx] problems (1997)
Ampersands in database fields? (1998)
Buying sans cart (1997)
date (2002)
WC2.0 Memory Requirements (1997)
Problem (1997)
[WebDNA] feature request (2011)
2 easy questions re: [showif] and [sendmail] (1997)
with Link i need to (1997)
Client-side Image Maps and WebCat? (1998)
[WAY OFF TOPIC] anybody live in Kansas? (2003)
Preloading code? (2002)
using showpage and showcart commands (1996)
Searching for words equal to A or equal to B (1999)
Include a big block of text (1997)