View Full Version : Perfect Search Problem

09-07-2004, 11:01 PM
Perfect Search is not indexing down through all my sub-directories.
I have less than the 100 maximum pages so that should not be the problem. What should I be checking on to determine why certian pages are not being listed on the serach index and therefore not being found when I use the search itself.


09-08-2004, 01:37 AM
Hi mc, welcome to Westhost Forum!

If you found that application in Site Manager, probably you can ask for support by Westhost. You can contact them via this page: http://members.westhost.com/contactus.html

09-08-2004, 01:45 AM
I am using
<!--#include virtual="/menu.htm" -->
I have many pages that are filename.shtml
here is the result I am getting
Ignoring 'http://www.primeparts.net/AllenBradley/abindex.shtml': not below $HTTP_LIMIT_URL or non-http protocol

If you can point me in the right direction I would appreciate it


09-08-2004, 01:53 AM
Thanks for the reply.
However contacting westhost is where I started.
I must say I was surprised and disappointed that they replyed to my contact saying
"We are not able to offer support on third party applications. If you need assistance
with the Perlfect Search application, you may check the Forums
http://forums.westhost.com or check out their Web Site;

Thrilled me since the script is something they provide. I know in days past westhost helped out with scripts they provided but not with ones they didn't provide. That's undersatndable.

I have been with westhost for over 5 years and I keep seeing service slip. Particuallarly in the last year.

Anyhow, thanks for pointin gme in that direction but I have been there and as I say that went no where.


09-08-2004, 02:06 AM
I am sorry I don't know how to solve your problem, but I would contact Westhost again for a second time hoping that another technician could offer some advice.

I had the impression that apps included in Site Manager had some support.

If you are interested to add search in your website, you may like to consider these services of Google: This (http://www.google.com/searchcode.html) and That (http://www.google.com/appliance/).

09-08-2004, 07:21 AM
Hi mc,

I don't use the script much so not real sure but I was reading the users guide (http://www.manual.westhost.com/sitesearch.html) and it mentioned this...
To index dynamic pages, load conf.pl into an editor and set $HTTP_START_URL. That makes me wonder if you want to take a look at that file and see if $HTTP_LIMIT_URL is set to something that that would be affecting it. You might also be able to set the $HTTP_START_URL which may help.

Like I say I don't use it but I do think I have it on my test account and when I get to my main computer I'll take a look at the code and see if can see anything else I think may be keeping the pages from indexing.

You might check and make sure you don't have a robot.txt or meta tags that are in the pages themselves that could be keeping the page(s) from indexing.

09-08-2004, 11:20 AM
Hi mc,

I have been looking into this a bit more. I visited the Perlfect (http://perlfect.com/freescripts/search/) site and checked the FAQ (http://perlfect.com/freescripts/search/faq.shtml). One thing I saw that might help is this answer:

If you are indexing your local filesystem check the values of @EXT in conf.pl and the entries in conf/no_index.txt. If you make changes to those values, you will have to run indexer.pl again. If you are indexing via http, check the following list:
Remember that the script will only find files that are directly or indirectly linked from your start page ($HTTP_START_URL).
If you have pages which are only accessible with Cookies, Java, Javascript, Flash etc enabled, these will not be indexed either. This is not a bug in Perlfect Search but a general problem that other search engines have too. You'll have to rework your pages to also work without Cookies/Java/Javascript/Flash.
Framesets need a proper <noframes> section with correct links.
Perlfect Search only follows links, it does not try to submit forms. So every automatically generated page that should be indexed needs to be accessible via a common link.
If all that does not help, check the values of @HTTP_CONTENT_TYPES and $HTTP_LIMIT_URL and turn on $HTTP_DEBUG to get more debugging output during indexingIn case all that is a bit confusing what I get out of it is to make sure that .shtml is in the @HTTP_CONTENT_TYPES . I still have not been able to look at the code itself but wanted to pass this on. The current documation is for version 3.31b and not sure of the version WH runs but don't think these things have changed if it is an older version.

09-08-2004, 11:33 AM
I found two archived threads on the site by searching the error that may help you out also:


You have to use the Next message link at the top to see the replies to the person that was having problems. The first post has the guys full output but if you go to the reply there are some suggestions to look for.