...
Expand | ||
---|---|---|
| ||
XperienCentral 10.22.0See also the XperienCentral 10.22 Changelog for information on the issues that have been fixed and other product improvements. DependencyManagerIn XperienCentral 10.22.0, the DependencyManager implementation has been changed. This has an impact for plugins that use the DependencyManager object in their Activator class with package name If the Compat library class For project plugins the refactoring should be straightforward when upgrading to XperienCentral 10.22 or higher. For plugins that must be deployed on all XperienCentral versions (reusables), a fix is available and implemented in the reusable Utility Services (version ?1.6.2). You must refactor your plugins or resuables in the following cases: Project PluginsIf your Activator uses the DependencyManager object with package name Reusable PluginsThe same situation applies as above, except you need to add an extra subclass in the Activator class in order to be compatible with XperienCentral versions 10.22.0 higher. If the reusable already uses the Utility Services dependency, you can use the If your Activator class uses the createServiceDependency method to add a Service to the DependencyManager (in REST cases for example), your must refactor this implementation to use the addServiceDependency method from the CompatibleActivatorBase class. If your Activator class does not use a DependencyManager object and the Activator class extends from the XperienCentral
Custom FacetsTwo facets for the keywords field have been added in this release. In order to be able to uniquely identify a facet, changes have been made that affect custom made facet components. The following changes must be made in your project code:
Other Changes
|
Expand | ||
---|---|---|
| ||
XperienCentral 10.21.1A problem has been fixed that caused deleted elements to not be completely removed which resulted in excessive space being taken up in the database. After upgrading and starting up XperienCentral for the first time, a task is executed that removes these deleted elements - in some environments, this could take some time to complete.
|
Expand | ||
---|---|---|
| ||
XperienCentral 10.18.0
|
Expand | |||||
---|---|---|---|---|---|
| |||||
XperienCentral 10.17.0
|
Expand | ||
---|---|---|
| ||
XperienCentral 10.16.1Adjust presentations where the
|
Expand | ||
---|---|---|
| ||
XperienCentral 10.16.0
|
Expand | ||
---|---|---|
| ||
XperienCentral 10.15.1The clientside
|
Expand | ||
---|---|---|
| ||
XperienCentral 10.15.0In order to make sure the
|
Expand | ||
---|---|---|
| ||
XperienCentral 10.14.0
|
Expand | ||
---|---|---|
| ||
XperienCentral 10.13.0
|
Expand | ||
---|---|---|
| ||
XperienCentral 10.12.1
|
Expand | ||
---|---|---|
| ||
XperienCentral 10.12.0
|
Expand | ||
---|---|---|
| ||
XperienCentral 10.11.0
|
Expand | ||
---|---|---|
| ||
XperienCentral 10.10.1Links are now filtered by scheme. Schemes that are not allowed result in removal of the illegal link. Allowed link schemes can be configured using the Setup Tool, property valid_link_schemes in the website settings. The following schemes are accepted by default:
|
Expand | ||
---|---|---|
| ||
XperienCentral 10.10.0
|
Expand | |||||
---|---|---|---|---|---|
| |||||
XperienCentral 10.9.0
|
Expand | ||
---|---|---|
| ||
XperienCentral 10.7.1XperienCentral 10.7.1 provides an oEmbed service to embed XC content in external oEmbed consumers. The presentation of this content is provided by some XC presentation files. An example implementation can be found in the
|
Expand | ||
---|---|---|
| ||
XperienCentral 10.7.0
|
Expand | ||
---|---|---|
| ||
XperienCentral 10.5.0The model in order to store personalizations has been refactored. As a result, export files created using the content export functionality in the setup tool of older XperienCentral versions containing personalizations or references to personalizations cannot be imported on XperienCentral 10.5.0 and vice versa.
|
Expand | ||
---|---|---|
| ||
XperienCentral 10.4.1
|
Expand | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
XperienCentral 10.4.0
|
Expand | ||
---|---|---|
| ||
XperienCentral 10.2.x or older to 10.3.0
|
Expand | ||
---|---|---|
| ||
GX WebManager 9.18.x, 9.19.x and 9.20.x to XperienCentral 10.x.x- The "javax.servlet:servlet" artifact name has been changed to "javax.servlet:servlet-api". This may require changes to dependencies in WCB pom.xml files. However, most (if not all) WCBs "inherit" this setting from XperienCentral and won't require changes. NOTE: From 10.9.0 the 3.0 servlet API is supported, so see below for 10.9.0 related changes to to support this version of the servlet API. - Create pages as a display on page for page sections and the image, download, flash and multimedia and configure these special pages at "Website configuration" -> "Special pages". - Choose a page part that will display page sections that do not yet have a page section label assigned and configure it as such by checking the "Show page sections without label" checkbox at "Design templates" -> "Page parts". Make sure this page part is visible on the page section display on page configured in the previous step. Also see Online Help in XperienCentral. - Rebuild the search index - Update customized wmasolrsearch configuration - Presentation: Update xslStyleSheet.jspf in the "website" folder of your custom presentation WCB to check for "mode=incontext" instead of "mode=preview". This is needed for Read Access to work on the backend. - Tweak presentations to work seamlessly with Inline Editing. For more on this, see section 3 "Preparing presentation WCBs for use with the Inline Editor" below. - From GX WebManager 10.1 XperienCentral, Interactive Forms has become integral part of the platform. As a result, the Interactive Forms bundles are not upgraded automatically, and therefore, all Interactive Forms bundles with the version 2.x.y need to be stopped and uninstalled manually. Optional changes: - It is suggested to disable adds in the incontext mode of XperienCentral. - Remove or update maximum platform version in pom.xml. Note that as of GX WebManager 10 XperienCentral this property is no longer honored as the GX WebManager 10 XperienCentral API will remain backwards compatible with GX WebManager 9. - If a WCB uses dependency manager api directly it should switch to the new dependency manager 3 API - Updating icons for Custom Media Items may be preferred; existing icons may typically not fit that well in the new UI. Deleting them and falling back to the default may be a valid solution in many cases. New sizes are 20x20 and 180x180 with Sprite support. Icons for Elements will probably need to be updated as well. - Make sure empty content items have a non-zero size (in mode=incontext) in order to be able to doubleclick on it in the Inline Editor. The same goes for elements. - The menu has been reordered and target menu settings in WCB component definitions are now ignored. In order to place a menu item in a specific category, use "PanelComponentDefinitionImpl.setMenuCategory()" to set the category to one of the constants defined in PanelComponentDefinition. GX WebManager Versions older than 9.18.0 to XperienCentral 10.x.xWhen upgrading from a version older than GX WebManager 9.18.0, it is strongly advised to upgrade to GX WebManager 9.20.x before performing an upgrade to GX WebManager 10.x XperienCentral. |
...