re: Search form website

From: Mark Mesarch (anonymous_at_discussions.microsoft.com)
Date: 05/14/04


Date: Fri, 14 May 2004 16:34:54 -0700

Jim,
Thanks for the help.
YOu were right I was not trying the http://URL and that
worked. AT least to get into the page with the way I
expected to see to select options.

I chose "the entire website" as my option. As you said
below that it does not matter where the index is storing
the info as long as it is on the server. It is on the
server in a different drive. Does that matter?
What if we have numerous websites being housed on that
server and each has its own indexing being done. I would
think that if you said the search page can find the index
for a particular website...it would be able to find the
correct one for each website. IS that right?
Thanks again,
Mark
>-----Original Message-----
>>-----Original Message-----
>>I can not seem to get the Search Web Component to work
on
>>my website. I have a working area website on a
>>different computer than my server and I publish to the
>>server. I am using FP 2002.
>>
>>I followed the steps in FP Help but there seems to be an
>>important part missing that the Help says to do. ON the
>>12 Step where is says "In the Scope of search results
>>section, select where the search engine should
search."
>>I do not see anything like this. All I see are two
major
>>sections called Results: and Display Options:
>
>This is because the page was last saved on a machine
where
>Microsoft Indexing service wasn't installed. In the
>absence of Indexing Service, FrontPage uses its own, less
>capable search engine.
>
>If you save the page on a machine where Indexing Service
>isn't present, and then publish it, the search form will
>still be configured to use the FrontPage search engine.
To
>get the page configured for Indexing Service, you have to
>open your remote Web site using an http:// URL, open the
>Web Search page, and then save it.
>
>>It seems that I am not being able to tell the search
>>where to find the index on the server. ( I have checked
>>the server and we are indexing the site.)
>
>Right. The FrontPage search engine doesn't have this
>capability, so in that form of the dialog box, the option
>doesn't appear.
>
>>Instead of working on the remote site, I tried to work
>>directly on the live site. I put a web component on a
>>page and looked and did not see options that I am
suppose
>>to see.
>
>Are you sure you opened your site via an http:// URL, and
>not by means of a file share?
>
>>I found that I had an old version of a search in this
>>area and I openned that file. Low and Behold it had the
>>option I was suppose to see. I tried this and set
>>it "The Web" and it did not work.
>
>The Scope Of Search Results setting is supposed to be a
>folder name: the one at the root of the area you want to
>search.
>
>Unless you have a folder named "The Web", that name won't
>work.
>
>> Now I get a message that says I am trying to use a Web
>> Component and I must publish this page and not work on
>> it directly. So it seems I am running into circular
>> logic.
>
>This usually means you opened your site as a file share.
>You need to open it using an http:// URL.
>
>>I side issue that may be a concern is that our system
>>administrator is having the indexing stored on a
>>different drive on the same server than where the
>>website actually is. Am I going to have to have the
>>indexing stored on the same drive or even within the
>>website for this to work?
>>
>>Any help would be great.
>>Mark
>
>No, it doesn't matter where the index physically resides,
>as long as it's on the same server. The FrontPage Web
>Search component will communicate with Indexing Service
>and find the catalog (if any) that includes your site.
>
>Jim Buyens
>Microsoft FrontPage MVP
>http://www.interlacken.com
>Author of:
>*----------------------------------------------------
>|\---------------------------------------------------
>|| Microsoft Office FrontPage 2003 Inside Out
>||---------------------------------------------------
>|| Web Database Development Step by Step .NET Edition
>|| Microsoft FrontPage Version 2002 Inside Out
>|| Faster Smarter Beginning Programming
>|| (All from Microsoft Press)
>|/---------------------------------------------------
>*----------------------------------------------------
>
>.
>



Relevant Pages

  • Re: Basic Authentication + IIS 5 + Windows 2000 + Frontpage 2002 = failure?
    ... By this, I mean, usually, on the basic logon screen of a server, I see ... >;) under the website in question, enabling only Basic authentication. ... > - When testing with IE or FrontPage local to the webserver for a baseline ... From a website perspective, I ...
    (microsoft.public.inetserver.iis.security)
  • RE: Basic Authentication + IIS 5 + Windows 2000 + Frontpage 2002 = failure?
    ... ;) under the website in question, enabling only Basic authentication. ... IE (and FrontPage too, if I am not mistaken) will interperate the ... lets configure the server extensions on this VDIR....select the ... From a website perspective, I ...
    (microsoft.public.inetserver.iis.security)
  • Re: frontpage intranet migration website strategy with a twist
    ... decent experience with Frontpage and publishing to third party WWW ... I have a newly integrated Small Business Server 2003 and I'm ... trying to publish a website via FrontPage. ... Opening IIS and creating a new website using server ip address, ...
    (microsoft.public.frontpage.client)
  • Re: Problems with the "Search" webbot
    ... Microsoft MVP - FrontPage ... Install Indexing service through Add/Remove Windows Components. ... Create a catalog and point this catalog to the FPSE enabled web site. ... |> server, also ensure that Indexing service is allowed in the Web server ...
    (microsoft.public.frontpage.client)
  • Re: Search form website
    ... You need to try posting in the index server newsgroup to get better answers. ... Tom Pepper Willett [Microsoft MVP - FrontPage] ... Microsoft FrontPage: ... |>Microsoft Indexing service wasn't installed. ...
    (microsoft.public.frontpage.programming)