Upgrade 16.6 to 16.7

Overview

This guide describes how to upgrade a Bloomreach Content implementation project from version 16.6.x to 16.7.y.

Significant Changes

Version 16.7 introduces several new features, technical stack upgrades, and product improvements. Key updates for projects moving from 16.6 to 16.7 include:

  • AI Content Assistant Access Management: You can now control access to the AI Content Assistant using role-based management. Restrict access to specific users or groups, or enable gradual rollouts. For configuration details, see Initialize and configure the AI Content Assistant.
  • PDF Support in AI Content Assistant: The AI Content Assistant now supports using PDF documents stored in the CMS as primary context or reference material, such as brand guidelines, during AI conversations.
  • Angular v21 Upgrade: The Channel Manager, Project Management, and Navigation applications have been upgraded from Angular v12 to v21. This update improves performance, security, and long-term support.
  • Enhanced SVG Security: A new configurable SVG validator strengthens protection against malicious content in uploaded image files.
  • Refactored CMS File Uploads: The deprecated Blueimp File Upload library has been replaced with FilePond. Several internal Wicket classes have been removed or refactored.
  • Image Compression Improvements: A new parameter, compressionLossless, is available for image set variants. This parameter controls the compression quality factor for lossless formats such as PNG and GIF. For details, see Create a Custom Image Set and the Essentials Gallery Manager.

For a complete list of changes, see the 16.7.0 release notes.

Upgrade Steps

1. Perform Generic Minor Upgrade Steps

Follow the generic instructions for minor upgrades before proceeding with version-specific changes.

2. Review Custom Project Code for Library Incompatibilities

Third-party library upgrades in this release may introduce backward compatibility issues. If your project code fails to build or run after the upgrade, review the affected libraries and update your code as needed to ensure compatibility.

Refactored CMS File Uploads

The Blueimp File Upload frontend library has been replaced with FilePond to remove the dependency on jQuery 1 and address related security issues.

As part of this change, several internal Wicket classes have been removed or significantly refactored:

  • org.hippoecm.frontend.plugins.jquery.upload.multiple.FileUploadBar
  • org.hippoecm.frontend.plugins.jquery.upload.multiple.FileUploadTemplate
  • org.hippoecm.frontend.plugins.jquery.upload.multiple.FileDownloadTemplate
  • org.hippoecm.frontend.plugins.jquery.upload.single.FileUploadBar

If your project includes customizations or overrides that extend or depend on these classes or related packages, review and update those customizations for compatibility with version 16.7.0.

Deprecated APIs

The following APIs, which rely on Jackrabbit RMI connections, are now deprecated and will be removed in Bloomreach Content version 17:

org.hippoecm.repository.RemoteHippoRepository  
org.hippoecm.repository.decorating.client.ClientHierarchyResolver  
org.hippoecm.repository.decorating.client.ClientQuery  
org.hippoecm.repository.decorating.client.ClientRepository  
org.hippoecm.repository.decorating.client.ClientServicesAdapterFactory  
org.hippoecm.repository.decorating.client.ClientServicingNode  
org.hippoecm.repository.decorating.client.ClientServicingSession  
org.hippoecm.repository.decorating.client.ClientServicingWorkspace  
org.hippoecm.repository.decorating.client.ClientServicingXASession  
org.hippoecm.repository.decorating.client.ClientWorkflowDescriptor  
org.hippoecm.repository.decorating.client.ClientWorkflowManager  
org.hippoecm.repository.decorating.client.LocalServicingAdapterFactory  
org.hippoecm.repository.decorating.remote.RemoteHierarchyResolver  
org.hippoecm.repository.decorating.remote.RemoteQuery  
org.hippoecm.repository.decorating.remote.RemoteRepository  
org.hippoecm.repository.decorating.remote.RemoteServicingNode  
org.hippoecm.repository.decorating.remote.RemoteServicingSession  
org.hippoecm.repository.decorating.remote.RemoteServicingWorkspace  
org.hippoecm.repository.decorating.remote.RemoteServicingXASession  
org.hippoecm.repository.decorating.remote.RemoteWorkflowDescriptor
org.hippoecm.repository.decorating.remote.RemoteWorkflowManager  
org.hippoecm.repository.decorating.server.RemoteServicingAdapterFactory
org.hippoecm.repository.decorating.server.ServerHierarchyResolver  
org.hippoecm.repository.decorating.server.ServerQuery  
org.hippoecm.repository.decorating.server.ServerQueryManager  
org.hippoecm.repository.decorating.server.ServerRepository  
org.hippoecm.repository.decorating.server.ServerServicingAdapterFactory  
org.hippoecm.repository.decorating.server.ServerServicingNode  
org.hippoecm.repository.decorating.server.ServerServicingSession  
org.hippoecm.repository.decorating.server.ServerServicingWorkspace  
org.hippoecm.repository.decorating.server.ServerServicingXASession  
org.hippoecm.repository.decorating.server.ServerWorkflowDescriptor  
org.hippoecm.repository.decorating.server.ServerWorkflowManager  
org.hippoecm.hst.core.jcr.pool.BasicPoolingRepositoryFactory  
org.hippoecm.hst.core.jcr.pool.MultiplePoolingRepositoryFactory

Update your project to remove dependencies on these APIs before upgrading to version 17.

Additional Resources

For more detailed information, see the detailed release notes.

Share Feedback
Page: /about/upgrade-guides/minor-version-upgrades/v16/upgrade-16.6-to-16.7
Section: About
Category *