Use case examples 

• A user searches for "Meier". There's a page about a person called "Meier" in the index, but there are also lots of other content containing the word "Meier" in the index. Since "Meier" is not in the title of the page (maybe the page is called "Our new CEO"), the page is not ranked very high for this search word. We want the result for the page about "Meier" to be at the top, therefore we add "Meier" as a boost keyword to the page record.
• A user searches for "campingchair". There's a product called "campingchar" and there are also news articles, and other content containing the word "campingchair". We want the product result to be at the top, therefore we add "campingchair" as a boost keyword to that record.

Configuration 

You can enable/disable the boost keywords feature in the settings module in the extension configuration in the tab "Ranking".

The setting "Factor for boost keywords" allows you to define how strong the keywords should be weighted which means the higher you set this value, the stronger the "boost effect" will be.

Make sure set the sorting in the search plugin to "Relevance DOWN" in order to make the feature work!

Usage 

After activating the feature you can use the standard "keywords" field in pages and news records to add your keywords (comma-separated). The boosting effect will only work for search words matching exactly the given keywords. If in doubt which spelling or style the user will use, just add more keywords (eg "car,cars,vehicle,vehicles").

Example 

In this example we search for the word "album" in set of randomly imported articles from wikipedia.

One of the results is the article "Naimee Coleman". Without the boost keyword feature activated, this results ranks as #7 for the search word "album". We want this result to rank higher.

We now give the new record the keyword "album".

After activating the boost keywords feature (see above: "Configuration") you will have to restart the indexer.

The result does now rank higher:

If the effect should be stronger, we can adjust the setting "Factor":

The result is now at the top of the list:

Adding your own keywords 

If you want to add your own keywords as boost keywords or if you want to add keywords to other content types than pages or news, you will have to fill the column "boostkeywords" of the table "tx_kesearch_index" with your keywords. You can use the hooks ke_search provides. Please have a look at

Classes/Hooks/BoostKeywords.php

Use case examples 

• Show all page records before other records (eg. files or news).
• Show product pages on top.
• Show pages about persons on top.
• Show certain results at the end of the list.

Configuration 

You can enable/disable the custom ranking feature in the settings module in the extension configuration in the tab "Ranking".

After that please set the sorting to "Custom ranking DOWN" and "Relevance DOWN" in the plugin options (needs at least ke_search 3.1.5).

Usage 

You will find a field "Custom ranking value" in the page properties in the tab "Search" and in indexer configurations.

By setting this value, the page or the records fetched by this indexer configuration will be sorted to the very top of the result list. If both values are set, they will be summed up. You can also set negative values to push results to the end of the list.

Example 

In this example we have a page about the CTO of a company, "Mark Bristol". Search for "Bristol" shows also some news containing the word "Bristol".

We want to show the "CTO"-page on top of the list, thus we give it a custom ranking value of "1".

After re-indexing, the page is at the top of the list. Note that this page now will always be on top of the list, whenever it appears in the search result list. If you only want to give it a push when someone searches for "Bristol" you should use the Boost Keywords feature.

Adding your own custom ranking values 

If you want to use custom ranking values for your own indexers, you will have to fill the column "customranking" of the table "tx_kesearch_index" with the desired value. You can use the hooks ke_search provides. Please have a look at the Custom ranking hook class at

Classes/Hooks/CustomRanking.php

Technical background 

This features uses the column "content_hidden" of ke_search (introduced in version 4.5.0) to store partial words which will then be searched but not shown in the result list.

Use case examples 

• Find strings even if they are inside other words, e.g. if someone searches for "store", results with "bookstore" will be found.

Configuration 

You can enable/disable the in-word-search feature in the settings module in the extension configuration in the tab "Basic Settings".

After that please do a full indexing.

Usage 

Use the frontend search box to find words inside other words.

Example 

In this example we search for "paper" and find results which contain the word "newspapers".

Content Security Policy (CSP) 

Since version 7.0.0, the autocomplete feature is compatible with TYPO3's Content Security Policy (CSP). The logic is stored in an external JavaScript file, and configuration data is passed to the search input elements via data attributes. If your TYPO3 setup uses CSP nonces, these will be automatically applied to the configuration script.

