Search engine problems
Sun, 2 Dec 2001 12:17:39 -0600
Hah! Solved my own problem. The solution is the Searching element in the
ARTS & FARCES LLC
3D85 F3F4 9E65 4949 176A 260C CB47 190D C864 9A96
> -----Original Message-----
> From: Michael Fraase [mailto:firstname.lastname@example.org]
> Sent: Saturday, December 01, 2001 10:02 PM
> To: 'email@example.com'
> Subject: RE: Search engine problems
> (Sorry if this is a double post--the first didn't have a
> subject line, and I figured the server kicked it.)
> I deleted the Index.root file.
> Then I followed the instructions at:
> Specifically, here's what I did:
> 1. Opened manilaWebsites.root
> 2. Opened the website to index
> 3. Opened the #tools table
> 4. Selected New Script from the Table menu
> 5. Gave the script the name of initialIndex
> 6. Pasted in the script
> 7. Received a variety of script errors (too many parameters,
> syntax error)
> depending upon how I pasted the script in.
> > You could delete your index.root file and re-index your
> sites. That's
> > probably easiest.
> > -Brent
> >> At 5:30 PM -0600 12/1/01, Michael Fraase wrote:
> >> I'm having problems with Frontier's search engine. While I was
> >> prototyping our sites, I had Frontier running on port 88. I got
> >> everything working and changed Frontier to port 80 (that was
> >> something of an ordeal in itself).
> >> The problem, as you can imagine, is that all of the content pages
> >> were indexed when Frontier was running on port 88. All the search
> >> engine results contain double references for each "hit"
> (one for the
> >> object when it was on port 88; and one for the object on port 80).
> >> How can I get rid of the "hits" on port 88?
> >> Thanks.
> Michael Fraase
> ARTS & FARCES LLC
> PGP Fingerprint:
> 3D85 F3F4 9E65 4949 176A 260C CB47 190D C864 9A96