Loading...
 

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.



search-generalsettings
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
OR
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

search-generalsettings
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
OR
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

search-generalsettings
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
OR
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

search-generalsettings
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
OR
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

search-generalsettings
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
OR
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

search-generalsettings
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
OR
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



doc.tiki.org


Bootstrap

AdminGuide

UserGuide

Keywords

Keywords serve as “hubs” for navigation within the Tiki documentation. They correspond to development keywords (bug reports and feature requests):

Accessibility (WAI and 508)
Accounting (7.x)
Articles and Submissions
Backlinks
Banners
Batch (6.x)
BigBlueButton audio/video/chat/screensharing (5.x)
Blog
Bookmark
Browser Compatibility
Link Cache
Calendar
Category
Chat
Clean URLs
Comments
Communication Center
Compression (gzip)
Contacts (Address Book)
Contact us
Content Templates
Contribution (2.x)
Cookie
Copyright
Credit (6.x)
Custom Home and Group Home Page
Date and Time
Debugger Console
Directory of hyperlinks
Documentation link from Tiki to doc.tiki.org (Help System)
Docs 8.x
Draw 7.x
Dynamic Content
Dynamic Variable
External Authentication
FAQ
Featured links
File Gallery
Forum
Friendship Network (Community)
Gmap Google maps
Groups
Hotword
HTML Page
i18n (Multilingual, l10n, Babelfish)
Image Gallery
Import-Export
Install
Integrator
Interoperability
Inter-User Messages
InterTiki
Kaltura video management (4.x)
Karma
Live Support
Login
Logs (system & action)
Look and Feel
Lost edit protection
Mail-in
Map with Mapserver
Menu
Meta Tags
Mobile Tiki and Voice Tiki
Mods
Module
MultiTiki
MyTiki
Newsletter
Notepad
Payment
Performance Speed / Load
Permissions
Platform independence (Linux-Apache, Windows/IIS, Mac, BSD)
Polls
Profiles
Profile Manager
Report
Toolbar
Quiz
Rating
Feeds
Score
Search engine optimization
Search
Search and Replace
Security
Semantic links (3.x)
Shadowbox
Shadow Layers
Share
Shopping cart
Shoutbox
Slideshow
Smiley
Social Networks
Spam protection (Anti-bot CATPCHA)
Spellcheck
Spreadsheet
Stats
Surveys
Tags (2.x)
Task
Tell a Friend, alert + Social Bookmarking
TikiTests (2.x)
Theme CSS & Smarty
Trackers
Transitions (5.x)
TRIM
User Administration including registration and banning
User Files
User Menu
Watch
WebHelp
WebDAV (5.x)
Webmail
Web Services
Wiki 3D
Wiki History, page rename, etc
Wiki Page Staging and Approval (2.x)
Wiki Plugin extends basic syntax
Wiki Syntax
Wiki structure (book and table of content)
Workspace
WSOD
WYSIWYCA
WYSIWYG (2.x)
XMLRPC


Tiki Newsletter

Delivered fresh to your email inbox!
Newsletter subscribe icon
Don't miss major announcements and other news!
Contribute to Tiki
Show php error messages