...
Expand | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||
XperienCentral R36Release date: June 15, 2022
Check Configuration FilesSee Check Configuration Files. SEO UpdatesIn R35 and earlier, the To make sure this works as intended check the following settings in the Setup tool:
In R35, the default value was
If Apache is used, this field is usually empty and can be left as is.
The value of this field should be set to
Please also make sure that all changes in
|
Code Block | ||
---|---|---|
| ||
RewriteCond %{REQUEST_URI} !^/web/ RewriteCond %{REQUEST_URI} !^/admin/ RewriteRule ^/(.*)\.htm$ /web/$1.htm [PT,L] |
The last line should be updated to
Code Block | ||
---|---|---|
| ||
RewriteRule ^/(.*)\.htm$ /web/seo/$1.htm [PT,L] |
This applies to both the back- and frontend vhost
configurations.
In order to run XperienCentral without extensions at all, see Running XperienCentral without a Friendly URL Extension.
Update your Solr Configuration
In R36, the Solr version has been upgraded to version 8.11.1, therefore you must make the following changes:
In solrconfig.xml
, change the declaration:
<luceneMatchVersion>6.6.6</luceneMatchVersion>
to
<luceneMatchVersion>8.11.1</luceneMatchVersion>
The eDismax query parser parameter lowercaseOperators
now defaults to false
if the luceneMatchVersion
in solrconfig.xml
is 7.0.0 or above, therefore you must set the lowercaseOperators
parameter explicitly to true
:
<bool name="lowercaseOperators">true</bool>
The following spatial-related fields have been removed:
LatLonType
GeoHashField
SpatialVectorFieldType
SpatialTermQueryPrefixTreeFieldType
Choose one of these field types instead:
LatLonPointSpatialField
SpatialRecursivePrefixTreeField
RptWithGeometrySpatialField
Extra Steps
- Stop Tomcat if it is running.
- Remove the directory
<webmanager-root>/work/searchengine
. - If you have a custom
solrconfig.xml
, you need to modify it — open it in a text editor. - Save your custom
solrconfig.xml
. - Start Tomcat.
- Log in to XperienCentral.
Real-time indexing
If you use real-time indexing (the XperienCentral Realtime Indexing reusable):
- Navigate to Configuration > Realtime Indexing.
- Select the "Indexing" tab.
- Select all the websites that you want to index in the top part of the panel.
- Click [Index selected items].
No real-time indexing
If you do not use real-time indexing (the XperienCentral Realtime Indexing reusable):
- Open the Setup Tool.
- Select the Search Tools tab.
- Click [Index] in the "INDEX URL" section.
Rebuild the Content Index
Due to a change in the Search functionality, you must rebuild the content index. To do so, manually remove the <webmanager-root>/work/contentindex
directory after the upgrade and allow it to be regenerated after restarting XperienCentral. Selecting contentindex_queue_empty_reindex
in the General tab of the Setup Tool is not sufficient.
Expand | ||||
---|---|---|---|---|
| ||||
XperienCentral R35Release date: February 7, 2022
Check Configuration FilesSee Check Configuration Files. SSI URLsNew security measures were introduced in this version that prevent the manipulation of URLs that contain SSI object IDs and/or presentation IDs. In general the cache will still be filled with files that contain pre-upgrade SSI URLs after an upgrade, which will lead to SSIs not being loaded and to the following message being logged in the Catalina logs: nl.gx.webmanager.servlet.ControllerServlet.checkSsiObjectIdUrlSignature Block ssiObjectId request XXXXXXX because it is not allowed in this context This can be prevented by either clearing the frontend cache during the upgrade or, if that is not an option, by disabling the fragment.tag and fragmentLabel.tagThe files Changes to fragment.tagThis file has been updated to always render the HTML for the fragment label in the IAF Panel. Additionally, an ID is added to the Changes to fragmentLabel.tagIf you select "Required field" for a form fragment, you see that change immediately in the Interactive Forms panel. In earlier versions, this was not the case. In order to make this possible, the HTML is now always rendered in the Interactive Forms panel. |
...