Indexers

From phpCMS

[edit] Using the full text search engine indexers

[edit] The indexers explained

phpCMS offers three possibilities to create that search index:

Local indexing (also called File Indexer) 

This method directly processes the content of the content files. The disadvantage is that contents from the template(s) and possibly integrated dynamic elements will not be included into the index. The advantage on the other hand is that the indexing process is very fast and simple to handle.

HTTP indexing via a browser (also called HTTP Indexer) 

The HTTP indexer works the same way as a web based search engine as it retrieves the content via the HTTP protocol. Therefore it sees the output of phpCMS in exact the same way as users of your website. This makes it possible to include contents from the template(s) and from dynamic elements into the index. The indexer follows every link on the indexed pages unless a link has been excluded expressively (pay attention to the robots meta tag!) or is pointing to an external server. After the indexer has fetched and saved all pages the actual indexing process starts and extracts the contained text into the index. The HTTP Indexer is significantly slower than the File Indexer.

HTTP indexing via shell access (also called HTTP Indexer) 

Here the indexer works like the variant above over a browser interface but without constantly refreshing the display so that this method of HTTP indexing is faster than the one before. In order to be able to use this method one either has to have shell access to the web space or work on a local installation of phpCMS. In the latter case the created index files have of course to be uploaded to the web space once the indexing process has finished.