Login / Status
developer.Resource
Home . Documentation . Document Library . Extension Manuals
Sponsors
hosted by punkt.deTYPO3 and Open Source Magazine

1.1.Introduction Table Of Content 1.3.Executing the queue

1.2. Configuration

Extension Manager Configuration

A lot of options were added to the extension manager configuration, that allow settings to improve and enable new crawler features:

Configuration records

Formerly configuration was done by using page ts (see below). This is still possible (fully backwards compatible) but not recommended. Instead of writing pagets simply create a configuration record (table: tx_crawler_configuration) and put it on the topmost page of the pagetree you want to affect with this configuration.

The fields in these records are related to the page ts keys described below. The “name” fields corresponds to the “key” in the pagets setup.

Page TSconfig Reference (tx_crawler.crawlerCfg)

Property:

Data type:

Description:

Default:

paramSets.[key]

string

Get Parameter configuration. The values of GET variables are according to a special syntax. From the code documentation (class.tx_crawler_lib.php):

  1. Basically: If the value is wrapped in [...] it will be expanded according to the following syntax, otherwise the value is taken literally

  2. Configuration is splitted by "|" and the parts are processed individually and finally added together

  3. For each configuration part:

    1. "[int]-[int]" = Integer range, will be expanded to all values in between, values included, starting from low to high (max. 1000). Example "1-34" or "-40--30"

    2. "_TABLE:” in the beginning of string indicates a look up in a table. Syntax is a string where [keyword]:[value] pairs are separated by semi-colon. Example "_TABLE:tt_content; _PID:123"

      1. Keyword “_TABLE” (mandatory, starting string): Value is table name from TCA to look up into.

      2. Keyword “_PID”: Value is optional page id to look in (default is current page).

      3. Keyword “_FIELD”: Value is field name to use for the value (default is uid).

      4. Keyword “_PIDFIELD”: Optional value that contains the name of the column containing the pid. By default this is “pid”.

      5. Keyword “_ENABLELANG”: Optional flag. If set only the records from the current language are fetched.

    3. - Default: Literal value

Examples:

&L=[|1|2|3]
&L=[0-3]
&L=[0-3]&contentId=[_TABLE:tt_content]
paramSets.[key].procInstrFilter
string
List of processing instructions, eg. “tx_indexedsearch_reindex” from indexed_searchto send for the request. Processing instructions are necessary for the request to perform any meaningful action, since they activate third party activity.
paramSets.[key].procInstrParams.[procIn.key].[...]
strings
Options for processing instructions. Will be defined in the respective third party modules.
Examples:
.....procInstrParams.tx_staticpub_publish.includeResources=1
paramSets.[key].pidsOnly
list of integers (pages uid)
List of Page Ids to limit this configuration to
paramSets.[key].userGroups
list of integers (fe_groups uid)
User groups to set for the request.
paramSets.[key].cHash
boolean
If set, a cHash value is calculated and added to the URLs.
paramSets.[key].baseUrl
string
If not set, t3lib_div::getIndpEnv('TYPO3_SITE_URL') is used to request the page.
MUST BE SET if run from CLI (since TYPO3_SITE_URL does not exist in that context!)
[Page TSconfig: tx_crawler.crawlerCfg]
Example
tx_crawler.crawlerCfg.paramSets.test = &L=[0-3]&contentId=[_TABLE:tt_content]
tx_crawler.crawlerCfg.paramSets.test {
procInstrFilter = tx_indexedsearch_reindex
}



				

					

						

							1.1.Introduction
							Table Of Content
							1.3.Executing the queue