| {maketoc}
|
| -This package makes content on your site searchable. Currently, wiki pages, blog headers and entries, articles and comments.
|
| -
|
| !Overview
|
| -!!Random Indexing
|
| -The indexing engine in Bitweaver would, every so-many clicks, would pick a random piece of content and index it. (This number of clicks is the "Search Refresh Rate" in administration->search->search settings). This tactic, I presume, is designed to limit index table additions, and prevent the overloading of the server or database engine.
|
| -
|
| -The issue with "random" indexing is that when you submit an article, or wiki page - that page wouldn't necessarily ever get in the index. It is based on chance. If your site had enough traffic, the page would eventually get picked up. For smaller sites, however, this technique fails to deliver expected results - namely, submitted contet should get indexed and be findable using search.
|
| +This package makes all liberty content on your site searchable. Currently this includes articles, wiki pages, blog headers, blog posts and comments. Search is a service and automatically indexes content when the content is saved. The exception is articles which are only indexed after they are approved. |
|
|
| -!!Index On Submit
|
| -There is now In CVS (after the 1.2.1 release) an additional indexing option called "Index On Submit". This causes content to be indexed immediately after it is created (except articles that require approval. That content is indexed only after approval).
|
| +Developers: check SearchPackageDevNotes |
|
|
| -!Search Options
|
| -!!Full Text Search
|
| -This switch isn't used and has been removed
|
| +!Search Settings |
| +Administration -> Search -> Search Settings |
| !!Search Statistics
|
| Record searches made and their frequency. Checking this makes "search statistics" appear on the search admin menu, and gives you access to the statistics page.
|
| -!!Index On Submit
|
| -Described above - forces the index words for the content you are creating or editing to be created or refreshed immediately upon submit.
|
| -!!Search Refresh Rate
|
| -This applies only if you do __not__ have Index On Submit checked. This setting is the number of page reads between a random content piece is chosen and reindexed. There is no control over which content - it is random.
|
| !!Minimum number of letters in search word
|
| Index words that are this number of letters or longer only. I set mine to 4, then words like "the" aren't indexed.
|
| !!Maximum number of words
|
| -This applies to partial word searches. It is the maximum number of words containing a partial word that can be serached for in any one search.
|
| +This applies to partial word searches. It is the maximum number of words containing a "partial word" that can be used in any one search. So, if you type in "three" - search will pick up three and twentythree. That is two - the limit is 100 by default. |
| !!Age in hours of Search cache
|
| Again - applies to partial word searches. It defines the maximum age of cached search results for any given partial word. The results cache will be used to provide a search result if it is available, and will be cleared after either the age, or when the results cache reaches it's limit (LRU List Length)
|
| !!LRU Purging Rate
|
| Applies to partial word searches. LRU = Least Recently Used. Purges the oldest cache entries if there are more than the LRU List length entries every "rate" pages. This will keep space available in the cache for new seach results
|
| !!LRU List Length
|
| -Applies to partial word searches. Limit the results cache to this number of entries. I'd say the 100 default here is pretty low.
|
| +Applies to partial word searches. Limit the results cache to this number of entries. I'd say the 100 default here is pretty low. I set mine to 10000 |
| !!Clear Search Words
|
| Deletes all words from the partial word search cache
|
| !!Delete Index
|