automating replacement of webbots

[Sterling]

I'm trying to figure out a way of replacing webbots with
the actual code as I have users edit a site on one server
(which uses webbots) then with a nightly job I move the
site to another server. Once the pages are moved into
production, the webbots break unless if you run the
OWSADM -recalc command line at the new location. Working
with a site of ~10,000 pages - a gig plus in size which
takes time to run these process.

Ideas?

 

[Steve Easton]

Since no one has answered I'll take a stab at it.
1 Does the production server have Extensions installed??
2. If so, how are you "moving" the update to the
productions server??

If the answer to 1 is yes, the answer to 2 "must"
be http:// so as to preserve the extensions and not
break the web-bots.

hth

 

[Stefan B Rusynko]

FP webbot are either Design (applied at file save) or run time (executed by the FP SE) tools, which all require the web to be opened
and either applied in a specific web or "redone" using Tools Recalculate Hyperlinks (which updates any pages using the webbots -
resaves or executes).
A Publish web does the same

PS
IMHO if the web is 10K page it should be broken into several smaller subwebs




| I'm trying to figure out a way of replacing webbots with
| the actual code as I have users edit a site on one server
| (which uses webbots) then with a nightly job I move the
| site to another server. Once the pages are moved into
| production, the webbots break unless if you run the
| OWSADM -recalc command line at the new location. Working
| with a site of ~10,000 pages - a gig plus in size which
| takes time to run these process.
|
| Ideas?