DX 7.1.1.0 Release Notes

  Written by The Jahia Team
 
Sysadmins
   Estimated reading time:
This document is a wrap up of the production patches delivered between DX V7.1.0.1 and DX V7.1.1.0

Underlying Content Platform

  • Improved module validity check to avoid data corruption, modules containing incorrect definitions won't be allowed to start and will display an error message in the logs and in the module management. As invalid definitions were not always properly detected on previous versions, custom modules that were previously working might not start anymore and must be tested and fixed before migrating.
  • Node type definitions won't be automatically removed anymore, even when deploying a new version of the definition file that does not include them. Node types and associated content can now be removed manually from the definitions browser tools.
  • Fixed issue with password initializer when running Jahia on a single CPU machine.
  • Fixed NPE issue when trying to abort an already completed task.
  • Avoid trying to lock an already locked node.
  • Added logging to better trace locking issues.
  • Allowed dynamic choice list initializer to be configurable with Spring.
  • Fixed issue where custom Content List would not display the Edit Dialog.
  • Fixed 404 issue on a Jahia logo.
  • Added some missing translation in the ACME demo contact form.
  • Fixing issue where clicking on "view usage" of tags in the live workspace lists tags used in the default workspace.
  • Fixed Webflow issue with a custom view.
  • [SECURITY] use XSS filtered parameters for webflow execution. 
  • Vulnerabilities reported by Yury Maryshev from PTSecurity."
  • Fixed FlushCacheEventListener bug in the cluster.
  • Remove jsessionid parameter when performing redirect.
  • Use current site and all dependencies to resolve view, even for template nodes.
  • Check permission to add a new page on site node.
  • Changed the way files are written to JCR when they are sent as attachments.
  • Fix URL rewrite for nodes under modules/ (templates).
  • Fixed issue with password policy enforcement.
  • [SECURITY] Fixed issue with the password being shown in address bar.
  • Allow overriding redirection from a webflow by specifying the redirect manually in the RenderContext object.
  • Fixed issue where exception on parsing CND was not logged anywhere.
  • Add core tag library dependency.
  • Added support for detecting Maven 3.3.x on Windows.
  • Fixed poor validation and error handling when importing users from CSV file.
  • Fix PathNotFoundException for "uuid" when doing remote publication.
  • Fixed issue with navmenuText in sitemap which was clickable and leads to a 404 error.
  • Fixed LDAP nested groups which were broken.
  • Fixed issue where when doing URL rewrite, relative links shouldn't be transformed to absolute when server name is localhost.
  • Skip workflow task when exporting, as workflows are not exported.
  • Fixed navMenu issue when startLevel > 0.
  • Improved startup time.
  • [SECURITY] Prevent XSS exploits through request parameters.
  • Added module classloader also if the module has only DSL file (rules.dsl).
  • Disabled logger for the Jericho HTML parser by default.
  • Fixed LDAP issue and allow to have escaped characters in the DN for groups and users.
  • Fixed NPE when using workflow API.
  • Fixed issue with CMIS provider when moving object.
  • Fixed issue where users list does not take into account the case.
  • Fixed mount point issue with CMIS provider.
  • Properly handle position of the auto-registered custom authentication valves.
  • Fixed issue where members of LDAP group containing special characters in its name cannot be listed.
  • Fixed issue with types of properties when doing remote publication.
  • Added parameter in jahia.properties to choose module auto start behavior.
  • Fixed issues with references in the rich text.
  • Do not fail the startup of all dependent Spring contexts if one fails.

Digital Experience Manager

Edit Mode

  • Fixed issue where deletion confirmation popup would stay on top after switching mode.
  • Fixed link with target="_self" in Edit mode.
  • Escape double quotes in the path for edit mode
  • Fixed link to the administration from edit mode.

Engines/Managers

  • Added a property in jahia.properties to define what is the default option when uploading an already existing file.
  • Fixed scrolling issue in the File Manager with IE.
    # By default rename a file when a file with the same name exists
     jahia.fileUpload.already.exist.option = rename 
    # By default add a new version when a file with the same name exists
     jahia.fileUpload.already.exist.option = version

Server and site settings

  • Fixed issue preventing to save user when option "Users are not allowed to change password" was enabled.
  • Modules management: errors during module deployment are now displayed in the Modules management panel. If a module is not properly installed, a "Reinstall" button allows retrying installation without having to re-upload the jar.

Newsletter

  • Fixed personalized newsletter sending issue.
  • Fixed pagination issue in newsletter management.

Search and Replace Module:

  • Fixed boost setting issue for search indexing.
  • Use j:keywords field for a search query.

Module deployment

  • Starting with Digital Experience Manager 7.1.1, errors during module deployment are displayed in the Modules management panel. If a module is not properly installed, a "Reinstall" button allows an installation retry without having to re-upload the jar.
  • Starting with Digital Experience Manager 7.1.1 and in cluster environments, modules do not need to be deployed on processing server as last node anymore and can be deployed on every cluster node in any order but, in case definitions are not backward compatible with the previous module version, the module must be installed and started on all cluster nodes simultaneously.
  • Starting with Digital Experience Manager 7.1.1,  due to improvement on module validity checks,  modules containing incorrect definitions will not be allowed to start and will display error message in the logs and in the module management even if related modules seemed to work properly before. This has been done to avoid potential data corruption. As invalid definitions were not always properly detected on previous versions, custom modules that were previously working might not startup anymore and must be tested and fixed before migration.