Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Anchor
top
top


This topic describes the extra steps you need to take when provides extra information about upgrading your XperienCentral installation to a specific version. The modifications per version are cumulative which means that you need to apply the changes for all versions above the one you are upgrading from. For example, if you upgrade from XperienCentral 10.14.0 to 10.21.1, you need to apply the changes described for all versions from 10.14.1 up to and including 10.21.1. For general upgrade information, see Upgrading a Linux Installation or Upgrading a Windows Installation.

...

  • Users can now be granted rights to access XperienCentral in specific ways. Whereas a user could always use password-based login and/or container-based (if enabled), each login method now has to be enabled for each user. By default, all users will be allowed all relevant access methods. We advise you to review the list of ways that each user may log in after the upgrade and adjust them accordingly.
  • String interpolation in Interactive Forms has changed slightly. In previous versions of XperienCentral, a JavaScript syntax error would cause the original string value to be returned.  This error is now logged and other expressions (if any) will be evaluated. This may result in partially interpolated strings being returned instead of the input string.
  • When upgrading to XperienCentral 10.12.1 or newer, the index directories contentindex and searchengine are removed automatically. However, in a clustered environment, this is only done on the master node. To upgrade successfully, the aforementioned index directories should be removed manually from all the slave nodes.
  • JBoss/Wildfly application server users should deactivate the "as-default" profile and activate the Maven "as-jboss" profile by uncommenting the profiles in the profiles section in the settings.xml or by passing the profiles as Maven profile using the Maven command line -P <profiles> option.


...

XperienCentral 10.12.0

...

  • SOLR has been upgraded to version 5.5.1, therefore it is necessary to fully rebuild the backend

...

  • and frontend search indices. The former is built automatically after the

...

  • upgrade. Please note

...

  • that this may take some time to complete and could cause high server load. The frontend search

...

  • index rebuild should be triggered manually via the Setup Tool.

...

  • The files conf/core0/conf/schema.xml and conf/core0/conf/solrconfig.xml have been updated.

...

  • If you have made custom changes

...

  • to one or both of these files, it is necessary to merge the new files

...

  • with the custom ones. If no custom changes have been made, the new versions of the files can simply

...

  • be used instead of the old ones.

...

  • The secure form signer used to protect forms against tampering has been changed. All dumped

...

  • pages which contain interactive forms or advanced forms will need to be regenerated or

...

  • flushed from the cache. Any old pre-upgrade forms submitted by browsers to the website after

...

  • the upgrade will be rejected by the secure forms checking filter.

...

  • Form sessions can now be completed if a different form version becomes active. If the default

...

  • showFormElementSsi.jspf, formFragmentOverview.jspf and form.tag are overruled in a custom

...

  • presentation, please synchronize these files.


...

XperienCentral 10.11.0

...

  • An extra input field has been added to the IAF csfw fields. If a custom form.tag is used in the

...

  • presentation, please add the following hidden input:

 

...


  • <input type="hidden" name="csfw_requestedChannel" value="${wmfn:escapeToHtml(presentationcontext.channel)}"/>

...


  • The E-Cards, Poll and Who-is-Who functionalities have been removed and all their persisted content will

...

  • be automatically removed during the upgrade process.

 

...

  • The system presentation

...

  • JSP elementAnchor.jspf

...

  • with scope

...

  • ElementAnchor

...

  • was changed and should be

...

  • copied to/synchronized with the project specific presentation.

 

...

  • In Interactive Forms

...

  • , an error on the form scope previously did not stop execution of any components in a

...

  • conditional block. If your project depends on this

...

  • behavior, you will have to change the relevant

...

  • conditions in Interactive Forms.

...

  • One line of text used by the Search element is garbled when shown on a Dutch page. To correct this by

...

  • hand, log into

...

  • XperienCentral,

...

  • navigate to the Configuration menu at the top of the page, select

...

...

  • Open the

...

  • "wm_language_search" part of the dialog and update the "all_pages" entry to

...

  • "Alle categorieën".


...

XperienCentral 10.10.1

 - Links are now filtered by scheme. Schemes that are not allowed result in removal of the illegal

...