Versions Compared

Old Version 409

changes.mady.by.user Matthew Wagner

Saved on

compared with

New Version 410

changes.mady.by.user Matthew Wagner

Saved on

Key

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

...

Expand
titleXperienCentral R39

XperienCentral R39

Release date: April 3, 2023


Note

Minimum Version Required for Upgrading to XperienCentral R39

Upgrading to XperienCentral R39 requires a minimum version of R26. If you are upgrading from XperienCentral R25 or lower, you must first upgrade to R26 and then upgrade to XperienCentral R39.


HTML
<br />

Check Configuration Files

See Check Configuration Files.

Filename Changes

The following files have been modified in this version of XperienCentral. If you have custom code that references the following files by name, you must modify your code to pick up these changes.

<xperiencentral-root>/webmanager-wcbs/webmanager-interactive-forms/wmpformpresentation/src/main/resources/presentationtype/static/wmpformpresentation/js/plugin/:

  • jquery-ui-1.13.1.min.css is now jquery-ui-1.13.2.min.css
  • jquery-ui-1.12.1.min.js is now jquery-ui-1.13.2.min.js
  • jquery-form-4.2.0.js is now jquery.form-4.3.0.min.js

<xperiencentral-root>/webmanager/webmanager-webapps/webmanager-backend-webapp/src/main/webapp/js/library/jquery/:

  • jquery.form.js is now jquery.form-4.3.0.patched.js
  • jquery-3.5.1.min.js is now jquery-3.6.1.min.js
  • jquery-ui-1.13.1.min.js is now jquery-ui-1.13.2.min.js

Angular and CSS Styling

  • Beginning in XperienCentral R39.0, GX Software recommends that you prevent Angular panels from rendering inline CSS styling. You should configure your Content Security Policy to block this. In Angular version 12, the so called "critical CSS" is rendered inline by default. This can be changed easily by setting the inlineCritical option in your build to false. For more information see [https://0xdbe.github.io/AngularSecurity-DisableInlineCriticalCSS/].
  • Starting in XperienCentral R39, the minimum password length has been increased to 12. After upgrading, GX Software recommends that you instruct your backend users to create a new password.
  • GXWM-39177 Remove inline styling from the Angular panels

Password Requirements

The password strength requirements have been modified in XperienCentral R39. A password must now contain 12 or more characters. While existing passwords will still work after upgrading to R39, GX Software recommends that you encourage your users to change their password after upgrading.

Remove the XML Parser Plugin

After upgrading to XperienCentral R39, you should manually remove the "GX WebManager - XML Parser" plugin to avoid errors in the log. See Plugins Management Console.


HTML
<br /><br /><br /><br /><br /><br /><br /><br />



Expand
titleXperienCentral R38

XperienCentral R38

Release date: October 28, 2022


Note

Minimum Version Required for Upgrading to XperienCentral R38

Upgrading to XperienCentral R38 requires a minimum version of R26. If you are upgrading from XperienCentral R25 or lower, you must first upgrade to R26 and then upgrade to XperienCentral R38.


HTML
<br />

Check Configuration Files

See Check Configuration Files.

Interactive Forms File Name Changes

  • The file static/wmpformpresentation/js/jquery.form.js was renamed to static/wmpformpresentation/js/plugin/jquery-form-4.2.0.js.
  • The file static/wmpformpresentation/css/plugin/jquery-ui.min.css was renamed to static/wmpformpresentation/css/plugin/jquery-ui-1.13.1.min.css.

If you have custom code that uses these files, you need to modify your code to pick up these name changes. These name changes are only relevant for projects that do not use the default formsHeadTag.jsp.

Shared languages

In XperienCentral version R38, language labels are no longer implicitly shared between channels. When you want to keep sharing the labels of a specific language between 2 channels, perform the following steps before upgrading to R38:

  1. Open the JCR Browser and navigate in the "JCR Tree" tab to the /wm:webmanager/wm:websites/wo:webinitiatif[{_}n{_}]/wo:wm_registry node where wo:webinitiatif[{_}n{_}] represents the channel that will receive the shared language labels.

  2. Click [Edit] by the wo:language property and remove the language you want to share. In order to find out which of the shown UUIDs represents that language, execute the following query in the JCR Browser:

    Code Block
    themeEclipse
    //element(*)[@jcr:uuid='<the uuid of a language>']


  3. Share the language between the 2 channels by following the steps on https://wiki.gxsoftware.com/wiki/display/PD/Multiple+Channels#MultipleChannels-sharing_contentSharingContent.

Upgrading to R38 has no impact when a language was already shared in the way described above.

HTML
<br /><br /><br /><br /><br /><br /><br /><br />


...