Frequently Asked Questions

 


  • Can I configure Webglimpse to work with Softcart and Google Analytics?

 

Yes, Webglimpse can be used with Softcart and Google Analytics, you can find the configuration information in our how-to's section.

  • I have forgotten my webglimpse administrator password, how can I reset it?

 

If you have forgotten the webglimpse administrator password, you can set a new one using the htpasswd utility that comes with apache webserver. Run:
   htpasswd /[webglimpse_home]/.wgpasswd [newuser]  
 You will need to run this command as the user that installed the program, or as root. You can also add additional admin users if desired.

  • I use image maps on my site, can I still index them?

 

Yes, "Traversing links" means following <A HREF...> and similar tags, just as if the program were a user clicking on links on the page. <FRAME> and <IMAGEMAP> tags are also traversed.

  • Can I convert HTML codes to upper-ASCII characters for indexing?

 

Yes, support for upper-ASCII characters is built into Webglimpse 2.1.01 and above; no manual changes are necessary.

  • I have a very large database that I need to index. Can I prefilter to speed up the search times?

 

Absolutely! Webglimpse 2.7.4 and above has a new setting that allows prefiltering of PDF and even HTML files, greatly increasing search speed for large indexes.

  • I originally installed the edu version but I would like to upgrade to get the custom modules. How do I do this?

  You should view our licensing page to determine which license you should purchase.
  • I'm trying to index only part of a web page, but nothing I try works. How can I do this?

 

Currently we can only configure to exclude whole documents, by adding a

Deny [regexp]

line to the .wgfilter-index file.

However, you can edit the script that pre-processes the files for indexing
(specified in .glimpse_filters), and modify the code to skip
<noindex>...</noindex> sections. If you have Webglimpse 2.13.2 or above, you
should have a library module named wgFilter.pm that has a function called
SkipSection that will help do what you want. Use htfilter.pl in place of
htuml2txt.pl, and add a line such as

&SkipSection("<noindex>","</noindex>",\@lines)

right before the main @lines loop.

  • I see that in the glimpse man pages you can use the -f or -F options to specify a pattern in the filenames. Is it possible to have similar functionality with webglimpse? If so, how do I do it?

 

Just use an input tag named 'filter'. For example:

Search Directory:<SELECT NAME="filter">

<OPTION VALUE="^/my/docroot/"> Whole site
<OPTION VALUE="^/my/docroot/dir1/">Dir 1
<OPTION VALUE="^/my/docroot/dir/2">Dir 2
...
</SELECT>

  • I am having difficulty figuring out how to properly configure my subdirectory index so it will return the correct URL, including the name of the subdirectory in which the search starts. Where do I start?

 

The key is to correctly configure the DocumentRoot for your domain. You can do this thru the web-ministration interface by pressing the 'Configure Local Domain' button, or directly edit the wgsites.conf file in the archives directory, by default that is /usr/local/wg2/archives.

Once the DocumentRoot setting is correct, then the directory paths will be translated to URLs automatically. You can actually test URL->filename translations by using the "Test Path Translations" button at the bottom of the main administration screen.

  • I don't understand how to make my Webglimpse application use a ranking order for the search results.
 

Glimpse actually does not use any ranking algorithm, except for ordering by most recent first. Webglimpse allows the administrator to create their own ranking formula based on the available variables in the .wgrankhits.cfg file. For more details view the Configuring and Customizing section on supporting metatags.

  • I'm having some indexing problems, what is the best way to debug?
 

To debug your search results, try viewing the source code of the results web page to get the actual glimpse command line, and test it from a shell.

In the source, you will see a line like this

<!-- Glimpse command: /usr/local/bin/glimpse -U -W -j -y -i -w -H /home/wgdemo/3 'test' | -->

You may cut and paste the actual command into a shell like so:

/usr/local/bin/glimpse -U -W -j -y -i -w -H /home/wgdemo/3 'test'

  • I've edited my .wgfilter-index file to include several allow/deny lines, but it only seems to work with the first few lines, why?
 

The most common misconception involving the .wgfilter-index file is about the combination of
allow and deny. It works this way: the first matching Allow or Deny applies at which point reading of the file stops. Consequently, later Allow or Deny lines will not have any affect if an earlier line is matched.