FP Search component

How do I keep the FP (2002) search component from searching certain folders.
For instance, my web has a Webalizer usage log analyzer folder and search
will often turn up a whole slew of usage logs that web visitors can view.
Not that I mind, but it clouds the issue when the search returns 12
different logs in the results.

How is your web set up on the server when viewed in File Manager using the Web Masters Control
panel??
The reason I ask is that the webalizer logs are normally kept in a folder named tmp in a password
protected area above / outside the root of the web, and are not "normally" accessible from the root
folder containing the web.

Assuming an Apache/UNIX server, the root folder containing your web should be named: public_html

--
Steve Easton
Microsoft MVP FrontPage
95isalive
This site is best viewed............
........................with a computer

"Mike" <mfjanke@nospam.hotmail.com> wrote in message
news:sJZud.1170$Yj4.1097@newsread3.news.atl.earthlink.net...
> How do I keep the FP (2002) search component from searching certain folders.
> For instance, my web has a Webalizer usage log analyzer folder and search
> will often turn up a whole slew of usage logs that web visitors can view.
> Not that I mind, but it clouds the issue when the search returns 12
> different logs in the results.
>
>

If the server supports subwebs, convert the webalizer folder into a subweb.
Open the online web in FrontPage, right-click and choose "Convert to web".
Check with your host that the conversion will not affect the Webalizer
program first.

--
Ron Symonds (Microsoft MVP - FrontPage)
Reply only to group - emails will be deleted unread.


"Mike" <mfjanke@nospam.hotmail.com> wrote in message
news:sJZud.1170$Yj4.1097@newsread3.news.atl.earthlink.net...
> How do I keep the FP (2002) search component from searching certain
> folders.
> For instance, my web has a Webalizer usage log analyzer folder and search
> will often turn up a whole slew of usage logs that web visitors can view.
> Not that I mind, but it clouds the issue when the search returns 12
> different logs in the results.
>
>

I should have updated this post a bit before I reposted it (it got no
answers two weeks ago). I'll explain why shortly.

The folder was just a plain old folder called "Webalizer" that was below the
root, just like the "images" folder and others. I am on an Apache/UNIX
server btw. This folder was created automatically when I enabled Webalizer
in my host's control panel for this sort of thing so I'm not sure I could
have moved or renamed it.

Mine is just a "hobby" site of sorts, so I had no major need for Webalizer
and I disabled it and deleted that folder completely over a week ago.
However, my searches STILL return links to webalizer log files, though they
haven't existed for a week and clicking on those links returns a 404 error.

What does it take for Frontpage to rebuild its search index, if it even uses
that sort of thing?

mike


"Steve Easton" <admin@95isalive.com> wrote in message
news:uzhEZRG4EHA.2316@TK2MSFTNGP15.phx.gbl...
> How is your web set up on the server when viewed in File Manager using the
> Web Masters Control
> panel??
> The reason I ask is that the webalizer logs are normally kept in a folder
> named tmp in a password
> protected area above / outside the root of the web, and are not "normally"
> accessible from the root
> folder containing the web.
>
> Assuming an Apache/UNIX server, the root folder containing your web should
> be named: public_html

Open the live/remote site directly in FP, then run Tools | Recalculate Hyperlinks.

--
==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
WEBMASTER Resources(tm)
http://www.ycoln-resources.com
FrontPage Resources, WebCircle, MS KB Quick Links, etc.
==============================================
To assist you in getting the best answers for FrontPage support see:
http://www.net-sites.com/sitebuilder/newsgroups.asp

"Mike" <mfjanke@nospam.hotmail.com> wrote in message
news:C%4vd.1693$2J2.578@newsread2.news.atl.earthlink.net...
>I should have updated this post a bit before I reposted it (it got no answers two weeks ago). I'll
>explain why shortly.
>
> The folder was just a plain old folder called "Webalizer" that was below the root, just like the
> "images" folder and others. I am on an Apache/UNIX server btw. This folder was created
> automatically when I enabled Webalizer in my host's control panel for this sort of thing so I'm
> not sure I could have moved or renamed it.
>
> Mine is just a "hobby" site of sorts, so I had no major need for Webalizer and I disabled it and
> deleted that folder completely over a week ago. However, my searches STILL return links to
> webalizer log files, though they haven't existed for a week and clicking on those links returns a
> 404 error.
>
> What does it take for Frontpage to rebuild its search index, if it even uses that sort of thing?
>
> mike
>
>
> "Steve Easton" <admin@95isalive.com> wrote in message
> news:uzhEZRG4EHA.2316@TK2MSFTNGP15.phx.gbl...
>> How is your web set up on the server when viewed in File Manager using the Web Masters Control
>> panel??
>> The reason I ask is that the webalizer logs are normally kept in a folder named tmp in a password
>> protected area above / outside the root of the web, and are not "normally" accessible from the
>> root
>> folder containing the web.
>>
>> Assuming an Apache/UNIX server, the root folder containing your web should be named: public_html
>
>

If, when you enabled webalizer it created a folder inside your web "root," your host does *not* have
the server / webalizer program / control panel configured correctly.


--
Steve Easton
Microsoft MVP FrontPage
95isalive
This site is best viewed............
........................with a computer

"Mike" <mfjanke@nospam.hotmail.com> wrote in message
news:C%4vd.1693$2J2.578@newsread2.news.atl.earthlink.net...
> I should have updated this post a bit before I reposted it (it got no
> answers two weeks ago). I'll explain why shortly.
>
> The folder was just a plain old folder called "Webalizer" that was below the
> root, just like the "images" folder and others. I am on an Apache/UNIX
> server btw. This folder was created automatically when I enabled Webalizer
> in my host's control panel for this sort of thing so I'm not sure I could
> have moved or renamed it.
>
> Mine is just a "hobby" site of sorts, so I had no major need for Webalizer
> and I disabled it and deleted that folder completely over a week ago.
> However, my searches STILL return links to webalizer log files, though they
> haven't existed for a week and clicking on those links returns a 404 error.
>
> What does it take for Frontpage to rebuild its search index, if it even uses
> that sort of thing?
>
> mike
>
>
> "Steve Easton" <admin@95isalive.com> wrote in message
> news:uzhEZRG4EHA.2316@TK2MSFTNGP15.phx.gbl...
> > How is your web set up on the server when viewed in File Manager using the
> > Web Masters Control
> > panel??
> > The reason I ask is that the webalizer logs are normally kept in a folder
> > named tmp in a password
> > protected area above / outside the root of the web, and are not "normally"
> > accessible from the root
> > folder containing the web.
> >
> > Assuming an Apache/UNIX server, the root folder containing your web should
> > be named: public_html
>
>

> Open the live/remote site directly in FP, then run Tools | Recalculate
> Hyperlinks.

Thanks, I'll do that right away.

> If, when you enabled webalizer it created a folder inside your web "root,"
> your host does *not* have
> the server / webalizer program / control panel configured correctly.

I'll go on their support forum and give 'em hell.