Configuration 

You can enable/disable the autocomplete feature in the settings module in the extension configuration.

After enabling the checkbox for autocomplete and a "clear cache", the needed TypoScript files will be included automatically; there's no need to add a template manually.

Classes/Middleware/Autocomplete.php

EXT:ke_search_premium/Configuration/TypoScript/Autocomplete/constants.typoscript
EXT:ke_search_premium/Configuration/TypoScript/Autocomplete/setup.typoscript

Configuration 

System requirements 

• "curl" has to be installed.
• Activate distance search (see chapter "How to activate the distance search")
• This feature does not work together with the boost keywords feature.
• Since distance calculation is done within MySQL, it is not possible to use "Sphinx" at the same time.

How to activate the distance search 

• Install "tt_address" and create address records. By default the distance search is based on tt_address. It is possible to use other types of records (see below).
• Go to "Admin Tools" --> "Settings" --> "Extension configuration" --> "ke_search_premium" and enable the distance search in the tab "distancesearch" (option "Enable the distance search")
• Geocoding is done using the Geocoding API provided by Google (https://developers.google.com/maps/documentation/geocoding/). You need a Google Geocoding API key for backend geocoding. Set it as googleapikeyserver in the extension configuration tab distancesearch. (If there are errors during geocoding, they will be logged to the ke_search log file.)
• Map rendering in the frontend uses the Google Maps JavaScript API. You need a browser key (googleapikeybrowser) and a Map ID (googlemapsmapid) in the extension configuration tab distancesearch. The map marker rendering uses google.maps.marker.AdvancedMarkerElement, which requires a Map ID. If no map ID is configured, DEMO_MAP_ID is used as a fallback.
• In the tab "distancesearch" fill out the country field. This is used for geocoding the zip or city in the search form and for the addresses if no country is given.
• In order to display the distance and the map in the frontend, you can place markers in your own template or activate the options "display distance in standard-template" and "display map in standard-template" in the extension-manger.
• If you use the default template, you can show the distance for each result by activating Add distance to default template in the ke_search_premium extension settings in the tab distancesearch. If you use your own template you can use the variable {distance} in the Subpart ResultRow partial to show the distance.
• If you use the default template, you can show the map by enabling Add map to default template in the ke_search_premium extension settings. If you use your own template you can use the snippet <div id="map-canvas"></div> in the ResultList partial to show the map.
• To show the distance search in the frontend create a filter record of type "Distance search". This filter type does not have filter options.
• Add this filter to the list of filters to be displayed in your plugin "Searchbox and filters".
• Add a indexer configuration of type "Addresses (tt_address)". Geocoding will be done upon the next indexing.

Configuration 

The distance search configuration can be adjusted using this TypoScript (see Configuration/TypoScript/Distancesearch/setup.typoscript):

plugin.tx_kesearchpremium {
    distancesearch {
        templatepath = EXT:ke_search_premium/Resources/Private/Templates/DistanceSearch/
        radiusoptions = 10,20,50,100,200
        radiuslabel = km
    }
}
page.includeCSS.keSearchPremiumGoogleMapsCss = EXT:ke_search_premium/Resources/Public/Css/google-maps.css

Geocode own content 

In order to geocode your own content you will have to create a hook in your own extension and do the geocoding.

Please have a look at the hook modifyAddressIndexEntry (ke_search_premium/Classes/DistanceSearch/DistanceSearch.php) delivered with ke_search_premium.

Troubleshooting 

If geocoding or distance search does not work, please check the following:

• Check if the Geocoding API key (googleapikeyserver) is correct.
• Check if the browser key (googleapikeybrowser) is correct.
• Check if a valid Google Map ID (googlemapsmapid) is configured when the map is enabled.
• Check if the country is set in the extension configuration.
• Check the ke_search log file for errors. If Google Maps returns an error, this will be logged.

Configuration steps 

• Install ke_search_premium in the main and in the remote TYPO3 instance.
• Activate the "API" function in the extension manager.
• On the remote website: Set username and password in the "API" tab.
• On the main website: Add an indexer configuration. Configure the domain, login data and page uid on which the search index is saved in the remote instance.
• Starting the indexer will now transfer the data from remote to the main instance where it can be searched.
• You can set a tag in order to use facetting for the transfered data.

Activate API function 

Add an indexer configuration 

Restrictions 

There are some restrictions to take into account if you want to use the Sphinx feature:

• starttime and endtime restrictons won't be applied. So make sure you do not need those restrictions in your search results.
• Not all of the other features work together with the spinx feature such as the Boost Keywords, Custom Ranking, Distance based search with Google Maps integration and Synonyms features.
• Search words are always and-combined, not or.

Using Sphinx with ke_search 

Please follow these steps to activate the Sphinx support for ke_search:

wget http://sphinxsearch.com/files/sphinx-2.2.11-release.tar.gz
tar xzf sphinx-2.2.11-release.tar.gz
cd sphinx-2.2.11-release/
./configure --prefix=/var/www/my_directory/sphinx
make
make install

sudo apt-get install libmysql++-dev

sudo apt-get install build-essential libmariadb-dev-compat make

sudo apt-get install g++
make install

source tx_kesearch_index {
	type = mysql
	sql_host = [MySQL-Server] In most cases „localhost“
	sql_user = [Username for MySQL]
	sql_pass = [Password for MySQL]
	sql_db = [Databasename for MySQL]
	sql_query_pre = SET NAMES utf8
	sql_query = SELECT uid, title, tags, content, sortdate, CONCAT('_pid_', pid) as pid, CONCAT('_group_', REPLACE(IF(fe_group="", "NULL", fe_group), ',', ',_group_')) as fe_group, CONCAT('_language_', language) AS language FROM tx_kesearch_index
	sql_field_string = title
	sql_field_string = language
	sql_field_string = fe_group
	sql_attr_timestamp = sortdate
}
   index tx_kesearch_index {
	source = tx_kesearch_index
	path = /var/www/my_directory/sphinx/var/data/tx_kesearch_index
	charset_table = 0..9,A..Z->a..z,a..z,_,-,U+C4->U+E4,U+E4,U+D6->U+F6,U+F6,U+DC->U+FC,U+FC,U+DF,U+C0->U+E0,U+E0,U+C9->U+E9,U+E9
	min_word_len = 4
	min_prefix_len = 4
	min_infix_len = 0
}
indexer {
	mem_limit = 256M
}
searchd {
	listen = 9312
	log = /var/www/my_directory/sphinx/var/log/searchd.log
	pid_file = /var/www/my_directory/sphinx/var/log/searchd.pid
}

/var/www/my_directory/sphinx/bin/indexer –all

chown [user]:[group] /var/www/my_directory/sphinx/etc/sphinx.conf
chown -R [user]:[group] /var/www/my_directory/sphinx/var/data/

cd /var/www/my_directory/sphinx/bin/
./searchd

Configure TYPO3 extension 

• Go to the extension settings of ke_search_premium in the TYPO3 backend.
• Activate the Sphinx support with setting enableSphinxSearch in tab Sphinx
• Configure the paths to the Sphinx binaries indexer and searchd

min_infix_len = 1
min_prefix_len = 0

source tx_kesearch_index {
	type = mysql
	sql_host = ...
	sql_user = ...
	sql_pass = ...
	sql_db = ...
	sql_query_pre = SET NAMES utf8
	sql_query = SELECT uid, title, tags, content, sortdate, CONCAT('_group_', REPLACE(IF(fe_group="", "NULL", fe_group), ',', ',_group_')) as fe_group, CONCAT('_language_', language) AS language FROM tx_kesearch_index
	sql_field_string = title
	sql_field_string = language
	sql_field_string = fe_group
	sql_attr_timestamp = sortdate
}

Activate the synonym feature 

Please activate this feature in extension configuration first.

Add synonyms 

In order to add synonyms, please use the "List" module, and add "Synonym" record in your search storage page (where your indexer configuration is stored).

You have to enter each synonym in one line (divided by a line break).

Use case examples 

• Render search results with AJAX.
• Create a headless application and use ke_search in the backend.

Configuration 

Please install and configure ke_search, the indexers and the plugins as if you would use ke_search in non-headless context (see "Quickstart" in the ke_search documentation).

You can then use the extension settings module, open the "Headless" tab in the ke_search_premium settings and specify the UIDs of the ke_search plugins you want to make available for headless response.

After that you need to include the static template "Faceted Search Premium - Headless" in your main template.

Alternatively, if you are using site sets, you can add the site set "Faceted Search Headless".

A new plugin will appear and you need to switch both search plugins (searchbox and result list) to their "cachable" versions.

Please also specify the IP address(es) from which access to the headless function should be allowed. Although it is possible to use "*" to make the headless function publicly available, it is recommended to limit the access to only the IP address of your application, because the response will include full database rows e. g. from the pages table (in the "orig_row" property) which may disclose information you want to keep private.

You will also need to specify the fields which should be exposed to the public by defining a whitelist. This is a semicolon-separated list of fields which should be included in the response. Fields in a multidimensional array must be combined with a dash, the sub-fields must then be added with a colon and separated with a colon.

Example for the fields whitelist:

page;searchword;searchwordDefault;sortByField;sortByDir;filters;filters:title,name,id,checkboxOptions;filters-checkboxOptions:title,tag,slug,key,id

Overwriting the headless response 

There is also a hook which you can use to overwrite the configuration for the headless response. The hook is called "modifyHeadlessConfiguration". See Class

Classes/Middleware/HeadlessApiMiddleware.php

Usage 

You can access the headless function by adding the parameter "tx_kesearch_pi1[headless_ce]" to specify the content element from which you want to receive the JSON response. The other parameters are the same as you would access ke_search in non-headless mode. Please add the "no_cache" parameter.

Examples 

For the following examples we assume that the content element with the UID 308 is our search box plugin and the UID 309 is our search result plugin.

Default result list 

Calling the result list plugin without any further parameters will give you the first 10 results (if not configured otherwise in the plugin settings).

https://my.example.org/?tx_kesearch_pi1[headless_ce]=309&no_cache=1

Copied!

Search plugin (including filters) 

Calling the search box plugin will give you the search configuration including the filters.

https://my.example.org/?tx_kesearch_pi1[headless_ce]=308&no_cache=1

Copied!

https://my.example.org/?tx_kesearch_pi1[headless_ce]=309&tx_kesearch_pi1[sword]=my%20search%20phrase&no_cache=1

https://my.example.org/?tx_kesearch_pi1[headless_ce]=309&tx_kesearch_pi1[filter_11]=syscat84&no_cache=1

https://my.example.org/?tx_kesearch_pi1[headless_ce]=309&tx_kesearch_pi1[filter_3_273]=fruits&tx_kesearch_pi1[filter_3_302]=syscat94&no_cache=1

More parameters 

You can use all the parameters ke_search supports in the non-headless mode (like sorting, pagebrowser settings etc.):

• sword
• filter
• page
• sortByField
• sortByDir

Upgrading from ke_search_premium 5 to 6 

If you have previously used the headless feature in ke_search_premium 5, you will need to update the "Type" of result list content element from "Insert Plugin" to "Faceted search - Cachable Results".

Version 7.0.0 (18 June 2026) 

• [!!!] This version works with TYPO3 14 and 13 and drops support for TYPO3 12.
• [FEATURE] Improve autocomplete feature by adding compatibility with TYPO3's Content Security Policy (CSP).
• [TASK] Make Distance Search and Google Maps rendering compatible with TYPO3 CSP by adding nonce-aware inline assets and dedicated CSP directives.
• [TASK] Bump TYPO3 and ke_search version requirements to support newer versions.
• [TASK] Remove TYPO3 12-specific hook for query modification.
• [TASK] Update composer dependencies to align with TYPO3 13 and 14 compatibility.
• [TASK] Add unit tests for Autocomplete feature
• [TASK] Migrate Google Maps marker rendering from deprecated google.maps.Marker to google.maps.marker.AdvancedMarkerElement and add extension setting googlemapsmapid (fallback: DEMO_MAP_ID).
• [TASK] Refactor autocomplete configuration handling
• [TASK] Refactor NoResultsHandler
• [TASK] Add extension title to localization file (for usage in the new record wizard)
• [TASK] Add extension title in composer.json description (for usage in the extension manager)
• [TASK] Migrate remote indexer: Refactor FetchIndexEntries and Api middleware
• [TASK] Refactor modifyFieldValuesBeforeStoring to simplify checks and improve null handling
• [TASK] Integrate request handling in Headless API and DistanceSearch classes
• [TASK] Add site set for Headless API
• [BUGFIX] Adjust return property type in class KeSearchPremium (Sphinx API) to allow false to allow logging of errors
• [DOCS] Add alternative text for images in feature documentation to improve accessibility

Version 6.0.3 (11 November 2025) 

• [BUGFIX] Correct handling of synonyms in ModifySearchWords class to avoid problems with "explicit and" setting

Version 6.0.2 (26 August 2025) 

• [BUGFIX] Show missing FlexForm in cached result list plugin
• [BUGFIX] Fix potential null return in preg_replace usage
• [BUGFIX] Fix dependency range for ke_search

Version 6.0.1 (4 April 2025) 

• [BUGFIX] Fix bug with boost keywords in ke_search 6.2.0 and above

Version 6.0.0 (20 December 2024) 

• [!!!] This version works with TYPO3 13 and 12 and drops support for TYPO3 11.
• [TASK] Update requirements, require TYPO3 12 or 13, drop TYPO3 11
• [TASK] Make DistanceSearch feature compatible with TYPO3 13
• [TASK] Add type declarations in NoResultsHandler
• [TASK] Make "Did you mean" feature compatible with TYPO3 13
• [TASK] Make it possible to disable "Did you mean" via TypoScript
• [DOCS] Update documentation on "Did you mean" feature
• [TASK] Make Sphinx you mean" feature compatible with TYPO3 13
• [BUGFIX] Fix index so that sphinxLimit setting is visible in the extension manager
• [DOCS] Update documentation on Sphinx feature
• [TASK] Make Autocomplete feature compatible with TYPO3 13
• [DOCS] Update documentation on Autocomplete feature
• [TASK] Make Synonym feature compatible with TYPO3 13
• [DOCS] Update documentation on Synonym feature
• [TASK] Make Remote Indexer feature compatible with TYPO3 13
• [DOCS] Update documentation on Remote Indexer feature
• [TASK] Make Custom Ranking feature compatible with TYPO3 13
• [DOCS] Update documentation on Custom Ranking feature
• [TASK] Make Boost Keywords feature compatible with TYPO3 13
• [DOCS] Update documentation on Boost Keywords feature
• [TASK] Make Headless feature compatible with TYPO3 13
• [DOCS] Update documentation on Headless feature
• [TASK] Make In-Word-Search feature compatible with TYPO3 13
• [DOCS] Update documentation on In-Word-Search feature

Version 5.0.7 (23 August 2024) 

• [TASK] Clean up autocomplete result

Version 5.0.6 (16 August 2024) 

• [TASK] Make synonyms feature compatible with InnoDB
• [TASK] Remove dependency to TpwdKeSearchLibDb in Autocomplete.php
• [TASK] Respect language in autocomplete function. Note: The signature for the hook function "modifyAutocompleWordList" has changed. Please update your hook function accordingly if you create your own autocomplete words.

Version 5.0.5 (19 April 2024) 

• [BUGFIX] Avoid undefined array key warning for keywords. If a page has no translation and "CustomRanking" is activated an "undefined array key" error appeared. Thanks to Remo Häusler.

Version 5.0.4 (February 2024) 

• [BUGFIX] Avoid undefined array key warning for keywords
• [TASK] Remove obsolete "showRecordFieldList" property from TCA definition for table tx_kesearchpremium_synonym
• [BUGFIX] Remove type declaration for $pObj variables to make synonyms and "Did you mean" work again with ke_search 5.2.1. (In ke_search 5.2.1 the type of the "PluginBase" object has changed.)

Version 5.0.3 (November 2023) 

• [DOCS] Add note about using the fluid_styled_content for the headless feature
• [BUGFIX] Avoid array key not sent warning in HeadlessApiMiddleware

Version 5.0.2 (September 2023) 

• [TASK] Exclude ke_search_premium headless parameter from cacheHash calculation to avoid 404 error
• [DOCS] Add note about using the "cachable" searchbox plugin for headless

Version 5.0.1 (September 2023) 

• [BUGFIX] Fix extension setting for "Did you mean"

Version 5.0.0 (July 2023) 

• [!!!] This version works with TYPO3 12 and 11 and drops support for TYPO3 10.
• [!!!] The way how to set up the headless feature has changed for TYPO3 12. Please refer to the documentation.
• [TASK] Update requirements, require TYPO3 11 or 12, drop TYPO3 10
• [TASK] Update SphinxClient to avoid PHP warnings
• [TASK] Fix errors reported by PHPStan
• [TASK] Add type declarations
• [TASK] Migrate query builder function calls
• [TASK] Migrate constant TYPO3_MODE to TYPO3
• [TASK] Use LLL:EXT: syntax for language file reference
• [TASK] Add more information about failed geolocation to the log
• [TASK] Only store successful geolocation data in the cache
• [TASK] Update documentation
• [TASK] Migrate path configuration for autocomplete files to EXT: syntax to work with TYPO3 12
• [TASK] Make FetchIndexEntries function static to work with TYPO3 12
• [TASK] Use site router to build links instead of content object renderer
• [TASK] Migrate usage of GeneralUtility::_GP() and use ServerRequest instead
• [TASK] Use or instead of orX in queryBuilder
• [TASK] Remove obsolete second parameter from findWordsWhichBeginsWith()
• [TASK] Make headless feature work with TYPO3 12

Version 4.2.3 (March 2023) 

• [TASK] Add phpstan and php-cs-fixer
• [TASK] Fix code style issues found by php-cs-fixer
• [TASK] Fix issues reported by PHPStan
• [BUGFIX] Fix undefined array key issues in Autocomplete.php

Version 4.2.2 (December 2022) 

• [TASK] Treat synonyms as phrases, keep the original search string when synonyms are used and highlight synonyms in search result list

Version 4.2.1 (September 2022) 

• [BUGFIX] Fix error logging when geocoding failed
• [BUGFIX] Show sorting "Distance" when distance search is activated (fix deprecation)

Version 4.2.0 (September 2022) 

• [FEATURE] Partial word search (find searchstrings inside words) without the need of using Sphinx
• [BUGFIX] Fix PHP8 issues
• [TASK] Add Services.yaml and use correct file name for SphinxApi class
• [TASK] Refactor BoostKeywords to use new event "MatchColumnsEvent"
• [TASK] Raise ke_search dependency to 4.5.0

Version 4.1.0 (December 2021) 

• [!!!] This version works with TYPO3 10 and 11 and drops support for TYPO3 9.
• [TASK] Mark as compatible to TYPO3 11.5
• [TASK] Move language files from xml to xlf
• [TASK] Move TypoScript configuration files to Configuration/TypoScript and rename the ending from txt to typoscript
• [TASK] Make Autocomplete function compatible to TYPO3 11
• [TASK] Optimize Autocomplete function in order to make it work with multiple search forms on the page
• [TASK] Do not use underscore for filter names in distance search filter. Underscores must not be used for filter names (due to the fact that the routing features uses underscores to flatten filter arrays).
• [TASK] Initialize customranking value only if it not has been set before

Version 4.0.1 (October 2021) 

• [BUGFIX] Security Fix. Please update!

Version 4.0.0 (October 2021) 

• [TASK] Use namespace "tpwd" for ke_search_premium classes
• [TASK] Use new namespace "tpwd" for ke_search classes (has changed in ke_search 4.0.0)
• [TASK] Require twpd/ke_search
• [TASK] Require ke_search version 4.0.1
• [TASK] Log sphinx errors to ke_search logfile
• [TASK] Change eID class signature in order to adapt remote indexer feature to TYPO3 10
• [TASK] Include fields for the result list in the default fields for the headless response

Version 3.4.2 (September 2021) 

• [BUGFIX] Security Fix. Please update!

Version 3.4.1 (July 2021) 

• [TASK] Add whitelist for headless response fields
• [TASK] Add hook for headless configuration

Version 3.4.0 (June 2021) 

• [FEATURE] Add headless (JSON) response via MiddleWare
• [TASK] Add extension key to composer.json
• [TASK] Rearrange the settings in the extension manager (move settings from the basic tab to the tab they belong to)
• [TASK] Raise ke_search requirement to 3.8.1

Version 3.3.0 (January 2021) 

[!!!] This version changes the database structure!

• [TASK] Add ke_search 3.1.5 requirement
• [TASK] Synonyms: Use words as synonyms only if the full word matches exactly (no part word matches)
• [BUGFIX] Fix TYPO3 requirement (works with 9, not only 10) in ext_emconf.php to match composer.json

Version 3.2.0 (July 2020) 

• [BREAKING] Note: This version changes the database structure.
• [FEATURE] Add feature "Keyword Boost"
• [FEATURE] Add feature "Custom Ranking Boost"

Version 3.1.1 (January 2020) 

• [TASK] Set compatibility to TYPO3 10.4

Version 3.1.0 (January 2020) 

This version works with TYPO3 9.5 and 10.2.

• [TASK] Make distance search work with TYPO3 10.2, move TCA configuration to Configuration/TCA/Overrides, include static template automatically in ext_tables.conf (no need to add static template manually anymore), remove ext_tables.php.
• [TASK] Make autocomplete feature work with TYPO3 10.2
• [TASK] use ExtensionConfiguration API in ext_localconf.php.
• [TASK] remove "use" statement in ext_localconf.php.
• [TASK] use ExtensionConfiguration API in ext_tables.php.
• [TASK] remove "use" statement in ext_tables.php.
• [BUGFIX] Fix check for valid URL in remote indexer.
• [TASK] Do not use jQuery for the autocomplete feature but use plain javascript instead.
• [BUGFIX] remove wrong use statement in ModifySearchWords.php
• [TASK] Fix deprecation, replace getUserObj with makeInstance.

Version 3.0.0 (January 2019) 

This version works with TYPO3 9.5.

• [FEATURE] Make ke_search_premium compatible with TYPO3 9.5 and ke_search version 3.0.0
• [TASK] Use namespaced classes
• [TASK] move TCA to Configuration/TCA
• [TASK] use doctrine / query builder for database queries
• [TASK] remove ext_autoload.php
• [TASK] Move autocomplete javascript to the footer
• [BUGFIX] Fix including of TypoScript code for autocomplete feature

Version 2.1.0 (January 2018) 

• [FEATURE] Add configuration option for Google API (you'll need two keys, one for maps and one for geocoding).
• [FEATURE] Use SSL for Google API access.
• [FEATURE] Make ke_search_premium compatible with TYPO3 8.7 and ke_search Version 2.6.2.
• [BUGFIX] Fix bug "No columns definition in TCA table" in TYPO3 8.7

Version 2.0.0 (May 2016) 

• [FEATURE] Make ke_search_premium compatible with TYPO3 7.6 and ke_search Version 2.2.1.

Version 1.2.2 

• bugfix release

Version 1.2.1, February 2015 

• bugfix: fix typo
• bugfix: fix function header for google maps integration

Version 1.2.0, January 2015 

• feature: Add remote indexer. This new indexer allows to import search results from a different TYPO3 website. This feature makes it possible to search two or more TYPO3 websites using one search form. On the remote TYPO3 website ke_search and ke_search_premium have to be installed and configured.
• task: add image for remote indexer
• task: add note how to activate "in word search" in extension manager.

Version 1.1.2 

• feature: improve performance for large result sets by reducing the sorting to the first 1000 elements. After that, results will be unsorted.
• feature: improve autosuggest feature customization possibilites (new hook, pid checking).
• workaround for large result sets (> 50.000), TODO: optimize query so that this large amount of memory is not needed

Version 1.1.1, September 2014 

• Sphinx search bugfixing: Show correct number of results in filter options.
• feature: allow sphinx server name and port configuration in extension manager.
• feature: send email to administrator if sphinx reports an error.

Version 1.1.0, July 2014 

• Distance search and Google maps integration

Version 1.0.X 

• Sphinx support
• Autocomplete
• Did you mean?
• Synonyms