...
Expand | ||||||
---|---|---|---|---|---|---|
| ||||||
XperienCentral R34Release date: November 18, 2021
Check Configuration FilesSee Check Configuration Files. Deprecated Media Repository Method RemovedThe following method which was deprecated in 2009 has been removed from
|
Expand | ||||||
---|---|---|---|---|---|---|
| ||||||
XperienCentral R33.1Release date: September 27, 2021
Check Configuration FilesSee Check Configuration Files. CSRF Approved URL SettingA new CSRF setting has been added that allows you to approve URLs and bypass the CSRF checks. See the setting
Minimum Java VersionBeginning in R33.1, the minimum Java version required to run XperienCentral is Java 11. The maximum Java version supported is Java 13. This is also required for the XperienCentral add-ons:
|
...
Expand | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
XperienCentral R33Release date: July 30, 2021
Check Configuration FilesSee Check Configuration Files. Google Sitemap Automatic UploadIn XperienCentral R33, a new setting for controlling whether XperienCentral automatically uploads generated sitemaps to Google has been introduced. The setting Because it is disabled by default, when upgrading from R32, the option must be enabled manually if XperienCentral should continue to automatically submit the sitemap to Google. New Channel for the Interactive Forms PanelBeginning in XperienCentral version R33, the Interactive Forms panel uses the "iafpanel" channel to render forms. This mechanism makes it possible to decouple the IAF visual representations from the website presentation. New presentations should use it for all standard fragment types unless the representation inside the IAF panel must resemble the website's presentation. When upgrading, there are 3 possible options for handling this situation:
CSRF SettingsTo better protect websites hosted by XperienCentral against CSRF attacks, a new mechanism has been introduced that uses a CSRF token that is stored in a cookie, and an SHA-256 hash of this token plus a random 16 character long nonce, postfixed with the used nonce, must be included in all non-GET requests to the server as a header or form field. This change could affect custom functionality in the following ways:
See also Security Guidelines for Developers for more information. formvalidationbindings.jsThe following changes have been made to the
Interactive Forms Upload ElementThe Upload element in Interactive Forms has been modified to allow multiple file uploads. You can also set a minimum and maximum number of allowed files in an Upload element. See Creating Forms for complete information. Modular Content Tag Property change (v2.0.13)Properties of type
Previously, the tag name would be retrieved using Previously in Java
Now in Java
Previously in JSP Code
Now in JSP Code
Interactive Forms Deprecated MethodsIn XperienCentral versions R33 and higher, the following form methods have been deprecated. FormScopeThe following method has been deprecated:
use the following method instead:
FormValuesMapThe following method has been deprecated:
use the following method instead:
UploadFragmentScopeAll methods have been deprecated. Use the following method instead:
|
...
Expand | ||||
---|---|---|---|---|
| ||||
XperienCentral R32Release date: May 12, 2021
Check Configuration FilesSee Check Configuration Files. Rebuild the Content IndexDue to a change in the Search functionality, you must rebuild the content index. To do so, manually remove the Check Google Sitemap Generator ScheduleIn R32, XperienCentral generates and uploads a Google Sitemap by default once per day. If you do not want to generate a sitemap, clear the field Changes to the XperienCentral APIRemoved MethodsThe following deprecated methods have been removed in R32:
Added MethodsThe methods
The purpose of the Lead field is to provide a short summary of the content item's content and can be used, for example, as a summary in a search function or in a Content Overview. One important difference is that, as designed, the Meta Description field is not meant to be visible to end users while the Lead Text is. The following methods have been moved from
Furthermore, the following methods have been added to
|
...
Expand | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||
XperienCentral R31Release date: March 4, 2021
Check Configuration FilesSee Check Configuration Files. Default Content Language
New WYSIWYG Editor in Interactive FormsIn XperienCentral R31, a new WYSIWYG editor has been introduced in Interactive Forms. It generates HTML in a slightly different way than the old editor. The changes introduced by the new WYSIWYG editor are:
After ugrading to XperienCentral R31, HTML already stored in existing form elements remains unchanged. All new HTML produced after the upgrade will be generated in the new way. If you edit an existing WYSIWYG form element, it will be upgraded after saving. In some cases, extra whitespace may be introduced between elements. GX Software recommends that you check new or modified WYSIWYG form elements after upgrading to R31 in order to determine whether you need to tweak your CSS to accommodate the behavior of the new WYSIWYG editor. Connector Definition for AJP/1.3 ConnectionsIn Tomcat versions 8.5.51, 9.0.31 and later, the connector definition in the
getPersonalizationXMLDataThe getPersonalizationXMLData method in the PersonalizationXMLDataProvider API has been changed from
to
If you use this method, you must refactor your code to cope with the modification. getMediaItemVersionsIn version R31 of XperienCentral, the tag Replace all instances of the
to
See getMediaItemVersions and the Javadoc for Delete Cache Before to Logging in to an XperienCentral R31 Installation Running LocallyDue to a change to internal JavaScript files in this release, GX Software strongly recommends that you delete your browser cache if you run a local installation of XperienCentral R31 after upgrading but before logging in for the first time. This does not apply to XperienCentral running on an Apache web server. GX WebManager JUnit Wrapper BundleBeginning in XperienCentral version R31, the JUnit wrapper bundle is no longer deployed to XperienCentral by default. It is possible that plugins (including any reusables) built against older versions of XperienCentral still have an indirect dependency on this plugin which results in those dependent plugins not starting when XperienCentral is started. There are two ways to fix this issue:
|
...
Expand | ||||
---|---|---|---|---|
| ||||
XperienCentral R30.1Release date: December 10, 2020
Check Configuration FilesSee Check Configuration Files. XSS Features
External Application Support
Uploaded File Handling
See also Linux Server Installation. xss_allowlist_siteworks_expressionsThe setting |
...
Expand | ||||
---|---|---|---|---|
| ||||
XperienCentral R29.3Release date: December 2, 2020
Check Configuration FilesSee Check Configuration Files. XSS Features
External Application Support
Uploaded File Handling
See also Linux Server Installation. xss_allowlist_siteworks_expressionsThe setting |
...
Expand | ||||
---|---|---|---|---|
| ||||
XperienCentral R30Release date: October 28, 2020
Check Configuration FilesSee Check Configuration Files. |
...
Expand | ||||
---|---|---|---|---|
| ||||
XperienCentral R29.2Release date: October 8, 2020
Check Configuration FilesSee Check Configuration Files. |
...
Expand | ||||
---|---|---|---|---|
| ||||
XperienCentral R29.1
Release date: September 7, 2020
Check Configuration FilesSee Check Configuration Files. Changes to the Interactive Forms Date ValidatorThe date validator in Interactive Forms now only accepts the Additionally, you need to check any post-processing code that further handles dates submitted in an Interactive Form. For example, if the date submitted in the form is used in an email handler or stored in a database, you need to evaluate how this change affects any further processing you do on data received in forms. |
...
Expand | |||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||
XperienCentral R29
Release date: July 21, 2020
Check Configuration FilesSee Check Configuration Files. New Method for Retrieving Media Items in Content OverviewsIn this release, the Dynamic Content Overview now supports an explicit fallback language selection. For this implementation, the API of
For example, in
must be replaced by:
New Mechanism for Generating Download LinksBeginning in version R29, SEO URLs are now available for downloads. If download elements are linked to downloads in the Content Repository, a small change is required to use these new SEO URLs. The change must be applied to each presentation of a download element (any presentation with scope
Beginning in R29, use the
New Security Protocol Setting for Frontend ServersIn XperienCentral R29, a new preview functionality was introduced. Among other things, this feature enables visitors who do not have permission to log in to the XperienCentral backend to nevertheless preview unpublished content. For this reason, the new setting
|
...
Expand | ||||
---|---|---|---|---|
| ||||
XperienCentral R28Release date: May 13, 2020
Check Configuration FilesSee Check Configuration Files. Performance Dashboard is RemovedThe Performance Dashboard has been removed from XperienCentral in R28. Use the Monitoring Dashboard to view statistics and metrics related to your XperienCentral deployment. See also Administrative Pages. While the upgrade scripts for XperienCentral should in principle remove all components related to the Performance Dashboard, in some circumstances it may not, therefore you need to manually remove any remnants. Follow these steps:
See also Plugins Management Console. Code ChangesThe
must be changed to:
JCR IndexBeginning in R28, XperienCentral uses an XperienCentral-optimized indexing solution to support queries on frontend nodes instead of the Apache Jackrabbit JCR. This solution generally improves performance and drastically reduces the amount of time it takes to bring a new frontend node online in cloud deployments when traffic demands increase. The new indexing solution will always be used in XperienCentral even if the old JCR index is not disabled. The old JCR index should be disabled on production environments if possible. See also the new JCR Index Settings that have been added to the Setup Tool. JCR Query ReplacementIf you use custom JCR queries in your deployment, they should be replaced in order to use the new API. The following shows a typical query replacement: Queries similar to this:
should be changed to something like this:
Disabling the Built-in Apache Jackrabbit JCR IndexTo disable the old Apache Jackrabbit JCR index, follow these steps:
Content API User CredentialsIn the Connector API, there are two locations in Configuration > Import/Export Configuration where user credentials define which user account executes import/export jobs: one on the Configuration tab and one on the Job tab. The Job tab previously contained the fields "Username", "Password" and "Use application key". The Cofiguration tab contained the same fields with an additional "Website" field. These fields have been replaced by a single "User" drop-down list. In R28 a new System user option has been introduced in the User Authorization panel. Only user accounts designated as system users can be authorized to execute automated export/import jobs. Re-add Users as System UsersAfter upgrading to R28, the existing username(s) will still be used by the Connector API. As soon as you open either of the panels, however, the user(s) might not be selectable anymore and if you re-save the configuration, the jobs might stop running. This is the intended behavior. The solution is to navigate to the Authorization panel, designate new system users and then designate them as the user accounts that run jobs on the Configuration and Job tabs in Import/Export Configuration. |
...
Expand | ||
---|---|---|
| ||
XperienCentral R27Release date: March 26, 2020 Check Configuration FilesSee Check Configuration Files. Language Version Support for Media ItemsBeginning in XperienCentral 10.27.0, each version of a media item has a specific language defined for it. During the upgrade R27 or higher, each media item is assigned the default editing language of the home page. A consequence of this is that media items might not be shown any longer if its language differs from that of the page on which it should be shown. This is also the case for (lead) images stored in the Content Repository. This can be solved in many cases by defining a fallback language for the languages on your channel. If the fallback language for Dutch is set to English, for example, and there is no Dutch media item to be shown on a Dutch page, then the English version will be shown. This is the case for all kinds of media items, images as well as articles, for example. Check the following to ensure that media items in your channel(s) are handled appropriately:
Modify your Solr ConfigurationIn this version of XperienCentral, the Lucene version has been upgraded to version 6.6.6, therefore you must make the following changes to Change the declaration
to
and add the following declaration to the
Deprecated MethodThe following method has been deprecated in the XperienCentral API in this release:
Removed Methods/InterfacesThe following methods and interfaces have been removed from the XperienCentral API in this release:
Update your Presentation JSPsYou need to update your presentation JSPs if they use the following methods:
Perform a global search in your presentation JSPs for the string " |
...
Expand | ||
---|---|---|
| ||
XperienCentral R26.1Release date: January 21, 2020 Check Configuration FilesSee Check Configuration Files. Solr SearchThe search functionality has been upgraded to Solr 6 in this version of XperienCentral. After upgrading, perform the following steps in order to prepare your deployment for Solr 6:
Realtime indexing If you use real-time indexing (the XperienCentral Realtime Indexing reusable):
No realtime indexing
|
...