Platinum sponsors
Extension Key: mnogosearch
Copyright 2000-2002, Dmitry Dulepov, <dmitry@typo3.org>
This document is published under the Open Content License
available from http://www.opencontent.org/opl.shtml
The content of this document is related to TYPO3
- a GNU/GPL CMS/Framework available from www.typo3.com
Warning! This manual is incomplete. Current version provides minimum information enough to install, configure and run mnoGoSearch on target system. Manual will be extended in future with tips, better instructions and more details about configuration and optimization.
This extension is intended to replace indexed search extension for medium-to-large web sites. It provides better performance and superior features not found in indexed search.
This extensions makes use of two external components:
mnoGoSearch engine
mnoGoSearch PHP extension
See below for description of these components.
Extension also provides a CLI (shell, command line) script that takes care of reindexing pages that were modified by editors. This script should be executed as cron job. See section "Installing mnoGoSearch cron script" later in this document for more information.
mnoGoSearch engine is a standalone set of applications that provide indexing capabilities for various content types. mnoGoSearch engine has a long history and used on a number of large web sites (for example, at http://www.mysql.com/). It must be compiled and installed on the server before installing mnoGoSearch PHP and TYPO3 extensions. See section "Compiling and installing mnoGoSearch engine" later in this document.
mnoGoSearch TYPO3 extension makes use of mnoGoSearch PHP extension. PHP extension extends PHP with additional functions that enable to query mnoGoSearch engine for searhed words and returning results. PHP extension must be downloaded, compiled and installed on the server before mnoGoSearch TYPO3 extension is installed to TYPO3.
finding word forms (if Ispell files for web site language is installed)
use search operators (& | ~) for search
full phrase search
indexes only parts of the page that should be indexed
unlike indexed search, properly handles elements that should not be indexed
