Overview of all update notes
2.6
Change of index scheme in core0
In core0
the index scheme has changed. If you want to migrate the indexed documents from your current smart.finder installation, follow the migration instructions for the version update.
New bundle sf_bootstrap
A new bundle sf_bootstrap
has been added, which loads the basic components of smart.finder when the app starts.
This bundle is necessary for the start of smart.finder.
-
If you are using a custom app that already contains one of the collection bundles (starting with
sf_bundle-set_…
), you do not need to do anything further. The bundlesf_bootstrap
is automatically loaded in this case. -
If the app does not contain any of the collection bundles
sf_bundle-set…
, please add the bundlesf_bootstrap
to your app as shown in the following example:{ "allowedBundles": [ "sf_bootstrap", "..." ] }
2.5
Password in security mode 'INTEGRATED'
For security reasons, the administrator password in security mode INTEGRATED
is no longer preset in the delivery. Set this using the security.user.admin.pw
property to enable logging in to the smart.finder.
Change of the index scheme in indexingmanagement
.
In indexingmanagement
the index scheme has changed. Follow the information in migration guide for the version update.
Change of index scheme in core0
.
In core0
the index scheme has changed. If you want to migrate the indexed documents from your current smart.finder installation, follow the migration instructions for the version update.
sf_search-ui-connector
-Bundle
The SearchAnythingSearchTermResetAction
component has been removed.
You can now control the behaviour of the search with an empty search term through the searchAllOnEmptySearchTerm
property of the ResultListPageForwarder
component.
See the sf_search-ui-connector bundle documentation for additional information.
sf_resultlist.SortConfig
component
Due to the new sorting component the configuration schema of the SortConfig
component in the sf_resultlist
bundle has been changed.
So if you made adjustments to this component in your app.json
files, see the sf_resultlist bundle documentation for details on how to update you configuration to the current schema.
Dropped leading dot in cookie domain
In prior versions of smart.finder the cookie domain in the configuration property security.sso.cookie.domain
required a leading dot. This dot is no longer supported. So specify the domain without a leading dot in compliance with RFC 6265. Example:
security.sso.cookie.domain=sub.example.com
2.4
Password in security mode 'INTEGRATED'
For security reasons, the administrator password in security mode INTEGRATED
is no longer preset in the delivery. Set this using the security.user.admin.pw
property to enable logging in to the smart.finder.
Change of the index scheme in indexingmanagement
.
In indexingmanagement
the index scheme has changed. Follow the information in migration guide for the version update.
Change of index scheme in core0
.
In core0
the index scheme has changed. If you want to migrate the indexed documents from your current smart.finder installation, follow the migration instructions for the version update.
sf_search-ui-connector
-Bundle
The SearchAnythingSearchTermResetAction
component has been removed.
You can now control the behaviour of the search with an empty search term through the searchAllOnEmptySearchTerm
property of the ResultListPageForwarder
component.
See the sf_search-ui-connector bundle documentation for additional information.
sf_resultlist.SortConfig
component
Due to the new sorting component the configuration schema of the SortConfig
component in the sf_resultlist
bundle has been changed.
So if you made adjustments to this component in your app.json
files, see the sf_resultlist bundle documentation for details on how to update you configuration to the current schema.
Dropped leading dot in cookie domain
In prior versions of smart.finder the cookie domain in the configuration property security.sso.cookie.domain
required a leading dot. This dot is no longer supported. So specify the domain without a leading dot in compliance with RFC 6265. Example:
security.sso.cookie.domain=sub.example.com
2.3
sf_search-ui-connector
-Bundle
The SearchAnythingSearchTermResetAction
component has been removed.
You can now control the behaviour of the search with an empty search term through the searchAllOnEmptySearchTerm
property of the ResultListPageForwarder
component.
See the sf_search-ui-connector bundle documentation for additional information.
sf_resultlist.SortConfig
component
Due to the new sorting component the configuration schema of the SortConfig
component in the sf_resultlist
bundle has been changed.
So if you made adjustments to this component in your app.json
files, see the sf_resultlist bundle documentation for details on how to update you configuration to the current schema.
2.1
If you want to continue using your existing index, you only have to let the property solr.solr.home
point to the location of the index.
Then restart Tomcat.
Now all search results and indexing jobs should be available again.
If the search boxes are not displayed for a core, enter the following command in the browser:
https://<yourserver>/smartfinder-search/<CORENAME>/suggest?suggest.build=true
The suggestions will then be displayed again.
2.0
2.0.3
Due to the update to Apache Solr 8.6.2 the internal initialisation of the backend service has changed. Therefore, the following steps are necessary:
-
the JNDI entry
solr/home
in/META-INF/context.xml
, which refers to the index directory, is no longer used. For this purpose a new propertysolr.solr.home
is provided.If you have changed the location of
solr.home
, you must apply these changes by using thesolr.solr.home
property. -
In the configuration files of the cors used
[SOLR_HOME]/[CORE_NAME]/conf/solrconfig.xml
, you must ensure that the XML elementluceneMatchVersion
has the value 8.6.2:solrconfig.xml<?xml version="1.0" encoding="UTF-8" ?> <config> <luceneMatchVersion>8.6.2</luceneMatchVersion> [...] </config>
If you are using a customized file, make sure that the value matches.