Search General Settings tab
- Overview
- This tab is the main place to enable and disable search features and attributes
- To Access
- From the Search page, click the General Settings tab.
| Option | Description | Default |
|---|---|---|
| Unified search index | Enables searching for content at the site using a Tiki-managed index. It's recommended to set a cron job to periodically rebuild the search index. |
Enabled |
| Search statistics | Enables administrators to collect and view statistics on search activity. | Disabled |
| Users available in search results | Users available within search results. Content related to the user will be included in the index. None | All | Public |
None |
| Incremental Index Update | Update the index incrementally as the site content is modified. This may lead to lower performance and accuracy than processing the index on a periodic basis. |
Enabled |
| Search index rebuild memory limit | Temporarily adjust the memory limit to use during Search index rebuild. Depending on the volume of data, some large operations require more memory. Increasing it locally, per operation, allows to keep a lower memory limit globally. Keep in mind that memory usage is still limited to what is available on the server. for example: 256M |
None |
| Search index rebuild time limit | Temporarily adjust the time limit to use during Search index rebuild. Depending on the volume of data, some requests may take longer. Increase the time limit locally to resolve the issue. Use reasonable values. | None |
| Unified search engine | Search engine used to index the content of this Tiki site. Some engines are more suitable for larger sites, but require additional software on the server. MySQL full-text search | Elasticsearch | Manticore Search |
MySQL full-text search |
| Elasticsearch URL | URL of any node in the cluster | http://localhost:9200 |
| Elasticsearch index prefix | The prefix that is used for all indexes for this installation in Elasticsearch | Tiki_ |
| Elasticsearch current index | A new index is created upon rebuilding, and the old one is then destroyed. This setting enables seeing the currently active index. Do not change this value unless you know what you are doing. |
None |
| Elasticsearch field limit per index | The maximum number of fields per search index in Elasticsearch version 5.x and above | 1000 fields |
| Relation types to index within object. | Comma-separated relation types for which objects should be indexed in their related objects. Elasticsearch needed |
None |
| Use MySQL Full-Text Search (fallback) | In case of Elasticsearch is active and unavailable, use MySQL Full-Text Search as fallback | Disabled |
| MySQL use short field names | Due to frm file constraints, number of search fields that one index can hold is usually limited to about 1500. This can be exceeded if you have numerous tracker fields. Enabling this option will try to shorten the field names internally that should allow you to use 300-500 more fields. Switching this option requires full index rebuild. | Disabled |
| Restore old MySQL indexes during reindex | If set, after the reindex is performed, old table MySQL indexes will be restored to the reindex related table. | Disabled |
| Manticore URL | URL of the Manticore search server | http://127.0.0.1 |
| Manticore HTTP(S) Port | Port number for the HTTP(S) interface. | 9308 |
| Manticore MySQL Port | Port number for the MySQL interface. | 9306 |
| Manticore index prefix | The prefix that is used for all indexes for this installation in Manticore | Tiki_ |
| Manticore current index | A new set of indexes are created upon rebuilding, and the old ones are then destroyed. This setting enables seeing the currently active index prefix. Do not change this value unless you know what you are doing. |
None |
| Morphology processing | Advanced morphology preprocessors to apply in the Manticore index. See Manticore manual for possible values. | None |
| Manticore indexed full-text fields | Manticore has a hard-limit of 256 full-text indexed fields per index. If your installation has more, some will be indexed as string attributes and perform the slower regex search. You can add a comma-separated list of fields to always index as full-text here. | title,contents |
| Default Boolean Operator | Use OR or AND as the default search operator. AND | OR |
AND |
| Excluded categories | List of category IDs to exclude from the search index | None |
| Excluded plugins | List of plugin names to exclude while indexing | None |
| Exclude all plugins | Indexing will exclude all plugins. | Enabled |
| Except included plugins | List of plugin names that are required to be included while indexing, when excluding all. Example: fancytable,list,trackerlist,trackerfilter | None |
| Don't index non searchable fields | Indexing will skip adding all tracker fields that are not marked as "searchable". This will free index space but also make it impossible to use those fields in search index queries. | Disabled |
| Index forum replies together with initial post | Forum replies will be indexed together with the initial post as a single document instead of being indexed separately. | Enabled |
| Tokenize version numbers | Tokenize version number strings so that major versions are found when sub-versions are mentioned. For example, searching for 2.7 would return documents containing 2.7.4, but not 1.2.7. | Disabled |
| Tokenize CamelCase words | Consider the components of camel-case words as separate tokens, allowing them to be searched individually. Conflicts with Tokenize Version Numbers. |
Disabled |
| Possessive Stemmer | The possessive stemmer removes possessives (trailing "'s") from words before indexing them. | Enabled |
| Field weights | Allow the field weights to be set that apply when ranking pages in the search results. The weight is applied only when the field is in the query. To nullify the value of a field, use an insignificant amount, but not 0, which may lead to unexpected behaviors such as stripping of results. (Add these fields to the "Default content fields" preference below for it to have an effect in a global "content" search) One field per line, field_name:5.3 |
title:2.5 allowed_groups:0.... |
| Default content fields | All of the content is aggregated in the contents field. For custom weighting to apply, the fields must be included in the query. This option allows other fields to be included in the default content search. | contents, title |
| Cache per user and query for Tiki built-in search | Time in minutes a user has a same query cached applied to Tiki built-in search interface only. | 0 minutes |
| Cache result-specific formatted results | Formatted search results such as the ones used in the List plugin will be cached to prevent process-intensive reformatting on each page load. The cache is result-specific. Every different result will generate a separate cache. This could quickly build up a large cache directory. It is recommended to clear Tiki caches often (e.g. once per week) via an automated job if you use this feature. |
Disabled |
| Cache individual search formatters | List of search formatters whose output will be cached. This is separate to the result-specific formatted results cache. | None |
| LIST plugin cache default on | If selected, LIST plugins will be cached by default unless turned off at plugin level. | Disabled |
| LIST plugin cache default expiry | Default number of minutes for LIST plugin cache expiry. | 30 |
| Format to use for tracker field keys | Choose between field IDs and permanent names for the tracker indexing Permanent name | Field ID (backward compatibility mode with Tiki 7 and 8) |
Permanent name |
| Index Tracker Category names | Index the names and paths of category field values Requires reindexing |
Disabled |
| Use unified search in category admin | Use unified search to find objects to add to categories. This limits the types of objects available to those included in the unified index. | Disabled |
| Automatically trim Elasticsearch results on date-sorted query | Automatically trim Elasticsearch results in unified search if the query is sorted by modification or creation date. | Disabled |
| Show error on missing field | When using List plugin to specify certain fields, especially tracker fields, this check helps ensure their names were entered correctly. | Enabled |
| Stop Word List | Words excluded from the search index, because they can be too frequent and produce unwanted results. MySQL full-text search has its own list of stop words configured in the server. |
a, an, and, are, as, at, be... |
| Search index outdated | Number of days to consider the search index outdated | 2 days |
| Automatic indexing of file content | Uses command line tools to extract the information from the files based on their MIME types. | Disabled |
| Automatic indexing of emails stored as files | Parses message/rfc822 types of files (aka eml files) and stores individual email headers and content in search index. | Disabled |
| Asynchronous indexing | Enabled | |
| MySQL full-text search | Also known as 'Basic Search'. This search uses the MySQL full-text search feature. The indexation is continuously updated. | Disabled |
| Referer search highlighting | When a user lands on a Tiki page from a search engine, Tiki highlights the search words they used. Its similar to using Tiki’s search facility. | Enabled |
| Ignore individual object permissions | Display items the user may not be entitled to view in search results. Will improve performance, but may show forbidden results. |
Disabled |
| Ignore category viewing restrictions | Display items the user may not be entitled to view in search results. Will improve performance, but may show forbidden results |
Disabled |
| Autocomplete page names | Automatically complete page names as the user starts typing. For example the user types the start of the wiki page name “Sear” and Tiki returns “Search”, “Search General Settings”, etc | Disabled |
| File thumbnail preview | Have a preview of attachments in search results | Disabled |
| Forum name search | When listing forums | Disabled |
| Forum content search | When listing forums | Enabled |
| Topic content search | Enabled | |
| Unified search for forums and file galleries | Enabled |
| Option | Description | Default |
|---|---|---|
| Unified search index | Enables searching for content at the site using a Tiki-managed index. It's recommended to set a cron job to periodically rebuild the search index. |
Enabled |
| Search statistics | Enables administrators to collect and view statistics on search activity. | Disabled |
| Users available in search results | Users available within search results. Content related to the user will be included in the index. None | All | Public |
None |
| Incremental Index Update | Update the index incrementally as the site content is modified. This may lead to lower performance and accuracy than processing the index on a periodic basis. |
Enabled |
| Search index rebuild memory limit | Temporarily adjust the memory limit to use during Search index rebuild. Depending on the volume of data, some large operations require more memory. Increasing it locally, per operation, allows to keep a lower memory limit globally. Keep in mind that memory usage is still limited to what is available on the server. for example: 256M |
None |
| Search index rebuild time limit | Temporarily adjust the time limit to use during Search index rebuild. Depending on the volume of data, some requests may take longer. Increase the time limit locally to resolve the issue. Use reasonable values. | None |
| Unified search engine | Search engine used to index the content of this Tiki site. Some engines are more suitable for larger sites, but require additional software on the server. MySQL full-text search | Elasticsearch |
MySQL full-text search |
| Elasticsearch URL | URL of any node in the cluster | http://localhost:9200 |
| Elasticsearch index prefix | The prefix that is used for all indexes for this installation in Elasticsearch | Tiki_ |
| Elasticsearch current index | A new index is created upon rebuilding, and the old one is then destroyed. This setting enables seeing the currently active index. Do not change this value unless you know what you are doing. |
None |
| Elasticsearch field limit per index | The maximum number of fields per search index in Elasticsearch version 5.x and above | 1000 fields |
| Relation types to index within object. | Comma-separated relation types for which objects should be indexed in their related objects. Elasticsearch needed |
None |
| Use MySQL Full-Text Search (fallback) | In case of Elasticsearch is active and unavailable, use MySQL Full-Text Search as fallback | Disabled |
| MySQL use short field names | Due to frm file constraints, number of search fields that one index can hold is usually limited to about 1500. This can be exceeded if you have numerous tracker fields. Enabling this option will try to shorten the field names internally that should allow you to use 300-500 more fields. Switching this option requires full index rebuild. | Disabled |
| Restore old MySQL indexes during reindex | If set, after the reindex is performed, old table MySQL indexes will be restored to the reindex related table. | Disabled |
| Default Boolean Operator | Use OR or AND as the default search operator. AND | OR |
AND |
| Excluded categories | List of category IDs to exclude from the search index | None |
| Excluded plugins | List of plugin names to exclude while indexing | None |
| Exclude all plugins | Indexing will exclude all plugins. | Enabled |
| Except included plugins | List of plugin names that are required to be included while indexing, when excluding all. Example: fancytable,list,trackerlist,trackerfilter | None |
| Don't index non searchable fields | Indexing will skip adding all tracker fields that are not marked as "searchable". This will free index space but also make it impossible to use those fields in search index queries. | Disabled |
| Index forum replies together with initial post | Forum replies will be indexed together with the initial post as a single document instead of being indexed separately. | Enabled |
| Tokenize version numbers | Tokenize version number strings so that major versions are found when sub-versions are mentioned. For example, searching for 2.7 would return documents containing 2.7.4, but not 1.2.7. | Disabled |
| Tokenize CamelCase words | Consider the components of camel-case words as separate tokens, allowing them to be searched individually. Conflicts with Tokenize Version Numbers. |
Disabled |
| Possessive Stemmer | The possessive stemmer removes possessives (trailing "'s") from words before indexing them. | Enabled |
| Field weights | Allow the field weights to be set that apply when ranking pages in the search results. The weight is applied only when the field is in the query. To nullify the value of a field, use an insignificant amount, but not 0, which may lead to unexpected behaviors such as stripping of results. (Add these fields to the "Default content fields" preference below for it to have an effect in a global "content" search) One field per line, field_name:5.3 |
title:2.5 allowed_groups:0.... |
| Default content fields | All of the content is aggregated in the contents field. For custom weighting to apply, the fields must be included in the query. This option allows other fields to be included in the default content search. | contents, title |
| Cache per user and query for Tiki built-in search | Time in minutes a user has a same query cached applied to Tiki built-in search interface only. | 0 minutes |
| Cache result-specific formatted results | Formatted search results such as the ones used in the List plugin will be cached to prevent process-intensive reformatting on each page load. The cache is result-specific. Every different result will generate a separate cache. This could quickly build up a large cache directory. It is recommended to clear Tiki caches often (e.g. once per week) via an automated job if you use this feature. |
Disabled |
| Cache individual search formatters | List of search formatters whose output will be cached. This is separate to the result-specific formatted results cache. | None |
| LIST plugin cache default on | If selected, LIST plugins will be cached by default unless turned off at plugin level. | Disabled |
| LIST plugin cache default expiry | Default number of minutes for LIST plugin cache expiry. | 30 |
| Format to use for tracker field keys | Choose between field IDs and permanent names for the tracker indexing Permanent name | Field ID (backward compatibility mode with Tiki 7 and 8) |
Permanent name |
| Index Tracker Category names | Index the names and paths of category field values Requires reindexing |
Disabled |
| Use unified search in category admin | Use unified search to find objects to add to categories. This limits the types of objects available to those included in the unified index. | Disabled |
| Automatically trim Elasticsearch results on date-sorted query | Automatically trim Elasticsearch results in unified search if the query is sorted by modification or creation date. | Disabled |
| Show error on missing field | When using List plugin to specify certain fields, especially tracker fields, this check helps ensure their names were entered correctly. | Enabled |
| Stop Word List | Words excluded from the search index, because they can be too frequent and produce unwanted results. MySQL full-text search has its own list of stop words configured in the server. |
a, an, and, are, as, at, be... |
| Search index outdated | Number of days to consider the search index outdated | 2 days |
| Automatic indexing of file content | Uses command line tools to extract the information from the files based on their MIME types. | Disabled |
| Automatic indexing of emails stored as files | Parses message/rfc822 types of files (aka eml files) and stores individual email headers and content in search index. | Disabled |
| Asynchronous indexing | Enabled | |
| MySQL full-text search | Also known as 'Basic Search'. This search uses the MySQL full-text search feature. The indexation is continuously updated. | Disabled |
| Referer search highlighting | When a user lands on a Tiki page from a search engine, Tiki highlights the search words they used. Its similar to using Tiki’s search facility. | Enabled |
| Ignore individual object permissions | Display items the user may not be entitled to view in search results. Will improve performance, but may show forbidden results. |
Disabled |
| Ignore category viewing restrictions | Display items the user may not be entitled to view in search results. Will improve performance, but may show forbidden results |
Disabled |
| Autocomplete page names | Automatically complete page names as the user starts typing. For example the user types the start of the wiki page name “Sear” and Tiki returns “Search”, “Search General Settings”, etc | Disabled |
| File thumbnail preview | Have a preview of attachments in search results | Disabled |
| Forum name search | When listing forums | Disabled |
| Forum content search | When listing forums | Enabled |
| Topic content search | Enabled | |
| Unified search for forums and file galleries | Enabled |
| Option | Description | Default |
|---|---|---|
| Unified search index | Enables searching for content at the site using a Tiki-managed index. It's recommended to set a cron job to periodically rebuild the search index. |
Enabled |
| Search statistics | Enables administrators to collect and view statistics on search activity. | Disabled |
| Users available in search results | Users available within search results. Content related to the user will be included in the index. None | All | Public |
None |
| Incremental Index Update | Update the index incrementally as the site content is modified. This may lead to lower performance and accuracy than processing the index on a periodic basis. |
Enabled |
| Search index rebuild memory limit | Temporarily adjust the memory limit to use during Search index rebuild. Depending on the volume of data, some large operations require more memory. Increasing it locally, per operation, allows to keep a lower memory limit globally. Keep in mind that memory usage is still limited to what is available on the server. for example: 256M |
None |
| Search index rebuild time limit | Temporarily adjust the time limit to use during Search index rebuild. Depending on the volume of data, some requests may take longer. Increase the time limit locally to resolve the issue. Use reasonable values. | None |
| Unified search engine | Search engine used to index the content of this Tiki site. Some engines are more suitable for larger sites, but require additional software on the server. MySQL full-text search | Elasticsearch |
MySQL full-text search |
| Elasticsearch URL | URL of any node in the cluster | http://localhost:9200 |
| Elasticsearch index prefix | The prefix that is used for all indexes for this installation in Elasticsearch | Tiki_ |
| Elasticsearch current index | A new index is created upon rebuilding, and the old one is then destroyed. This setting enables seeing the currently active index. Do not change this value unless you know what you are doing. |
None |
| Elasticsearch field limit per index | The maximum number of fields per search index in Elasticsearch version 5.x and above | 1000 fields |
| Relation types to index within object. | Comma-separated relation types for which objects should be indexed in their related objects. Elasticsearch needed |
None |
| Use MySQL Full-Text Search (fallback) | In case of Elasticsearch is active and unavailable, use MySQL Full-Text Search as fallback | Disabled |
| MySQL use short field names | Due to frm file constraints, number of search fields that one index can hold is usually limited to about 1500. This can be exceeded if you have numerous tracker fields. Enabling this option will try to shorten the field names internally that should allow you to use 300-500 more fields. Switching this option requires full index rebuild. | Disabled |
| Restore old MySQL indexes during reindex | If set, after the reindex is performed, old table MySQL indexes will be restored to the reindex related table. | Disabled |
| Default Boolean Operator | Use OR or AND as the default search operator. AND | OR |
AND |
| Excluded categories | List of category IDs to exclude from the search index | None |
| Excluded plugins | List of plugin names to exclude while indexing | None |
| Exclude all plugins | Indexing will exclude all plugins. | Enabled |
| Except included plugins | List of plugin names that are required to be included while indexing, when excluding all. Example: fancytable,list,trackerlist,trackerfilter | None |
| Don't index non searchable fields | Indexing will skip adding all tracker fields that are not marked as "searchable". This will free index space but also make it impossible to use those fields in search index queries. | Disabled |
| Index forum replies together with initial post | Forum replies will be indexed together with the initial post as a single document instead of being indexed separately. | Enabled |
| Tokenize version numbers | Tokenize version number strings so that major versions are found when sub-versions are mentioned. For example, searching for 2.7 would return documents containing 2.7.4, but not 1.2.7. | Disabled |
| Tokenize CamelCase words | Consider the components of camel-case words as separate tokens, allowing them to be searched individually. Conflicts with Tokenize Version Numbers. |
Disabled |
| Possessive Stemmer | The possessive stemmer removes possessives (trailing "'s") from words before indexing them. | Enabled |
| Field weights | Allow the field weights to be set that apply when ranking pages in the search results. The weight is applied only when the field is in the query. To nullify the value of a field, use an insignificant amount, but not 0, which may lead to unexpected behaviors such as stripping of results. (Add these fields to the "Default content fields" preference below for it to have an effect in a global "content" search) One field per line, field_name:5.3 |
title:2.5 allowed_groups:0.... |
| Default content fields | All of the content is aggregated in the contents field. For custom weighting to apply, the fields must be included in the query. This option allows other fields to be included in the default content search. | contents, title |
| Cache per user and query for Tiki built-in search | Time in minutes a user has a same query cached applied to Tiki built-in search interface only. | 0 minutes |
| Cache result-specific formatted results | Formatted search results such as the ones used in the List plugin will be cached to prevent process-intensive reformatting on each page load. The cache is result-specific. Every different result will generate a separate cache. This could quickly build up a large cache directory. It is recommended to clear Tiki caches often (e.g. once per week) via an automated job if you use this feature. |
Disabled |
| Cache individual search formatters | List of search formatters whose output will be cached. This is separate to the result-specific formatted results cache. | None |
| LIST plugin cache default on | If selected, LIST plugins will be cached by default unless turned off at plugin level. | Disabled |
| LIST plugin cache default expiry | Default number of minutes for LIST plugin cache expiry. | 30 |
| Format to use for tracker field keys | Choose between field IDs and permanent names for the tracker indexing Permanent name | Field ID (backward compatibility mode with Tiki 7 and 8) |
Permanent name |
| Index Tracker Category names | Index the names and paths of category field values Requires reindexing |
Disabled |
| Use unified search in category admin | Use unified search to find objects to add to categories. This limits the types of objects available to those included in the unified index. | Disabled |
| Automatically trim Elasticsearch results on date-sorted query | Automatically trim Elasticsearch results in unified search if the query is sorted by modification or creation date. | Disabled |
| Show error on missing field | When using List plugin to specify certain fields, especially tracker fields, this check helps ensure their names were entered correctly. | Enabled |
| Stop Word List | Words excluded from the search index, because they can be too frequent and produce unwanted results. MySQL full-text search has its own list of stop words configured in the server. |
a, an, and, are, as, at, be... |
| Search index outdated | Number of days to consider the search index outdated | 2 days |
| Automatic indexing of file content | Uses command line tools to extract the information from the files based on their MIME types. | Disabled |
| Automatic indexing of emails stored as files | Parses message/rfc822 types of files (aka eml files) and stores individual email headers and content in search index. | Disabled |
| Asynchronous indexing | Enabled | |
| MySQL full-text search | Also known as 'Basic Search'. This search uses the MySQL full-text search feature. The indexation is continuously updated. | Disabled |
| Referer search highlighting | When a user lands on a Tiki page from a search engine, Tiki highlights the search words they used. Its similar to using Tiki’s search facility. | Enabled |
| Ignore individual object permissions | Display items the user may not be entitled to view in search results. Will improve performance, but may show forbidden results. |
Disabled |
| Ignore category viewing restrictions | Display items the user may not be entitled to view in search results. Will improve performance, but may show forbidden results |
Disabled |
| Autocomplete page names | Automatically complete page names as the user starts typing. For example the user types the start of the wiki page name “Sear” and Tiki returns “Search”, “Search General Settings”, etc | Disabled |
| File thumbnail preview | Have a preview of attachments in search results | Disabled |
| Forum name search | When listing forums | Disabled |
| Forum content search | When listing forums | Enabled |
| Topic content search | Enabled | |
| Unified search for forums and file galleries | Enabled |
| Option | Description | Default |
|---|---|---|
| Unified search index | Enables searching for content at the site using a Tiki-managed index. It's recommended to set a cron job to periodically rebuild the search index. |
Enabled |
| Search statistics | Enables administrators to collect and view statistics on search activity. | Disabled |
| Users available in search results | Users available within search results. Content related to the user will be included in the index. None | All | Public |
None |
| Incremental Index Update | Update the index incrementally as the site content is modified. This may lead to lower performance and accuracy than processing the index on a periodic basis. |
Enabled |
| Search index rebuild memory limit | Temporarily adjust the memory limit to use during Search index rebuild. Depending on the volume of data, some large operations require more memory. Increasing it locally, per operation, allows to keep a lower memory limit globally. Keep in mind that memory usage is still limited to what is available on the server. for example: 256M |
None |
| Search index rebuild time limit | Temporarily adjust the time limit to use during Search index rebuild. Depending on the volume of data, some requests may take longer. Increase the time limit locally to resolve the issue. Use reasonable values. | None |
| Unified search engine | Search engine used to index the content of this Tiki site. Some engines are more suitable for larger sites, but require additional software on the server. MySQL full-text search | Elasticsearch |
MySQL full-text search |
| Elasticsearch URL | URL of any node in the cluster | http://localhost:9200 |
| Elasticsearch index prefix | The prefix that is used for all indexes for this installation in Elasticsearch | Tiki_ |
| Elasticsearch current index | A new index is created upon rebuilding, and the old one is then destroyed. This setting enables seeing the currently active index. Do not change this value unless you know what you are doing. |
None |
| Elasticsearch field limit per index | The maximum number of fields per search index in Elasticsearch version 5.x and above | 1000 fields |
| Relation types to index within object. | Comma-separated relation types for which objects should be indexed in their related objects. Elasticsearch needed |
None |
| Use MySQL Full-Text Search (fallback) | In case of Elasticsearch is active and unavailable, use MySQL Full-Text Search as fallback | Disabled |
| MySQL use short field names | Due to frm file constraints, number of search fields that one index can hold is usually limited to about 1500. This can be exceeded if you have numerous tracker fields. Enabling this option will try to shorten the field names internally that should allow you to use 300-500 more fields. Switching this option requires full index rebuild. | Disabled |
| Restore old MySQL indexes during reindex | If set, after the reindex is performed, old table MySQL indexes will be restored to the reindex related table. | Disabled |
| Default Boolean Operator | Use OR or AND as the default search operator. AND | OR |
AND |
| Excluded categories | List of category IDs to exclude from the search index | None |
| Excluded plugins | List of plugin names to exclude while indexing | None |
| Exclude all plugins | Indexing will exclude all plugins. | Enabled |
| Except included plugins | List of plugin names that are required to be included while indexing, when excluding all. Example: fancytable,list,trackerlist,trackerfilter | None |
| Don't index non searchable fields | Indexing will skip adding all tracker fields that are not marked as "searchable". This will free index space but also make it impossible to use those fields in search index queries. | Disabled |
| Index forum replies together with initial post | Forum replies will be indexed together with the initial post as a single document instead of being indexed separately. | Enabled |
| Tokenize version numbers | Tokenize version number strings so that major versions are found when sub-versions are mentioned. For example, searching for 2.7 would return documents containing 2.7.4, but not 1.2.7. | Disabled |
| Tokenize CamelCase words | Consider the components of camel-case words as separate tokens, allowing them to be searched individually. Conflicts with Tokenize Version Numbers. |
Disabled |
| Possessive Stemmer | The possessive stemmer removes possessives (trailing "'s") from words before indexing them. | Enabled |
| Field weights | Allow the field weights to be set that apply when ranking pages in the search results. The weight is applied only when the field is in the query. To nullify the value of a field, use an insignificant amount, but not 0, which may lead to unexpected behaviors such as stripping of results. (Add these fields to the "Default content fields" preference below for it to have an effect in a global "content" search) One field per line, field_name:5.3 |
title:2.5 allowed_groups:0.... |
| Default content fields | All of the content is aggregated in the contents field. For custom weighting to apply, the fields must be included in the query. This option allows other fields to be included in the default content search. | contents, title |
| Cache per user and query for Tiki built-in search | Time in minutes a user has a same query cached applied to Tiki built-in search interface only. | 0 minutes |
| Cache result-specific formatted results | Formatted search results such as the ones used in the List plugin will be cached to prevent process-intensive reformatting on each page load. The cache is result-specific. Every different result will generate a separate cache. This could quickly build up a large cache directory. It is recommended to clear Tiki caches often (e.g. once per week) via an automated job if you use this feature. |
Disabled |
| Cache individual search formatters | List of search formatters whose output will be cached. This is separate to the result-specific formatted results cache. | None |
| LIST plugin cache default on | If selected, LIST plugins will be cached by default unless turned off at plugin level. | Disabled |
| LIST plugin cache default expiry | Default number of minutes for LIST plugin cache expiry. | 30 |
| Format to use for tracker field keys | Choose between field IDs and permanent names for the tracker indexing Permanent name | Field ID (backward compatibility mode with Tiki 7 and 8) |
Permanent name |
| Index Tracker Category names | Index the names and paths of category field values Requires reindexing |
Disabled |
| Use unified search in category admin | Use unified search to find objects to add to categories. This limits the types of objects available to those included in the unified index. | Disabled |
| Automatically trim Elasticsearch results on date-sorted query | Automatically trim Elasticsearch results in unified search if the query is sorted by modification or creation date. | Disabled |
| Show error on missing field | When using List plugin to specify certain fields, especially tracker fields, this check helps ensure their names were entered correctly. | Enabled |
| Stop Word List | Words excluded from the search index, because they can be too frequent and produce unwanted results. MySQL full-text search has its own list of stop words configured in the server. |
a, an, and, are, as, at, be... |
| Search index outdated | Number of days to consider the search index outdated | 2 days |
| Automatic indexing of file content | Uses command line tools to extract the information from the files based on their MIME types. | Disabled |
| Automatic indexing of emails stored as files | Parses message/rfc822 types of files (aka eml files) and stores individual email headers and content in search index. | Disabled |
| Asynchronous indexing | Enabled | |
| MySQL full-text search | Also known as 'Basic Search'. This search uses the MySQL full-text search feature. The indexation is continuously updated. | Disabled |
| Referer search highlighting | When a user lands on a Tiki page from a search engine, Tiki highlights the search words they used. Its similar to using Tiki’s search facility. | Enabled |
| Ignore individual object permissions | Display items the user may not be entitled to view in search results. Will improve performance, but may show forbidden results. |
Disabled |
| Ignore category viewing restrictions | Display items the user may not be entitled to view in search results. Will improve performance, but may show forbidden results |
Disabled |
| Autocomplete page names | Automatically complete page names as the user starts typing. For example the user types the start of the wiki page name “Sear” and Tiki returns “Search”, “Search General Settings”, etc | Disabled |
| File thumbnail preview | Have a preview of attachments in search results | Disabled |
| Forum name search | When listing forums | Disabled |
| Forum content search | When listing forums | Enabled |
| Topic content search | Enabled | |
| Tiki-indexed search | Disabled | |
| Use database (full-text) search | Disabled |
| Option | Description | Default |
|---|---|---|
| Unified search index | Enables searching for content at the site using a Tiki-managed index. It's recommended to set a cron job to periodically rebuild the search index. |
Enabled |
| Search statistics | Enables administrators to collect and view statistics on search activity. | Disabled |
| Users available in search results | Users available within search results. Content related to the user will be included in the index. None | All | Public |
None |
| Incremental Index Update | Update the index incrementally as the site content is modified. This may lead to lower performance and accuracy than processing the index on a periodic basis. |
Enabled |
| Search index rebuild memory limit | Temporarily adjust the memory limit to use during Search index rebuild. Depending on the volume of data, some large operations require more memory. Increasing it locally, per operation, allows to keep a lower memory limit globally. Keep in mind that memory usage is still limited to what is available on the server. for example: 256M |
None |
| Search index rebuild time limit | Temporarily adjust the time limit to use during Search index rebuild. Depending on the volume of data, some requests may take longer. Increase the time limit locally to resolve the issue. Use reasonable values. | None |
| Unified search engine | Search engine used to index the content of this Tiki site. Some engines are more suitable for larger sites, but require additional software on the server. Lucene (PHP implementation) - Deprecated | MySQL full-text search | Elasticsearch |
MySQL full-text search |
| Highlight results snippets | Highlight the result snippet based on the search query to improve user experience. May impact performance |
Disabled |
| Lucene index location | Path to the location of the Lucene search index. The index must be on a local filesystem with enough space to contain the volume of the database. | temp/unified-index |
| Lucene maximum results | Maximum number of results to produce. Results beyond these will need a more refined query to be reached. | 200 results |
| Lucene maximum result-set limit | This is used when calculating result scores and sort order which can lead to "out of memory" errors on large data sets. The default of 1000 is safe with the PHP memory_limit set to 128M Maximum size of result set to consider. 0 for unlimited |
1000 result sets |
| Lucene terms per query limit | Maximum number of terms to be generated. This value may need to be increased in the case of "Terms per query limit is reached" espescially with wildcard, range and fuzzy searches. | 1024 terms |
| Lucene maximum number of buffered documents | Number of documents required before the buffered in-memory documents are written into a new segment. | 10 documents |
| Lucene maximum number of merge documents | Largest number of documents merged by addDocument(). Small values (for example, less than 10,000) are best for interactive indexing, as this limits the length of pauses while indexing to a few seconds. Larger values are best for batched indexing and speedier searches. Small values (for example, less than 10,000) are best for interactive indexing. Use 0 for the Lucene default, which is practically infinite. |
0 merge documents |
| Lucene merge factor | How often segment indices are merged by addDocument(). With smaller values, less RAM is used while indexing, and searches on unoptimized indices are faster, but indexing speed is slower. With larger values, more RAM is used during indexing, and while searches on unoptimized indices are slower, indexing is faster. Large values (greater than 10) are best for batch index creation, and smaller values (less than 10) for indices that are interactively maintained. |
10 |
| Elasticsearch URL | URL of any node in the cluster | http://localhost:9200 |
| Elasticsearch index prefix | The prefix that is used for all indexes for this installation in Elasticsearch | Tiki_ |
| Elasticsearch current index | A new index is created upon rebuilding, and the old one is then destroyed. This setting enables seeing the currently active index. Do not change this value unless you know what you are doing. |
None |
| Elasticsearch field limit per index | The maximum number of fields per search index in Elasticsearch version 5.x and above | 1000 fields |
| Relation types to index within object. | Comma-separated relation types for which objects should be indexed in their related objects. Elasticsearch needed |
None |
| Use MySQL Full-Text Search (fallback) | In case of Elasticsearch is active and unavailable, use MySQL Full-Text Search as fallback | Disabled |
| MySQL use short field names | Due to frm file constraints, number of search fields that one index can hold is usually limited to about 1500. This can be exceeded if you have numerous tracker fields. Enabling this option will try to shorten the field names internally that should allow you to use 300-500 more fields. Switching this option requires full index rebuild. | Disabled |
| Default Boolean Operator | Use OR or AND as the default search operator. AND | OR |
AND |
| Excluded categories | List of category IDs to exclude from the search index | None |
| Excluded plugins | List of plugin names to exclude while indexing | None |
| Exclude all plugins | Indexing will exclude all plugins. | Enabled |
| Except included plugins | List of plugin names that are required to be included while indexing, when excluding all. Example: fancytable,list,trackerlist,trackerfilter | None |
| Don't index non searchable fields | Indexing will skip adding all tracker fields that are not marked as "searchable". This will free index space but also make it impossible to use those fields in search index queries. | Disabled |
| Index forum replies together with initial post | Forum replies will be indexed together with the initial post as a single document instead of being indexed separately. | Enabled |
| Tokenize version numbers | Tokenize version number strings so that major versions are found when sub-versions are mentioned. For example, searching for 2.7 would return documents containing 2.7.4, but not 1.2.7. | Disabled |
| Tokenize CamelCase words | Consider the components of camel-case words as separate tokens, allowing them to be searched individually. Conflicts with Tokenize Version Numbers. |
Disabled |
| Possessive Stemmer | The possessive stemmer removes possessives (trailing "'s") from words before indexing them. | Enabled |
| Field weights | Allow the field weights to be set that apply when ranking pages in the search results. The weight is applied only when the field is in the query. To nullify the value of a field, use an insignificant amount, but not 0, which may lead to unexpected behaviors such as stripping of results. (Add these fields to the "Default content fields" preference below for it to have an effect in a global "content" search) One field per line, field_name:5.3 |
title:2.5 allowed_groups:0.... |
| Default content fields | All of the content is aggregated in the contents field. For custom weighting to apply, the fields must be included in the query. This option allows other fields to be included in the default content search. | contents, title |
| Cache per user and query for Tiki built-in search | Time in minutes a user has a same query cached applied to Tiki built-in search interface only. | 0 minutes |
| Cache result-specific formatted results | Formatted search results such as the ones used in the List plugin will be cached to prevent process-intensive reformatting on each page load. The cache is result-specific. Every different result will generate a separate cache. This could quickly build up a large cache directory. It is recommended to clear Tiki caches often (e.g. once per week) via an automated job if you use this feature. |
Disabled |
| Cache individual search formatters | List of search formatters whose output will be cached. This is separate to the result-specific formatted results cache. | None |
| LIST plugin cache default on | If selected, LIST plugins will be cached by default unless turned off at plugin level. | Disabled |
| LIST plugin cache default expiry | Default number of minutes for LIST plugin cache expiry. | 30 |
| Format to use for tracker field keys | Choose between field IDs and permanent names for the tracker indexing Permanent name | Field ID (backward compatibility mode with Tiki 7 and 8) |
Permanent name |
| Index Tracker Category names | Index the names and paths of category field values Requires reindexing |
Disabled |
| Use unified search in category admin | Use unified search to find objects to add to categories. This limits the types of objects available to those included in the unified index. | Disabled |
| Automatically trim Elasticsearch results on date-sorted query | Automatically trim Elasticsearch results in unified search if the query is sorted by modification or creation date. | Disabled |
| Show error on missing field | When using List plugin to specify certain fields, especially tracker fields, this check helps ensure their names were entered correctly. | Enabled |
| Stop Word List | Words excluded from the search index, because they can be too frequent and produce unwanted results. MySQL full-text search has its own list of stop words configured in the server. |
a, an, and, are, as, at, be... |
| Search index outdated | Number of days to consider the search index outdated | 2 days |
| Automatic indexing of file content | Uses command line tools to extract the information from the files based on their MIME types. | Disabled |
| Asynchronous indexing | Enabled | |
| MySQL full-text search | Also known as 'Basic Search'. This search uses the MySQL full-text search feature. The indexation is continuously updated. | Disabled |
| Referer search highlighting | When a user lands on a Tiki page from a search engine, Tiki highlights the search words they used. Its similar to using Tiki’s search facility. | Enabled |
| Ignore individual object permissions | Display items the user may not be entitled to view in search results. Will improve performance, but may show forbidden results. |
Disabled |
| Ignore category viewing restrictions | Display items the user may not be entitled to view in search results. Will improve performance, but may show forbidden results |
Disabled |
| Autocomplete page names | Automatically complete page names as the user starts typing. For example the user types the start of the wiki page name “Sear” and Tiki returns “Search”, “Search General Settings”, etc | Disabled |
| File thumbnail preview | Have a preview of attachments in search results | Disabled |
| Forum name search | When listing forums | Disabled |
| Forum content search | When listing forums | Enabled |
| Topic content search | Enabled | |
| Tiki-indexed search | Disabled | |
| Use database (full-text) search | Disabled |
| Option | Description | Default |
|---|---|---|
| Unified search index | Enables searching for content at the site using a Tiki-managed index. It's recommended to set a cron job to periodically rebuild the search index. |
Enabled |
| Search statistics | Enables administrators to collect and view statistics on search activity. | Disabled |
| Users available in search results | Users available within search results. Content related to the user will be included in the index. None | All | Public |
None |
| Incremental Index Update | Update the index incrementally as the site content is modified. This may lead to lower performance and accuracy than processing the index on a periodic basis. |
Enabled |
| Search index rebuild memory limit | Temporarily adjust the memory limit to use during Search index rebuild. Depending on the volume of data, some large operations require more memory. Increasing it locally, per operation, allows to keep a lower memory limit globally. Keep in mind that memory usage is still limited to what is available on the server. for example: 256M |
None |
| Search index rebuild time limit | Temporarily adjust the time limit to use during Search index rebuild. Depending on the volume of data, some requests may take longer. Increase the time limit locally to resolve the issue. Use reasonable values. | None |
| Unified search engine | Search engine used to index the content of this Tiki site. Some engines are more suitable for larger sites, but require additional software on the server. Lucene (PHP implementation) - Deprecated | MySQL full-text search | Elasticsearch |
MySQL full-text search |
| Highlight results snippets | Highlight the result snippet based on the search query to improve user experience. May impact performance |
Disabled |
| Lucene index location | Path to the location of the Lucene search index. The index must be on a local filesystem with enough space to contain the volume of the database. | temp/unified-index |
| Lucene maximum results | Maximum number of results to produce. Results beyond these will need a more refined query to be reached. | 200 results |
| Lucene maximum result-set limit | This is used when calculating result scores and sort order which can lead to "out of memory" errors on large data sets. The default of 1000 is safe with the PHP memory_limit set to 128M Maximum size of result set to consider. 0 for unlimited |
1000 result sets |
| Lucene terms per query limit | Maximum number of terms to be generated. This value may need to be increased in the case of "Terms per query limit is reached" espescially with wildcard, range and fuzzy searches. | 1024 terms |
| Lucene maximum number of buffered documents | Number of documents required before the buffered in-memory documents are written into a new segment. | 10 documents |
| Lucene maximum number of merge documents | Largest number of documents merged by addDocument(). Small values (for example, less than 10,000) are best for interactive indexing, as this limits the length of pauses while indexing to a few seconds. Larger values are best for batched indexing and speedier searches. Small values (for example, less than 10,000) are best for interactive indexing. Use 0 for the Lucene default, which is practically infinite. |
0 merge documents |
| Lucene merge factor | How often segment indices are merged by addDocument(). With smaller values, less RAM is used while indexing, and searches on unoptimized indices are faster, but indexing speed is slower. With larger values, more RAM is used during indexing, and while searches on unoptimized indices are slower, indexing is faster. Large values (greater than 10) are best for batch index creation, and smaller values (less than 10) for indices that are interactively maintained. |
10 |
| Elasticsearch URL | URL of any node in the cluster | http://localhost:9200 |
| Elasticsearch index prefix | The prefix that is used for all indexes for this installation in Elasticsearch | Tiki_ |
| Elasticsearch current index | A new index is created upon rebuilding, and the old one is then destroyed. This setting enables seeing the currently active index. Do not change this value unless you know what you are doing. |
None |
| Elasticsearch field limit per index | The maximum number of fields per search index in Elasticsearch version 5.x and above | 1000 fields |
| Relation types to index within object. | Comma-separated relation types for which objects should be indexed in their related objects. Elasticsearch needed |
None |
| Use MySQL Full-Text Search (fallback) | In case of Elasticsearch is active and unavailable, use MySQL Full-Text Search as fallback | Disabled |
| Default Boolean Operator | Use OR or AND as the default search operator. AND | OR |
AND |
| Excluded categories | List of category IDs to exclude from the search index | None |
| Excluded plugins | List of plugin names to exclude while indexing | None |
| Exclude all plugins | Indexing will exclude all plugins. | Enabled |
| Except included plugins | List of plugin names that are required to be included while indexing, when excluding all. Example: fancytable,list,trackerlist,trackerfilter | None |
| Index forum replies together with initial post | Forum replies will be indexed together with the initial post as a single document instead of being indexed separately. | Enabled |
| Tokenize version numbers | Tokenize version number strings so that major versions are found when sub-versions are mentioned. For example, searching for 2.7 would return documents containing 2.7.4, but not 1.2.7. | Disabled |
| Tokenize CamelCase words | Consider the components of camel-case words as separate tokens, allowing them to be searched individually. Conflicts with Tokenize Version Numbers. |
Disabled |
| Possessive Stemmer | The possessive stemmer removes possessives (trailing "'s") from words before indexing them. | Enabled |
| Field weights | Allow the field weights to be set that apply when ranking pages in the search results. The weight is applied only when the field is in the query. To nullify the value of a field, use an insignificant amount, but not 0, which may lead to unexpected behaviors such as stripping of results. (Add these fields to the "Default content fields" preference below for it to have an effect in a global "content" search) One field per line, field_name:5.3 |
title:2.5 allowed_groups:0.... |
| Default content fields | All of the content is aggregated in the contents field. For custom weighting to apply, the fields must be included in the query. This option allows other fields to be included in the default content search. | contents, title |
| Cache per user and query for Tiki built-in search | Time in minutes a user has a same query cached applied to Tiki built-in search interface only. | 0 minutes |
| Cache result-specific formatted results | Formatted search results such as the ones used in the List plugin will be cached to prevent process-intensive reformatting on each page load. The cache is result-specific. Every different result will generate a separate cache. This could quickly build up a large cache directory. It is recommended to clear Tiki caches often (e.g. once per week) via an automated job if you use this feature. |
Disabled |
| Cache individual search formatters | List of search formatters whose output will be cached. This is separate to the result-specific formatted results cache. | None |
| LIST plugin cache default on | If selected, LIST plugins will be cached by default unless turned off at plugin level. | Disabled |
| LIST plugin cache default expiry | Default number of minutes for LIST plugin cache expiry. | 30 |
| Format to use for tracker field keys | Choose between field IDs and permanent names for the tracker indexing Permanent name | Field ID (backward compatibility mode with Tiki 7 and 8) |
Permanent name |
| Index Tracker Category names | Index the names and paths of category field values Requires reindexing |
Disabled |
| Use unified search in category admin | Use unified search to find objects to add to categories. This limits the types of objects available to those included in the unified index. | Disabled |
| Automatically trim Elasticsearch results on date-sorted query | Automatically trim Elasticsearch results in unified search if the query is sorted by modification or creation date. | Disabled |
| Show error on missing field | When using List plugin to specify certain fields, especially tracker fields, this check helps ensure their names were entered correctly. | Enabled |
| Stop Word List | Words excluded from the search index, because they can be too frequent and produce unwanted results. MySQL full-text search has its own list of stop words configured in the server. |
a, an, and, are, as, at, be... |
| Search index outdated | Number of days to consider the search index outdated | 2 days |
| MySQL full-text search | Also known as 'Basic Search'. This search uses the MySQL full-text search feature. The indexation is continuously updated. | Disabled |
| Referer search highlighting | When a user lands on a Tiki page from a search engine, Tiki highlights the search words they used. Its similar to using Tiki’s search facility. | Enabled |
| Ignore individual object permissions | Display items the user may not be entitled to view in search results. Will improve performance, but may show forbidden results. |
Disabled |
| Ignore category viewing restrictions | Display items the user may not be entitled to view in search results. Will improve performance, but may show forbidden results |
Disabled |
| Autocomplete page names | Automatically complete page names as the user starts typing. For example the user types the start of the wiki page name “Sear” and Tiki returns “Search”, “Search General Settings”, etc | Disabled |
| File thumbnail preview | Have a preview of attachments in search results | Disabled |
| Forum name search | When listing forums | Disabled |
| Forum content search | When listing forums | Enabled |
| Topic content search | Enabled | |
| Tiki-indexed search | Disabled | |
| Use database (full-text) search | Disabled |
Tiki 15 Preferences Image
| Option | Description | Default |
|---|---|---|
| Unified search index | Enables searching for content at the site using a Tiki-managed index. It's recommended to set a cron job to periodically rebuild the search index. |
Enabled |
| Search statistics | Enables administrators to collect and view statistics on search activity. | Disabled |
| Users available in search results | Users available within search results. Content related to the user will be included in the index. None | All | Public |
None |
| Incremental Index Update | Update the index incrementally as the site content is modified. This may lead to lower performance and accuracy than processing the index on a periodic basis. |
Enabled |
| Search index rebuild memory limit | Temporarily adjust the memory limit to use during Search index rebuild. Depending on the volume of data, some large operations require more memory. Increasing it locally, per operation, allows to keep a lower memory limit globally. Keep in mind that memory usage is still limited to what is available on the server. for example: 256M |
None |
| Search index rebuild time limit | Temporarily adjust the time limit to use during Search index rebuild. Depending on the volume of data, some requests may take longer. Increase the time limit locally to resolve the issue. Use reasonable values. | None |
| Unified search engine | Search engine used to index the content of this Tiki site. Some engines are more suitable for larger sites, but require additional software on the server. Lucene (PHP implementation) - Deprecated | MySQL full-text search | Elasticsearch |
MySQL full-text search |
| Highlight results snippets | Highlight the result snippet based on the search query to improve user experience. May impact performance |
Disabled |
| Lucene index location | Path to the location of the Lucene search index. The index must be on a local filesystem with enough space to contain the volume of the database. | temp/unified-index |
| Lucene maximum results | Maximum number of results to produce. Results beyond these will need a more refined query to be reached. | 200 results |
| Lucene maximum result-set limit | This is used when calculating result scores and sort order which can lead to "out of memory" errors on large data sets. The default of 1000 is safe with the PHP memory_limit set to 128M Maximum size of result set to consider. 0 for unlimited |
1000 result sets |
| Lucene terms per query limit | Maximum number of terms to be generated. This value may need to be increased in the case of "Terms per query limit is reached" espescially with wildcard, range and fuzzy searches. | 1024 terms |
| Lucene maximum number of buffered documents | Number of documents required before the buffered in-memory documents are written into a new segment. | 10 documents |
| Lucene maximum number of merge documents | Largest number of documents merged by addDocument(). Small values (for example, less than 10,000) are best for interactive indexing, as this limits the length of pauses while indexing to a few seconds. Larger values are best for batched indexing and speedier searches. Small values (for example, less than 10,000) are best for interactive indexing. Use 0 for the Lucene default, which is practically infinite. |
0 merge documents |
| Lucene merge factor | How often segment indices are merged by addDocument(). With smaller values, less RAM is used while indexing, and searches on unoptimized indices are faster, but indexing speed is slower. With larger values, more RAM is used during indexing, and while searches on unoptimized indices are slower, indexing is faster. Large values (greater than 10) are best for batch index creation, and smaller values (less than 10) for indices that are interactively maintained. |
10 |
| Elasticsearch URL | URL of any node in the cluster | http://localhost:9200 |
| Elasticsearch index prefix | The prefix that is used for all indexes for this installation in Elasticsearch | Tiki_ |
| Elasticsearch current index | A new index is created upon rebuilding, and the old one is then destroyed. This setting enables seeing the currently active index. Do not change this value unless you know what you are doing. |
None |
| Elasticsearch field limit per index | The maximum number of fields per search index in Elasticsearch version 5.x and above | 1000 fields |
| Relation types to index within object. | Comma-separated relation types for which objects should be indexed in their related objects. Elasticsearch needed |
None |
| Default Boolean Operator | Use OR or AND as the default search operator. AND | OR |
AND |
| Excluded categories | List of category IDs to exclude from the search index | None |
| Excluded plugins | List of plugin names to exclude while indexing | None |
| Exclude all plugins | Indexing will exclude all plugins. | Enabled |
| Except included plugins | List of plugin names that are required to be included while indexing, when excluding all. Example: fancytable,list,trackerlist,trackerfilter | None |
| Index forum replies together with initial post | Forum replies will be indexed together with the initial post as a single document instead of being indexed separately. | Enabled |
| Tokenize version numbers | Tokenize version number strings so that major versions are found when sub-versions are mentioned. For example, searching for 2.7 would return documents containing 2.7.4, but not 1.2.7. | Disabled |
| Tokenize CamelCase words | Consider the components of camel-case words as separate tokens, allowing them to be searched individually. Conflicts with Tokenize Version Numbers. |
Disabled |
| Possessive Stemmer | The possessive stemmer removes possessives (trailing "'s") from words before indexing them. | Enabled |
| Field weights | Allow the field weights to be set that apply when ranking pages in the search results. The weight is applied only when the field is in the query. To nullify the value of a field, use an insignificant amount, but not 0, which may lead to unexpected behaviors such as stripping of results. (Add these fields to the "Default content fields" preference below for it to have an effect in a global "content" search) One field per line, field_name:5.3 |
title:2.5 allowed_groups:0.... |
| Default content fields | All of the content is aggregated in the contents field. For custom weighting to apply, the fields must be included in the query. This option allows other fields to be included in the default content search. | contents, title |
| Cache per user and query | Time in minutes a user has a same query cached | 0 minutes |
| Search formatters to cache | Search formatters whose output will be cached | Categorylist |
| Format to use for tracker field keys | Choose between field IDs and permanent names for the tracker indexing Permanent name | Field ID (backward compatibility mode with Tiki 7 and 8) |
Permanent name |
| Cache formatted results | Formatted search results such as the ones used in the List plugin will be cached to prevent process-intensive reformatting on each page load. This could quickly build up a large cache directory. It is recommended to clear Tiki caches often (e.g. once per week) via an automated job if you use this feature. |
Disabled |
| Use unified search in category admin | Use unified search to find objects to add to categories. This limits the types of objects available to those included in the unified index. | Disabled |
| Automatically trim Elasticsearch results on date-sorted query | Automatically trim Elasticsearch results in unified search if the query is sorted by modification or creation date. | Disabled |
| Show error on missing field | When using List plugin to specify certain fields, especially tracker fields, this check helps ensure their names were entered correctly. | Enabled |
| Stop Word List | Words excluded from the search index, because they can be too frequent and produce unwanted results. MySQL full-text search has its own list of stop words configured in the server. |
a, an, and, are, as, at, be... |
| Search index outdated | Number of days to consider the search index outdated | 2 days |
| MySQL full-text search | Also known as 'Basic Search'. This search uses the MySQL full-text search feature. The indexation is continuously updated. | Disabled |
| Referer search highlighting | When a user lands on a Tiki page from a search engine, Tiki highlights the search words they used. Its similar to using Tiki’s search facility. | Enabled |
| Ignore individual object permissions | Display items the user may not be entitled to view in search results. Will improve performance, but may show forbidden results. |
Disabled |
| Ignore category viewing restrictions | Display items the user may not be entitled to view in search results. Will improve performance, but may show forbidden results |
Disabled |
| Autocomplete page names | Automatically complete page names as the user starts typing. For example the user types the start of the wiki page name “Sear” and Tiki returns “Search”, “Search General Settings”, etc | Disabled |
| File thumbnail preview | Have a preview of attachments in search results | Disabled |
| Forum name search | When listing forums | Disabled |
| Forum content search | When listing forums | Enabled |
| Topic content search | Enabled | |
| Tiki-indexed search | Disabled | |
| Use database (full-text) search | Disabled |
Tiki 15 Preferences Image
| Option | Description | Default |
|---|---|---|
| Unified search index | Enables searching for content at the site using a Tiki-managed index. It's recommended to set a cron job to periodically rebuild the search index. |
Enabled |
| Search statistics | This option enables administrators to collect and view statistics on search activity. | Disabled |
| Users available in search results | Users available within search results. Content related to the user will be included in the index. None | All | Public |
None |
| Incremental Index Update | Update the index incrementally as the site content is modified. This may lead to lower performance and accuracy than processing the index on a periodic basis. |
Enabled |
| Search index rebuild memory limit | Temporarily adjust the memory limit to use during Search index rebuild. Depending on the volume of data, some large operations require more memory. Increasing it locally, per operation, allows to keep a lower memory limit globally. Keep in mind that memory usage is still limited to what is available on the server. for example: 256M |
None |
| Search index rebuild time limit | Temporarily adjust the time limit to use during Search index rebuild. Depending on the volume of data, some requests may take longer. Increase the time limit locally to resolve the issue. Use reasonable values. | None |
| Unified search engine | The search engine used to index the content of this Tiki site. Some engines are more suitable for larger sites, but require additional software on the server. Lucene (PHP implementation) | MySQL full-text search | Elasticsearch |
MySQL full-text search |
| Highlight results snippets | Highlight the result snippet based on the search query to improve user experience. May impact performance |
Disabled |
| Lucene index location | Path to the location of the Lucene search index. The index must be on a local filesystem with enough space to contain the volume of the database. | temp/unified-index |
| Lucene maximum results | Maximum number of results to produce. Results beyond these will need a more refined query to be reached. | 200 results |
| Lucene maximum result-set limit | This is used when calculating result scores and sort order which can lead to "out of memory" errors on large data sets. The default of 1000 is safe with the PHP memory_limit set to 128M Maximum size of result set to consider. 0 for unlimited |
1000 result sets |
| Lucene terms per query limit | Maximum number of terms to be generated. This value may need to be increased in the case of "Terms per query limit is reached" errors, especially with wildcard, range and fuzzy searches. | 1024 terms |
| Lucene maximum number of buffered documents | Number of documents required before the buffered in-memory documents are written into a new segment. | 10 documents |
| Lucene maximum number of merge documents | Largest number of documents merged by addDocument(). Small values (for example, less than 10,000) are best for interactive indexing, as this limits the length of pauses while indexing to a few seconds. Larger values are best for batched indexing and speedier searches. Small values (for example, less than 10,000) are best for interactive indexing. Use 0 for the Lucene default, which is practically infinite. |
0 merge documents |
| Lucene merge factor | How often segment indices are merged by addDocument(). With smaller values, less RAM is used while indexing, and searches on unoptimized indices are faster, but indexing speed is slower. With larger values, more RAM is used during indexing, and while searches on unoptimized indices are slower, indexing is faster. Large values (greater than 10) are best for batch index creation, and smaller values (less than 10) for indices that are interactively maintained. |
10 |
| Elasticsearch URL | The The URL of any node in the cluster | http://localhost:9200 |
| Elasticsearch index prefix | The prefix that is used for all indexes for this installation in Elasticsearch. | Tiki_ |
| Elasticsearch current index | A new index is created upon rebuilding, and the old one is then destroyed. This setting enables seeing the currently active index. Do not change this value unless you know what you are doing. |
None |
| Elasticsearch field limit per index | The maximum number of fields per search index in Elasticsearch version 5.x and above | 1000 fields |
| Relation types to index within object. | Comma-separated relation types for which objects should be indexed in their related objects. Elasticsearch needed |
None |
| Default Boolean Operator | Use OR or AND as the default search operator. AND | OR |
AND |
| Excluded categories | List of category IDs to exclude from the search index | None |
| Excluded plugins | List of plugin names to exclude while indexing | None |
| Exclude all plugins | Indexing will exclude all plugins. | Enabled |
| Except included plugins | List of plugin names that are required to be included while indexing, when excluding all. Example: fancytable,list,trackerlist,trackerfilter | None |
| Index forum replies together with initial post | Forum replies will be indexed together with the initial post as a single document instead of being indexed separately. | Enabled |
| Tokenize version numbers | Tokenize version number strings so that major versions are found when sub-versions are mentioned. For example, searching for 2.7 would return documents containing 2.7.4, but not 1.2.7. | Disabled |
| Tokenize CamelCase words | Consider the components of camel-case words as separate tokens, allowing them to be searched individually. Conflicts with Tokenize Version Numbers. |
Disabled |
| Possessive Stemmer | The possessive stemmer removes possessives (trailing "'s") from words before indexing them. | Enabled |
| Field weights | Allow the field weights to be set that apply when ranking pages in the search results. The weight is applied only when the field is in the query. To nullify the value of a field, use an insignificant amount, but not 0, which may lead to unexpected behaviors such as stripping of results. One field per line, field_name:5.3 |
title:2.5 allowed_groups:0.... |
| Default content fields | All of the content is aggregated in the contents field. For custom weighting to apply, the fields must be included in the query. This option allows other fields to be included in the default content search. | contents, title |
| Cache per user and query | Time in minutes a user has a same query cached | 0 minutes |
| Search formatters to cache | Search formatters whose output will be cached | Categorylist |
| Format to use for tracker field keys | Choose between field IDs and permanent names for the tracker indexing Permanent name | Field ID (backward compatibility mode with Tiki 7 and 8) |
Permanent name |
| Cache formatted results | Formatted search results such as the ones used in the List plugin will be cached to prevent process-intensive reformatting on each page load. This could quickly build up a large cache directory. It is recommended to clear Tiki caches often (e.g. once per week) via an automated job if you use this feature. |
Disabled |
| Use unified search in category admin | Use unified search to find objects to add to categories. This limits the types of objects available to those included in the unified index. | Disabled |
| Automatically trim Elasticsearch results on date-sorted query | Automatically trim Elasticsearch results in unified search if the query is sorted by modification or creation date. | Disabled |
| Show error on missing field | When using List plugin to specify certain fields, especially tracker fields, this check helps ensure their names were entered correctly. | Enabled |
| Stop Word List | Words excluded from the search index, because they can be too frequent and produce unwanted results. MySQL full-text search has its own list of stop words configured in the server. |
a, an, and, are, as, at, be... |
| Search index outdated | Number of days to consider the search index outdated | 2 days |
| MySQL full-text search | Also known as 'Basic Search'. This search uses the MySQL full-text search feature. The indexation is continuously updated. Deprecated: This feature is unmaintained and may not be reliable. InnoDB doesn't support Full-Text Search earlier than version 5.6. |
Disabled |
| Referer search highlighting | Referrer search highlighting is when a user goes to a search engine such as Google or Yahoo and performs a search that generates links to your pages. When they click on the link and this feature is active, Tiki notices that they have come from a search engine site and highlights the search words they used. The result is similar to using the search using Tiki’s own search facility. | Enabled |
| Ignore individual object permissions | Allow forbidden items in search results. Will improve performance, but may show forbidden results. |
Disabled |
| Ignore category viewing restrictions | Allow showing forbidden (restricted) items in search result. Will improve performance, but may show forbidden results |
Disabled |
| Autocomplete page names | Automatically complete page names as the user starts typing. For example the user types the start of the wiki page name “Sear” and Tiki returns “Search”, “Search General Settings”, etc deprecated |
Disabled |
| Forum name search | When listing forums | Disabled |
| Forum content search | When listing forums | Enabled |
| Topic content search | Enabled | |
| Tiki-indexed search | Disabled | |
| Use database (full-text) search | Disabled |
Tiki 15 Preferences Image
| Option | Description | Default |
|---|---|---|
| Unified search index | Enables searching for content at the site using a Tiki-managed index. It’s recommended to set a cron job to periodically rebuild the search index. |
Enabled |
| Search statistics | This option enables administrators to collect and view statistics on search activity. | Disabled |
| Users available in search results | Users available within search results. Content related to the user will be included in the index. None | All | Public |
None |
| Incremental Index Update | Update the index incrementally as the site content is modified. This may lead to lower performance and accuracy than processing the index on a periodic basis. |
Enabled |
| Search index rebuild memory limit | Temporarily adjust the memory limit to use during Search index rebuild. Depending on the volume of data, some large operations require more memory. Increasing it locally, per operation, allows to keep a lower memory limit globally. Keep in mind that memory usage is still limited to what is available on the server. for example: 256M |
None |
| Search index rebuild time limit | Temporarily adjust the time limit to use during Search index rebuild. Depending on the volume of data, some requests may take longer. Increase the time limit locally to resolve the issue. Use reasonable values. | None |
| Unified search engine | Search engine used to index the content of your Tiki. Some engines are more suitable for larger sites, but require additional software on the server. Lucene (PHP implementation) | MySQL full-text search | Elasticsearch |
MySQL full-text search |
| Highlight results snippets | Highlight the result snippet based on the search query to improve user experience. May impact performance |
Disabled |
| Parse the results | Parse the results of Lucene search results. May impact performance |
Disabled |
| Lucene index location | Path to the location of the Lucene search index. The index must be on a local filesystem with enough space to contain the volume of the database. | temp/unified-index |
| Lucene maximum results | Maximum number of results to produce. Results beyond these will need a more refined query to be reached. | 200 results |
| Lucene maximum result-set limit | This is used when calculating result scores and sort order which can lead to out of memory errors on large data sets. The default of 1000 is safe with the PHP memory_limit set to 128M Maximum size of result set to consider. 0 for unlimited |
1000 result sets |
| Lucene terms per query limit | Maximum number of terms to be generated. Try increasing this value if you get errors saying “Terms per query limit is reached” espescially with wildcard, range and fuzzy searches. | 1024 terms |
| Lucene maximum number of buffered documents | Number of documents required before the buffered in-memory documents are written into a new segment. | 10 documents |
| Lucene maximum number of merge documents | Largest number of documents merged by addDocument(). Small values (for example, less than 10,000) are best for interactive indexing, as this limits the length of pauses while indexing to a few seconds. Larger values are best for batched indexing and speedier searches. Small values (for example, less than 10,000) are best for interactive indexing. Use 0 for the Lucene default, which is practically infinite. |
0 merge documents |
| Lucene merge factor | How often segment indices are merged by addDocument(). With smaller values, less RAM is used while indexing, and searches on unoptimized indices are faster, but indexing speed is slower. With larger values, more RAM is used during indexing, and while searches on unoptimized indices are slower, indexing is faster. Large values (greater than 10) are best for batch index creation, and smaller values (less than 10) for indices that are interactively maintained. |
10 |
| Elasticsearch URL | URL of any node in the cluster. | http://localhost:9200 |
| Elasticsearch index prefix | Prefix used for all indexes for this installation in Elasticsearch. | Tiki_ |
| Elasticsearch current index | A new index is created upon rebuild and the old one is then destroyed. This setting allows you to see the currently active one. Do not change this value unless you know what you are doing. |
None |
| Elasticsearch field limit per index | Maximum number of fields per search index in Elasticsearch version 5.x and above. | 1000 fields |
| Relation types to index within object. | Comma-separated relation types for which objects should be indexed in their related objects. Elasticsearch needed |
None |
| Default Boolean Operator | Use OR or AND as the default search operator. OR | AND |
None |
| Excluded categories | List of category IDs to exclude from the search index. | None |
| Excluded plugins | List of plugin names to exclude while indexing. | None |
| Exclude all plugins | Indexing will exclude all plugins. | Enabled |
| Except included plugins | List of plugin names that are required to be included while indexing, when excluding all. Example: fancytable,list,trackerlist,trackerfilter | None |
| Index forum replies together with initial post | Forum replies will be indexed together with the initial post as a single document instead of being indexed separately | Enabled |
| Tokenize version numbers | Tokenize version number strings so that major versions are found when sub-versions are mentionned. For example, searching for 2.7 would return documents containing 2.7.4, but not 1.2.7. | Disabled |
| Tokenize CamelCase words | Consider the components of camel-case words as separate tokens, allowing them to be searched individually. Conflicts with Tokenize Version Numbers. |
Disabled |
| Possesive Stemmer | The possessive stemmer removes ‘s from any words before indexing | Enabled |
| Field weights | Allows the field weights to be set that apply when ranking the pages for search listing. The weight only applies when the field is in the query. To nullify the value of a field, use an insignificant amount, not 0, which may lead to unexpected behaviors, such as stripping results. One field per line, field_name:5.3 |
title:2.5 allowed_groups:0.... |
| Default content fields | All of the content is aggregated in the contents field. For custom weighting to apply, the fields must be included in the query. This option allows other fields to be included in the default content search. | contents, title |
| Cache per user and query | Time in minutes a user has a same query cached | 0 minutes |
| Search formatters to cache | Search formatters to cache the output of | Categorylist |
| Format to use for tracker field keys | Choose between field IDs and permanent names for the tracker indexing Permanent name | Field ID (backward compatibility mode with Tiki 7 and 8) |
Permanent name |
| Use unified search in category admin | Use unfied search to find objects to add to categories. Limits types of objects available to those included in the unified index. | Disabled |
| Automatically trim Elasticsearch results on date-sorted query | Automatically trim Elastic Search results in unified search if the query is sorted by modification or creation date. | Disabled |
| Show error on missing field | When using LIST plugin to specify certain fields, especially tracker fields, this check helps ensure their names were entered correctly. | Enabled |
| Stop Word List | Words excluded from the search index as they can be too frequent and cause noise. MySQL full-text search has its own list of stop words configured in the server. |
a, an, and, are, as, at, be... |
| Search index outdated | Number of days to consider the search index outdated. | 2 days |
| MySQL full-text search | Also known as ‘Basic Search’. This search uses the MySQL full-text search feature. The indexation is continuously updated. Deprecated: This feature is unmaintained and may not be reliable. InnoDB doesn’t support Full-Text Search earlier than version 5.6. |
Disabled |
| Referer search highlighting | Referrer search highlighting is when a user goes to a search engine such as Google or Yahoo and performs a search that generates links to your pages. When they click on the link and this feature is active, Tiki notices that they have come from a search engine site and highlights the search words they used. The result is similar to using the search using Tiki’s own search facility. | Enabled |
| Ignore individual object permissions | Allow forbidden items in search results. Will improve performance, but may show forbidden results. |
Disabled |
| Ignore category viewing restrictions | Allow showing forbidden (restricted) items in search result. Will improve performance, but may show forbidden results |
Disabled |
| Autocomplete page names | Automatically complete page names as the user starts typing. For example the user types the start of the wiki page name “Sear” and Tiki returns “Search”, “Search General Settings”, etc deprecated |
Disabled |
| Forum name search | When listing forums | Disabled |
| Forum content search | When listing forums | Enabled |
| Topic content search | Enabled | |
| Tiki-indexed search | Disabled | |
| Use database (full-text) search | Disabled |
Tiki 15 Preferences Image
| Option | Description | Default |
|---|---|---|
| Unified Search Index | Enables searching for content at the site using a Tiki-managed index. Unified Search requires server processing resources and that you properly set the server permissions. It's recommended to set a cron job to periodically rebuild the search index. |
Enabled |
| Search statistics | This option enables administrators to collect and view statistics on search activity. | Disabled |
| Users available in search results | Users available within search results. Content related to the user will be included in the index. None | All | Public |
None |
| Incremental Index Update | Update the index incrementally as the site content is modified. This may lead to lower performance and accuracy than processing the index on a periodic basis. This may lead to lower performance and accuracy than processing the index on a periodic basis. |
Enabled |
| Memory limit to apply during search index rebuild | Temporarily adjust the memory limit to use during search index rebuild. Depending on the volume of data, some large operations require more memory. Increasing it locally, per operation, allows to keep a lower memory limit globally. Keep in mind that memory usage is still limited to what is available on the server. for example: 256M |
None |
| Time limit to apply during search index rebuild | Temporarily adjust the time limit to use during search index rebuild. Depending on the volume of data, some requests may take longer. Increase the time limit locally to resolve the issue. Use reasonable values. seconds |
None |
| Unified search engine | Search engine used to index the content of your Tiki. Some engines are more suitable for larger sites, but require additional software on the server. Lucene (PHP implementation) | MySQL full-text search | Elasticsearch |
MySQL full-text search |
| Highlight results snippets | Highlight the result snippet based on the search query. Enabling this option will impact performance, but improve user experience. May impact performance |
Disabled |
| Parse the results | Parse the results. May impact performance May impact performance |
Disabled |
| Lucene index location | Path to the location of the Lucene search index. The index must be on a local filesystem with enough space to contain the volume of the database. | temp/unified-index |
| Lucene maximum results | Maximum number of results to produce. Results beyond these will need a more refined query to be reached. | 200 |
| Lucene maximum result-set limit | This is used when calculating result scores and sort order which can lead to out of memory errors on large data sets. The default of 1000 is safe with the PHP memory_limit set to 128M Maximum size of result set to consider. Default 1000, 0 = unlimited. 0 for unlimited |
1000 |
| Lucene terms per query limit | Maximum number of terms to be generated. Try increasing this value if you get errors saying "Terms per query limit is reached" espescially with wildcard, range and fuzzy searches. | 1024 |
| Lucene maximum number of buffered documents | Number of documents required before the buffered in-memory documents are written into a new segment. | 10 |
| Lucene maximum number of merge documents | Largest number of documents merged by addDocument(). Small values (for example, less than 10,000) are best for interactive indexing, as this limits the length of pauses while indexing to a few seconds. Larger values are best for batched indexing and speedier searches. Small values (for example, less than 10,000) are best for interactive indexing. Use 0 for the Lucene default, which is practically infinite. |
0 |
| Lucene merge factor | How often segment indices are merged by addDocument(). With smaller values, less RAM is used while indexing, and searches on unoptimized indices are faster, but indexing speed is slower. With larger values, more RAM is used during indexing, and while searches on unoptimized indices are slower, indexing is faster. Thus larger values (> 10) are best for batch index creation, and smaller values (< 10) for indices that are interactively maintained. Large values (greater than 10) are best for batch index creation, and smaller values (less than 10) for indices that are interactively maintained. |
10 |
| Elasticsearch URL | URL of any node in the cluster. | http://localhost:9200 |
| Elasticsearch index prefix | Prefix used for all indexes for this installation in Elasticsearch. | Tiki_ |
| Elasticsearch current index | A new index is created upon rebuild and the old one is then destroyed. This setting allows you to see the currently active one. Do not change this value unless you know what you are doing. |
None |
| Relation types to index within object. | Comma-separated relation types for which objects should be indexed in their related objects. (Elasticsearch needed) Elasticsearch needed |
None |
| Default Boolean Operator | Use OR (default) or AND as the default search operator. OR | AND |
None |
| Excluded categories | List of category IDs to exclude from the search index. | None |
| Excluded plugins | List of plugin names to exclude while indexing. | None |
| Exclude all plugins | If enabled, indexing will exclude all plugins. | Enabled |
| Except included plugins | List of plugin names that are required to be included while indexing, when excluding all. Example: fancytable,list,trackerlist,trackerfilter . | None |
| Index forum replies together with initial post | If enabled, forum replies will be indexed together with the initial post as a single document instead of being indexed separately | Enabled |
| Tokenize version numbers | Tokenize version number strings so that major versions are found when sub-versions are mentionned. For example, searching for 2.7 would return documents containing 2.7.4, but not 1.2.7. | Disabled |
| Tokenize CamelCase words | Consider the components of camel-case words as separate tokens, allowing them to be searched individually. Elasticsearch only Conflicts with Tokenize Version Numbers. |
Disabled |
| Field weights | Allows the field weights to be set that apply when ranking the pages for search listing. The weight only applies when the field is in the query. To nullify the value of a field, use an insignificant amount, not 0, which may lead to unexpected behaviors, such as stripping results. One field per line, field_name:5.3 |
title:2.5 allowed_groups:0.... |
| Default content fields | All of the content is aggregated in the contents field. For custom weighting to apply, the fields must be included in the query. This option allows other fields to be included in the default content search. | contents, title |
| Cache per user and query | Time in minutes a user has a same query cached In minutes |
0 |
| Search formatters to cache | Search formatters to cache the output of | Categorylist |
| Format to use for tracker field keys | Choose between field IDs and permanent names for the tracker indexing Permanent name | Field ID (backward compatibility mode with Tiki 7 and 8) |
Permanent name |
| Use unified search in category admin | Use unfied search to find objects to add to categories. Limits types of objects available to those included in the unified index. | Disabled |
| Automatically Trim Elasticsearch results on Date-Sorted Query | Automatically trim Elastic Search results in unified search if the query is sorted by modification or creation date. | Disabled |
| Show error on missing field | When using LIST plugin to specify certain fields, especially tracker fields, this check helps ensure their names were entered correctly. | Enabled |
| Stop Word List | Words excluded from the search index as they can be too frequent and cause noise. MySQL full-text search has its own list of stop words configured in the server. |
a, an, and, are, as, at, be... |
| MySQL full-text search | Also known as 'Basic Search'. This search uses the MySQL full-text search feature. The indexation is continuously updated. Deprecated: This feature is unmaintained and may not be reliable. InnoDB doesn't support Full-Text Search earlier than version 5.6. |
Disabled |
| Referer search highlighting | Referrer search highlighting is when a user goes to a search engine such as Google or Yahoo and performs a search that generates links to your pages. When they click on the link and this feature is active, Tiki notices that they have come from a search engine site and highlights the search words they used. The result is similar to using the search using Tiki’s own search facility. | Enabled |
| Ignore individual object permissions | allow forbidden items in search result Will improve performance, but may show forbidden results Will improve performance, but may show forbidden results. |
Disabled |
| Ignore category viewing restrictions | allow showing forbidden (restricted) items in search result Will improve performance, but may show forbidden results Will improve performance, but may show forbidden results |
Disabled |
| Autocomplete page names | Automatically complete page names as the user starts typing. For example the user types the start of the wiki page name “Sear” and Tiki returns “Search”, “Search General Settings”, etc deprecated |
Disabled |
| Forum name search | When listing forums | Disabled |
| Forum content search | When listing forums | Enabled |
| Topic content search | Enabled | |
| Tiki-indexed search. | Disabled | |
| Use database (full-text) search. | Disabled |
Tiki 15 Preferences Image
| Option | Description | Default |
|---|---|---|
| Unified Search Index | Enables searching for content at the site using a Tiki-managed index. Unified Search requires server processing resources and that you properly set the server permissions. It's recommended to set a cron job to periodically rebuild the search index. |
Enabled |
| Search statistics | This option enables administrators to collect and view statistics on search activity. | Disabled |
| Users available in search results | Users available within search results. Content related to the user will be included in the index. None | All | Public |
None |
| Incremental Index Update | Update the index incrementally as the site content is modified. This may lead to lower performance and accuracy than processing the index on a periodic basis. This may lead to lower performance and accuracy than processing the index on a periodic basis. |
Enabled |
| Memory limit to apply during search index rebuild | Temporarily adjust the memory limit to use during search index rebuild. Depending on the volume of data, some large operations require more memory. Increasing it locally, per operation, allows to keep a lower memory limit globally. Keep in mind that memory usage is still limited to what is available on the server. for example: 256M |
None |
| Time limit to apply during search index rebuild | Temporarily adjust the time limit to use during search index rebuild. Depending on the volume of data, some requests may take longer. Increase the time limit locally to resolve the issue. Use reasonable values. seconds |
None |
| Unified search engine | Search engine used to index the content of your Tiki. Some engines are more suitable for larger sites, but require additional software on the server. Lucene (PHP implementation) | MySQL full-text search | ElasticSearch |
MySQL full-text search |
| Highlight results snippets | Highlight the result snippet based on the search query. Enabling this option will impact performance, but improve user experience. May impact performance |
Disabled |
| Parse the results | Parse the results. May impact performance May impact performance |
Disabled |
| Lucene index location | Path to the location of the Lucene search index. The index must be on a local filesystem with enough space to contain the volume of the database. | temp/unified-index |
| Lucene maximum results | Maximum number of results to produce. Results beyond these will need a more refined query to be reached. | 200 |
| Lucene maximum result-set limit | This is used when calculating result scores and sort order which can lead to out of memory errors on large data sets. The default of 1000 is safe with the PHP memory_limit set to 128M Maximum size of result set to consider. Default 1000, 0 = unlimited. 0 for unlimited |
1000 |
| Lucene terms per query limit | Maximum number of terms to be generated. Try increasing this value if you get errors saying "Terms per query limit is reached" espescially with wildcard, range and fuzzy searches. | 1024 |
| Lucene maximum number of buffered documents | Number of documents required before the buffered in-memory documents are written into a new segment. | 10 |
| Lucene maximum number of merge documents | Largest number of documents merged by addDocument(). Small values (for example, less than 10,000) are best for interactive indexing, as this limits the length of pauses while indexing to a few seconds. Larger values are best for batched indexing and speedier searches. Small values (for example, less than 10,000) are best for interactive indexing. Use 0 for the Lucene default, which is practically infinite. |
0 |
| Lucene merge factor | How often segment indices are merged by addDocument(). With smaller values, less RAM is used while indexing, and searches on unoptimized indices are faster, but indexing speed is slower. With larger values, more RAM is used during indexing, and while searches on unoptimized indices are slower, indexing is faster. Thus larger values (> 10) are best for batch index creation, and smaller values (< 10) for indices that are interactively maintained. Large values (greater than 10) are best for batch index creation, and smaller values (less than 10) for indices that are interactively maintained. |
10 |
| ElasticSearch URL | URL of any node in the cluster. | http://localhost:9200 |
| ElasticSearch index prefix | Prefix used for all indexes for this installation in ElasticSearch. | Tiki_ |
| ElasticSearch current index | A new index is created upon rebuild and the old one is then destroyed. This setting allows you to see the currently active one. Do not change this value unless you know what you are doing. |
None |
| Default Boolean Operator | Use OR (default) or AND as the default search operator. OR | AND |
None |
| Excluded categories | List of category IDs to exclude from the search index. | None |
| Excluded plugins | List of plugin names to exclude while indexing. | None |
| Exclude all plugins | If enabled, indexing will exclude all plugins. | Enabled |
| Except included plugins | List of plugin names that are required to be included while indexing, when excluding all. | None |
| Index forum replies together with initial post | If enabled, forum replies will be indexed together with the initial post as a single document instead of being indexed separately | Enabled |
| Tokenize version numbers | Tokenize version number strings so that major versions are found when sub-versions are mentionned. For example, searching for 2.7 would return documents containing 2.7.4, but not 1.2.7. | Disabled |
| Tokenize CamelCase words | Consider the components of camel-case words as separate tokens, allowing them to be searched individually. ElasticSearch only Conflicts with Tokenize Version Numbers. |
Disabled |
| Field weights | Allows the field weights to be set that apply when ranking the pages for search listing. The weight only applies when the field is in the query. To nullify the value of a field, use an insignificant amount, not 0, which may lead to unexpected behaviors, such as stripping results. One field per line, field_name:5.3 |
title:2.5 allowed_groups:0.... |
| Default content fields | All of the content is aggregated in the contents field. For custom weighting to apply, the fields must be included in the query. This option allows other fields to be included in the default content search. | contents, title |
| Cache per user and query | Time in minutes a user has a same query cached In minutes |
0 |
| Search formatters to cache | Search formatters to cache the output of | Categorylist |
| Format to use for tracker field keys | Choose between field IDs and permanent names for the tracker indexing Permanent name | Field ID (backward compatibility mode with Tiki 7 and 8) |
Permanent name |
| Use unified search in category admin | Use unfied search to find objects to add to categories. Limits types of objects available to those included in the unified index. | Disabled |
| Automatically Trim ElasticSearch results on Date-Sorted Query | Automatically trim Elastic Search results in unified search if the query is sorted by modification or creation date. | Disabled |
| Show error on missing field | When using LIST plugin to specify certain fields, especially tracker fields, this check helps ensure their names were entered correctly. | Enabled |
| Stop Word List | Words excluded from the search index as they can be too frequent and cause noise. MySQL full-text search has its own list of stop words configured in the server. |
a, an, and, are, as, at, be... |
| MySQL full-text search | Also known as 'Basic Search'. This search uses the MySQL full-text search feature. The indexation is continuously updated. Deprecated: This feature is unmaintained and may not be reliable. InnoDB doesn't support Full-Text Search earlier than version 5.6. |
Disabled |
| Referer search highlighting | Referrer search highlighting is when a user goes to a search engine such as Google or Yahoo and performs a search that generates links to your pages. When they click on the link and this feature is active, Tiki notices that they have come from a search engine site and highlights the search words they used. The result is similar to using the search using Tiki’s own search facility. | Enabled |
| Ignore individual object permissions | allow forbidden items in search result Will improve performance, but may show forbidden results Will improve performance, but may show forbidden results. |
Disabled |
| Ignore category viewing restrictions | allow showing forbidden (restricted) items in search result Will improve performance, but may show forbidden results Will improve performance, but may show forbidden results |
Disabled |
| Autocomplete page names | Automatically complete page names as the user starts typing. For example the user types the start of the wiki page name “Sear” and Tiki returns “Search”, “Search General Settings”, etc deprecated |
Disabled |
| Forum name search | When listing forums | Disabled |
| Forum content search | When listing forums | Enabled |
| Topic content search | Enabled | |
| Tiki-indexed search. | Disabled | |
| Use database (full-text) search. | Disabled |
Tiki 12 Preferences Image
| Option | Description | Default |
|---|---|---|
| MySQL Full-Text Search | Also known as 'Basic Search'. This search uses the MySQL Full-Text Search feature. The indexation is continuously updated. InnoDB doesn't support Full-Text Search until 5.6, so if this is your case, use Unified Search. |
Disabled |
| Referer Search Highlighting | Referrer search highlighting is when a user goes to a search engine such as Google or Yahoo and performs a search that generates links to your pages. When they click on the link and this feature is active, Tiki notices that they have come from a search engine site and highlights the search words they used. The result is similar to using the search using Tiki’s own search facility. | Enabled |
| Ignore individual object permissions | allow forbidden items in search result Will improve performance, but may show forbidden results Will improve performance, but may show forbidden results. |
Disabled |
| Ignore category viewing restrictions | allow showing forbidden (restricted) items in search result Will improve performance, but may show forbidden results Will improve performance, but may show forbidden results |
Disabled |
| Unified Search Index | Also known as 'Advanced Search'. Enables searching for content on the website, using Tiki-managed index. Unified Search requires more server processing resources, and that you properly set the server permissions. Also, it's recommended to set a cron job to periodically rebuild the search index. |
Disabled |
| Search stats | This option enables administrators to collect and view statistics on search activity. | Disabled |
| Users available in search results | Users available within search results. Content related to the user will be included in the index. None | All | Public |
None |
| Incremental Index Update | Update the index incrementally as the site content is modified. This may lead to lower performance and accuracy than processing the index on a periodic basis. This may lead to lower performance and accuracy than processing the index on a periodic basis. |
Enabled |
| Memory limit to apply during search index rebuild | Temporarily adjust the memory limit to use during search index rebuild. Depending on your volume of data, some large operations require more memory. Increasing it locally, per operation, allows to keep a lower memory limit globally. Keep in mind memory usage is still bound to what is available on the server. ex: 256M |
None |
| Time limit to apply during search index rebuild | Temporarily adjust the time limit to use during search index rebuild. Depending on the volume of data, some requests may take longer. Increase the time limit locally to resolve the issue. Use reasonable values. seconds |
None |
| Unified Search Engine | Search engine used to index the content of your Tiki. Some engines are more suitable for larger sites, but require additional software on the server. Lucene (PHP Implementation) | MySQL Full Text Search | ElasticSearch |
MySQL Full Text Search |
| Highlight results snippets | Highlight the result snippet based on the search query. Enabling this option will impact performance, but improve user experience. May impact performance |
Disabled |
| Parse the results | Parse the results. May impact the performance May impact performance |
Disabled |
| Lucene Index Location | Path to the location of the Lucene search index. The index must be on a local filesystem with enough space to contain the volume of the database. | temp/unified-index |
| Lucene Maximum Results | Maximum amount of results to expose. Results further than these will need a more refined query to be reached. | 200 |
| Lucene Maximum Result Set Limit | This is used when calculating result scores and sort order which can lead to out of memory errors on large data sets. The default of 1000 is safe with the PHP memory_limit set to 128M Maximum size of result set to consider. Default 1000, 0 = unlimited. 0 for unlimited |
1000 |
| Lucene Terms Per Query Limit | Maximum number of terms to be generated. Try increasing this value if you get errors saying "Terms per query limit is reached" espescially with wildcard, range and fuzzy searches. | 1024 |
| Lucene Max Buffered Documents | Number of documents required before the buffered in-memory documents are written into a new segment. | 10 |
| Lucene Max Merge Documents | Largest number of documents ever merged by addDocument(). Small values (e.g., less than 10,000) are best for interactive indexing, as this limits the length of pauses while indexing to a few seconds. Larger values are best for batched indexing and speedier searches. Small values (e.g., less than 10,000) are best for interactive indexing. Use 0 for the Lucene default, which is practically infinite. |
0 |
| Lucene Merge Factor | How often segment indices are merged by addDocument(). With smaller values, less RAM is used while indexing, and searches on unoptimized indices are faster, but indexing speed is slower. With larger values, more RAM is used during indexing, and while searches on unoptimized indices are slower, indexing is faster. Thus larger values (> 10) are best for batch index creation, and smaller values (< 10) for indices that are interactively maintained. Large values (> 10) are best for batch index creation, and smaller values (< 10) for indices that are interactively maintained. |
10 |
| ElasticSearch URL | URL of any node in the cluster. | http://localhost:9200 |
| ElasticSearch Index Prefix | Prefix used for all indexes for this installation in ElasticSearch. | Tiki_ |
| ElasticSearch Current Index | A new index is created upon rebuild and the old one is then destroyed. This setting allows you to see the currently active one. Do not change this value unless you know what you are doing. |
None |
| Default Boolean Operator | Use OR (default) or AND as the default search operator. OR | AND |
None |
| Excluded categories | List of category ids to exclude from the search index. | None |
| Excluded plugins | List of plugin names to exclude while indexing. | None |
| Exclude all plugins | If enabled, indexing will exclude all plugins. | Enabled |
| Except included plugins | List of plugin names to force include while indexing, when excluding all. | None |
| Index forum replies together with root post | If enabled, forum replies will be indexed together with the root post as a single document instead of being separately indexed | Enabled |
| Tokenize version numbers | Tokenize version number strings so that major versions are found when sub-versions are mentionned. For example, searching for 2.7 would return documents containing 2.7.4, but not 1.2.7. | Disabled |
| Field Weights | Allows the field weights to be set that apply when ranking the pages for search listing. The weight only applies when the field is in the query. To nullify the value of a field, use an insignificant amount, not 0, which may lead to unexpected behaviors, such as stripping results. One field per line, field_name:5.3 |
title:2.5 allowed_groups:0.... |
| Default content fields | All of the content is aggregated in the contents field. For custom weighting to apply, the fields must be included in the query. This option allows other fields to be included in the default content search. | contents, title |
| Cache per user and query | Time in minutes a user has a same query cached In minutes |
0 |
| Search formatters to cache | Search formatters to cache the output of | Categorylist |
| Format to use for tracker field keys | Choose between field ids and permanent names for the tracker indexing Permanent Name | Field ID (Backward compatibility mode with Tiki 7 and 8) |
Permanent Name |
| Use Unified Search in Category Admin | Use unfied search to find objects to add to categories. Limits types of objects available to those included in the unified index. | Disabled |
| Autocomplete on page names | Automatically complete page names as the user starts typing. For example the user types the start of the wiki page name “Sear” and Tiki returns “Search”, “Search General Settings”, etc deprecated |
Disabled |
| Forum name search | When listing forums | Disabled |
| Forum content search | When listing forums | Enabled |
| Topic content search | Enabled | |
| Tiki-indexed search. | Disabled | |
| Use database (full-text) search. | Disabled |
Tiki 12 Preferences Image
| Option | Description | Default |
|---|---|---|
| MySQL Full-Text Search | Also known as 'Basic Search'. This search uses the MySQL Full-Text Search feature. The indexation is continuously updated. InnoDB doesn't support Full-Text Search until 5.6, so if this is your case, use Unified Search. |
Disabled |
| Referer Search Highlighting | Referrer search highlighting is when a user goes to a search engine such as Google or Yahoo and performs a search that generates links to your pages. When they click on the link and this feature is active, Tiki notices that they have come from a search engine site and highlights the search words they used. The result is similar to using the search using Tiki’s own search facility. | Enabled |
| Ignore individual object permissions | allow forbidden items in search result Will improve performance, but may show forbidden results Will improve performance, but may show forbidden results. |
Disabled |
| Ignore category viewing restrictions | allow showing forbidden (restricted) items in search result Will improve performance, but may show forbidden results Will improve performance, but may show forbidden results |
Disabled |
| Unified Search Index | Also known as 'Advanced Search'. Enables searching for content on the website, using Tiki-managed index. Unified Search requires more server processing resources, and that you properly set the server permissions. Also, it's recommended to set a cron job to periodically rebuild the search index. |
Disabled |
| Search stats | This option enables administrators to collect and view statistics on search activity. | Disabled |
| Users available in search results | Users available within search results. Content related to the user will be included in the index. None | All | Public |
None |
| Incremental Index Update | Update the index incrementally as the site content is modified. This may lead to lower performance and accuracy than processing the index on a periodic basis. This may lead to lower performance and accuracy than processing the index on a periodic basis. |
Enabled |
| Memory limit to apply during search index rebuild | Temporarily adjust the memory limit to use during search index rebuild. Depending on your volume of data, some large operations require more memory. Increasing it locally, per operation, allows to keep a lower memory limit globally. Keep in mind memory usage is still bound to what is available on the server. ex: 256M |
None |
| Time limit to apply during search index rebuild | Temporarily adjust the time limit to use during search index rebuild. Depending on the volume of data, some requests may take longer. Increase the time limit locally to resolve the issue. Use reasonable values. seconds |
None |
| Unified Search Engine | Search engine used to index the content of your Tiki. Some engines are more suitable for larger sites, but require additional software on the server. Lucene (PHP Implementation) | MySQL Full Text Search | ElasticSearch |
MySQL Full Text Search |
| Highlight results snippets | Highlight the result snippet based on the search query. Enabling this option will impact performance, but improve user experience. May impact performance |
Disabled |
| Parse the results | Parse the results. May impact the performance May impact performance |
Disabled |
| Lucene Index Location | Path to the location of the Lucene search index. The index must be on a local filesystem with enough space to contain the volume of the database. | temp/unified-index |
| Lucene Maximum Results | Maximum amount of results to expose. Results further than these will need a more refined query to be reached. | 200 |
| Lucene Maximum Result Set Limit | This is used when calculating result scores and sort order which can lead to out of memory errors on large data sets. The default of 1000 is safe with the PHP memory_limit set to 128M Maximum size of result set to consider. Default 1000, 0 = unlimited. 0 for unlimited |
1000 |
| Lucene Terms Per Query Limit | Maximum number of terms to be generated. Try increasing this value if you get errors saying "Terms per query limit is reached" espescially with wildcard, range and fuzzy searches. | 1024 |
| Lucene Max Buffered Documents | Number of documents required before the buffered in-memory documents are written into a new segment. | 10 |
| Lucene Max Merge Documents | Largest number of documents ever merged by addDocument(). Small values (e.g., less than 10,000) are best for interactive indexing, as this limits the length of pauses while indexing to a few seconds. Larger values are best for batched indexing and speedier searches. Small values (e.g., less than 10,000) are best for interactive indexing. Use 0 for the Lucene default, which is practically infinite. |
0 |
| Lucene Merge Factor | How often segment indices are merged by addDocument(). With smaller values, less RAM is used while indexing, and searches on unoptimized indices are faster, but indexing speed is slower. With larger values, more RAM is used during indexing, and while searches on unoptimized indices are slower, indexing is faster. Thus larger values (> 10) are best for batch index creation, and smaller values (< 10) for indices that are interactively maintained. Large values (> 10) are best for batch index creation, and smaller values (< 10) for indices that are interactively maintained. |
10 |
| ElasticSearch URL | URL of any node in the cluster. | http://localhost:9200 |
| ElasticSearch Index Prefix | Prefix used for all indexes for this installation in ElasticSearch. | Tiki_ |
| ElasticSearch Current Index | A new index is created upon rebuild and the old one is then destroyed. This setting allows you to see the currently active one. Do not change this value unless you know what you are doing. |
None |
| Default Boolean Operator | Use OR (default) or AND as the default search operator. OR | AND |
None |
| Excluded categories | List of category ids to exclude from the search index. | None |
| Excluded plugins | List of plugin names to exclude while indexing. | None |
| Exclude all plugins | If enabled, indexing will exclude all plugins. | Enabled |
| Except included plugins | List of plugin names to force include while indexing, when excluding all. | None |
| Index forum replies together with root post | If enabled, forum replies will be indexed together with the root post as a single document instead of being separately indexed | Enabled |
| Tokenize version numbers | Tokenize version number strings so that major versions are found when sub-versions are mentionned. For example, searching for 2.7 would return documents containing 2.7.4, but not 1.2.7. | Disabled |
| Field Weights | Allows the field weights to be set that apply when ranking the pages for search listing. The weight only applies when the field is in the query. To nullify the value of a field, use an insignificant amount, not 0, which may lead to unexpected behaviors, such as stripping results. One field per line, field_name:5.3 |
title:2.5 allowed_groups:0.... |
| Default content fields | All of the content is aggregated in the contents field. For custom weighting to apply, the fields must be included in the query. This option allows other fields to be included in the default content search. | contents, title |
| Cache per user and query | Time in minutes a user has a same query cached In minutes |
0 |
| Search formatters to cache | Search formatters to cache the output of | Categorylist |
| Format to use for tracker field keys | Choose between field ids and permanent names for the tracker indexing Permanent Name | Field ID (Backward compatibility mode with Tiki 7 and 8) |
Permanent Name |
| Use Unified Search in Category Admin | Use unfied search to find objects to add to categories. Limits types of objects available to those included in the unified index. | Disabled |
| Autocomplete on page names | Automatically complete page names as the user starts typing. For example the user types the start of the wiki page name “Sear” and Tiki returns “Search”, “Search General Settings”, etc deprecated |
Disabled |
| Forum name search | When listing forums | Disabled |
| Forum content search | When listing forums | Enabled |
| Topic content search | Enabled | |
| Tiki-indexed search. | Disabled | |
| Use database (full-text) search. | Disabled |
Tiki 12 Preferences Image
| Option | Description | Default |
|---|---|---|
| MySQL Full-Text Search | Also known as 'Basic Search'. This search uses the MySQL Full-Text Search feature. The indexation is continuously updated. InnoDB doesn't support Full-Text Search until 5.6, so if this is your case, use Unified Search. |
Disabled |
| Referer Search Highlighting | Referrer search highlighting is when a user goes to a search engine such as Google or Yahoo and performs a search that generates links to your pages. When they click on the link and this feature is active, Tiki notices that they have come from a search engine site and highlights the search words they used. The result is similar to using the search using Tiki’s own search facility. | Enabled |
| Ignore individual object permissions | allow forbidden items in search result Will improve performance, but may show forbidden results Will improve performance, but may show forbidden results. |
Disabled |
| Ignore category viewing restrictions | allow showing forbidden (restricted) items in search result Will improve performance, but may show forbidden results Will improve performance, but may show forbidden results |
Disabled |
| Unified Search Index | Also known as 'Advanced Search'. Enables searching for content on the website, using Tiki-managed index. Unified Search requires more server processing resources, and that you properly set the server permissions. Also, it's recommended to set a cron job to periodically rebuild the search index. |
Disabled |
| Search stats | This option enables administrators to collect and view statistics on search activity. | Disabled |
| Users available in search results | Users available within search results. Content related to the user will be included in the index. None | All | Public |
None |
| Incremental Index Update | Update the index incrementally as the site content is modified. This may lead to lower performance and accuracy than processing the index on a periodic basis. This may lead to lower performance and accuracy than processing the index on a periodic basis. |
Enabled |
| Memory limit to apply during search index rebuild | Temporarily adjust the memory limit to use during search index rebuild. Depending on your volume of data, some large operations require more memory. Increasing it locally, per operation, allows to keep a lower memory limit globally. Keep in mind memory usage is still bound to what is available on the server. ex: 256M |
None |
| Time limit to apply during search index rebuild | Temporarily adjust the time limit to use during search index rebuild. Depending on the volume of data, some requests may take longer. Increase the time limit locally to resolve the issue. Use reasonable values. seconds |
None |
| Unified Search Engine | Search engine used to index the content of your Tiki. Some engines are more suitable for larger sites, but require additional software on the server. Lucene (PHP Implementation) | MySQL Full Text Search | ElasticSearch |
MySQL Full Text Search |
| Highlight results snippets | Highlight the result snippet based on the search query. Enabling this option will impact performance, but improve user experience. May impact performance |
Disabled |
| Parse the results | Parse the results. May impact the performance May impact performance |
Disabled |
| Lucene Index Location | Path to the location of the Lucene search index. The index must be on a local filesystem with enough space to contain the volume of the database. | temp/unified-index |
| Lucene Maximum Results | Maximum amount of results to expose. Results further than these will need a more refined query to be reached. | 200 |
| Lucene Maximum Result Set Limit | This is used when calculating result scores and sort order which can lead to out of memory errors on large data sets. The default of 1000 is safe with the PHP memory_limit set to 128M Maximum size of result set to consider. Default 1000, 0 = unlimited. 0 for unlimited |
1000 |
| Lucene Terms Per Query Limit | Maximum number of terms to be generated. Try increasing this value if you get errors saying "Terms per query limit is reached" espescially with wildcard, range and fuzzy searches. | 1024 |
| Lucene Max Buffered Documents | Number of documents required before the buffered in-memory documents are written into a new segment. | 10 |
| Lucene Max Merge Documents | Largest number of documents ever merged by addDocument(). Small values (e.g., less than 10,000) are best for interactive indexing, as this limits the length of pauses while indexing to a few seconds. Larger values are best for batched indexing and speedier searches. Small values (e.g., less than 10,000) are best for interactive indexing. Use 0 for the Lucene default, which is practically infinite. |
0 |
| Lucene Merge Factor | How often segment indices are merged by addDocument(). With smaller values, less RAM is used while indexing, and searches on unoptimized indices are faster, but indexing speed is slower. With larger values, more RAM is used during indexing, and while searches on unoptimized indices are slower, indexing is faster. Thus larger values (> 10) are best for batch index creation, and smaller values (< 10) for indices that are interactively maintained. Large values (> 10) are best for batch index creation, and smaller values (< 10) for indices that are interactively maintained. |
10 |
| ElasticSearch URL | URL of any node in the cluster. | http://localhost:9200 |
| ElasticSearch Index Prefix | Prefix used for all indexes for this installation in ElasticSearch. | Tiki_ |
| ElasticSearch Current Index | A new index is created upon rebuild and the old one is then destroyed. This setting allows you to see the currently active one. Do not change this value unless you know what you are doing. |
None |
| Default Boolean Operator | Use OR (default) or AND as the default search operator. OR | AND |
None |
| Excluded categories | List of category ids to exclude from the search index. | None |
| Excluded plugins | List of plugin names to exclude while indexing. | None |
| Exclude all plugins | If enabled, indexing will exclude all plugins. | Enabled |
| Except included plugins | List of plugin names to force include while indexing, when excluding all. | None |
| Index forum replies together with root post | If enabled, forum replies will be indexed together with the root post as a single document instead of being separately indexed | Enabled |
| Tokenize version numbers | Tokenize version number strings so that major versions are found when sub-versions are mentionned. For example, searching for 2.7 would return documents containing 2.7.4, but not 1.2.7. | Disabled |
| Field Weights | Allows the field weights to be set that apply when ranking the pages for search listing. The weight only applies when the field is in the query. To nullify the value of a field, use an insignificant amount, not 0, which may lead to unexpected behaviors, such as stripping results. One field per line, field_name:5.3 |
title:2.5 allowed_groups:0.... |
| Default content fields | All of the content is aggregated in the contents field. For custom weighting to apply, the fields must be included in the query. This option allows other fields to be included in the default content search. | contents, title |
| Cache per user and query | Time in minutes a user has a same query cached In minutes |
0 |
| Search formatters to cache | Search formatters to cache the output of | Categorylist |
| Format to use for tracker field keys | Choose between field ids and permanent names for the tracker indexing Permanent Name | Field ID (Backward compatibility mode with Tiki 7 and 8) |
Permanent Name |
| Use Unified Search in Category Admin | Use unfied search to find objects to add to categories. Limits types of objects available to those included in the unified index. | Disabled |
| Autocomplete on page names | Automatically complete page names as the user starts typing. For example the user types the start of the wiki page name “Sear” and Tiki returns “Search”, “Search General Settings”, etc deprecated |
Disabled |
| Forum name search | When listing forums | Disabled |
| Forum content search | When listing forums | Enabled |
| Topic content search | Enabled | |
| Tiki-indexed search. | Disabled | |
| Use database (full-text) search. | Disabled |
Tips
Improving search results for tags
On admin/search add freetags_text to these prefs:
- Field weights:
- freetags_text: 2.5
- title:1.5
- allowed_groups:0.0001
- categories:0.0001
- deep_categories:0.0001
- Default content fields:
- contents,title,freetags_text
;){kind=link}