Release Notes for Adobe Experience Manager 6.5 | Adobe Experience Manager (2024)

DocumentationAEM 6.5User Guide

• Topics:
• Release Information

CREATED FOR:

• User
• Admin
• Developer

6.5.21.0

Thursday, June 06, 2024

Software Distribution

• A new and easier to use credential for server-to-server authentication, replacing the existing Service Account (JWT) credential. (NPR-41994)

• The IPTC tab now supports Alt Text and Extended Description text fields. (ASSETS-34918)

• If the processing status of an asset is Failed or Metadata Failed, the captions and audio tracks UI does not work appropriately. (ASSETS-37281)
• When you save an asset metadata and try to edit it, the language name does not display. (ASSETS-37281)

• The Saved Searches label is not persistent. The placeholder is being used as the only visual label for a text field. (SITES-3050)

• When you click Sites > Core Core Components > Properties > Permissions tab > Effective Permission, the Effective Permissions dialog box does not open in. (SITES-17378)

• Fixed the double inclusion of the form elements. (SITES-21109)
• When creating a Content Fragment, the Close button sometimes becomes unresponsive, causing the entire page to freeze and necessitating a page refresh to close the Content Fragment. As for the version creation issue, the system is creating a new version of a Content Fragment. This issue occurs even when the user has not made any changes, simply by interacting with the RTE or a text field. (SITES-21187)

• While upgrading Adobe Experience Manager from 6.5.19.0 to 6.5.20.0, the path /libs/cq/graphql/sites/graphiql was getting deleted. (SITES-20098)

• Rollout of Experience Fragments from masters/language to country/language does not update cross-references. (SITES-21172)
• Templates not only specified in the cq:allowedTemplates, but templates that have allowedPaths configured at the template level, appear as options when creating a new Experience Fragment. (SITES-20855)

• Overlaying the Page component to add tabs in page properties. One of them is page configuration and has a property to add an Experience Fragment URL. The link configured in the page properties for the Experience Fragment does not change for any language copies created for that page. The configured link should change with the language copy URL. (SITES-19580)

• The edit mode applies a gray background inconsistently, which fails to comply with the WCAG (Web Content Accessibility Guidelines) color contrast standards. (SITES-20060)

• If an asset is published to Brand Portal, the publishing status remains inconsistent. (ASSETS-36807)
• Assets are not deleted when you delete them from an instance using an API call. (ASSETS-35131)
• When you try to import metadata, a question mark (?) replaces the insertion of characters in any language other than English. (ASSETS-35091)
• When dc:title property is used with data type string, the assets content tree is not working appropriately after the installation of Service Pack 6.5.19. (ASSETS-34684)
• An error is shown if there is any special character in the name of an asset. (ASSETS-33248)

• In AEM 6.5.18, it does not show all the hotspots added to an asset when you edit the hotspots. However, all the hotspots work in a published asset, but you cannot edit them later if you needed to. (ASSETS-33609)

• The latest EPS files that get uploaded are not generating thumbnails after reprocessing. (ASSETS-32617)

• In Tools > Assets > Dynamic Media Publish Setup > Request Attributes tab, the inputs Width(px) and Height(px) look different in Spanish, Italian, and Portuguese. They are not aligned with each other for these locations. (ASSETS-31896)

• Effective May 1, 2024, Adobe Dynamic Media ended support for the following:

  • SSL (Secure Socket Layer) 2.0

  • SSL 3.0

  • TLS (Transport Layer Security) 1.0 and 1.1

  • The following weak ciphers in TLS 1.2:

    • TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384
    • TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
    • TLS_RSA_WITH_AES_256_GCM_SHA384
    • TLS_RSA_WITH_AES_256_CBC_SHA256
    • TLS_RSA_WITH_AES_256_CBC_SHA
    • TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256
    • TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
    • TLS_RSA_WITH_AES_128_GCM_SHA256
    • TLS_RSA_WITH_AES_128_CBC_SHA256
    • TLS_RSA_WITH_AES_128_CBC_SHA
    • TLS_RSA_WITH_CAMELLIA_256_CBC_SHA
    • TLS_RSA_WITH_CAMELLIA_128_CBC_SHA
    • TLS_ECDHE_RSA_WITH_3DES_EDE_CBC_SHA
    • TLS_RSA_WITH_SDES_EDE_CBC_SHA

• Upgrade issue with AEM 6.5 Service Pack 19 (SP19) in which the Application server context-root path is missing for unauthorized requests to Apache Felix following the installation of SP19. Update to Apache Felix Web Management Console 4.9.8. (NPR-41933)

• AEM 6.5 Service Pack 15 is producing continuous error logs with significant entries. The following issues were reported:

  • 404 INFO error for missing resource at path /libs/granite/ui/content/shell/start.html
  • Error log entry for an uncaught SlingException due to NullPointerException at CampaignsDataSourceServlet.java:147

  Error logs should not be filled with frequent and voluminous error entries, and the AEM instance should function without issues related to missing resources or exceptions. (CQ-4357064)

• Remove Google Guava from AEM Cloud Services. (CQ-4356436)

• You cannot select Delete or Modify without Browse permission in the Configuration browser. (GRANITE-51002)

• Regarding cq-target-integration, need to remove non-test usage of Google Guava. (CQ-4357101)
• Replacement of Service Account (JSON Web Token or JWT) credentials with OAuth2 Server-to-Server credentials (also known as Service Principals). (NPR-41994)
• Create Audience request fails with IMS (Identity Management System) configuration. (NPR-41888)
• When a customer attempts to view the Payload page, the content does not display properly due to a malformed URL; a 404 error is displayed. A missing question mark symbol in the URL, before the query parameters, caused the error. This issue requires the customer to insert the question mark symbol to view the Payload page correctly. (NPR-41957)
• Remove code and dependency of Adobe Search&Promote from AEM 6.5, which reached end of life on September 2022 as per notice. (NPR-41855)

• In the Templates editor, the text string No video available. is not localized. (SITES-13190)
• String after activating or deactivating a user are not localized in Tools > Security > Users > any_user_name > Activate > OK, and select any_user_name > Deactivate > OK. (NPR-41737)

• The Unclosed resource resolver error is being experienced for com.day.cq.mailer.impl.DefaultMailService. The MessageGatewayService class, which is out-of-the-box, was being used without a resource resolver. The issue occurred on any page with a form submission button that sends an email using this class. (NPR-41853)
• In the About Adobe Experience Manager dialog box, the copyright year is still 2023. (CQ-4356349)

• An issue with AEM 6.5.19 out-of-the-box translation status not updating as expected for a launch. After importing a translated file into a translation job associated with an AEM launch, the status was expected to change to Approved. Instead, the status changed to Ready for Review, which is not the expected behavior. (NPR-41756)
• When creating multiple configurations and going to the Translation Cloud Services configurations, not all elements are displayed in the UI. Only the first 40 elements/folder are displayed; lazy loading is triggered but not adding more content. (NPR-41829)
• Garbled characters occur if there is Japanese on the Permissions page in the Touch user interface. (NPR-41794)
• AEM 6.5.14 and 6.5.9 do not send an emoji for translation. (CQ-4357000)

• In Tools > Security > Users > <user_name> > Profiles, in the Edit User Settings dialog box, clicking Cancel does not exit the dialog box. (NPR-41793)
• The Granite pathfield component at /libs/granite/ui/components/coral/foundation/form/pathfield fails to enable the Select button when an asset is selected. After the path field is popped up, and the user selects the asset checkbox, the Select button is not enabled; it does not change from gray to blue. (NPR-41970)
• An issue exists with the Content Fragment Model (CFM) reference field within AEM. Despite the CFM reference field being set as mandatory, the system allows users to click Save to save content with non-CFM values in certain scenarios. The Save button should be dimmed (unavailable). (NPR-41894)
• The standard Coral user interface dialog boxes that use the successresponse action must trigger a Success Response after the action. But in AEM 6.5 Service Pack 19, the reload action is not invoked and no message is displayed. (NPR-41797)
• AEM Notifications links are not working in AEM 6.5 Service Pack 18. When upgrading to Service Pack 18, the AEM Notifications links are not working when selecting the messages by way of the notifications button. (NPR-41792)

• In AEM 6.5.18, repeated errors in removing from user metadata cache during purge. (NPR-41762)

• Experience Manager 6.5.21.0 requires Experience Manager 6.5. See upgrade documentation for detailed instructions.
• The Service Pack download is available on Adobe Software Distribution.
• On a deployment with MongoDB and multiple instances, install Experience Manager 6.5.21.0 on one of the Author instances using the Package Manager.

Adobe does not recommend that you remove or uninstall the Experience Manager 6.5.21.0 package. As such, before you install the pack, you should create a backup of the crx-repository in case you must roll it back.

1. Restart the instance before installation if the instance is in update mode (when the instance was updated from an earlier version). Adobe recommends a restart if the current uptime for an instance is high.

2. Before installing, take a snapshot or a fresh backup of your Experience Manager instance.

3. Download the Service Sack from Software Distribution.

4. Open Package Manager, then select Upload Package to upload the package. To know more, see Package Manager.

5. Select the package, then select Install.

6. To update the S3 connector, stop the instance after installation of the Service Pack, replace the existing connector with a new binary file provided in the install folder, and restart the instance. See Amazon S3 Data Store.

• Place the package into ../crx-quickstart/install folder when the server is available online. The package is automatically installed.
• Use the HTTP API from Package Manager. Use cmd=install&recursive=true so that the nested packages are installed.

Experience Manager 6.5.21.0 does not support Bootstrap installation.

1. The product information page (/system/console/productinfo) displays the updated version string Adobe Experience Manager (6.5.21.0) under Installed Products.

2. All OSGi bundles are either ACTIVE or FRAGMENT in the OSGi Console (Use Web Console: /system/console/bundles).

3. The OSGi bundle org.apache.jackrabbit.oak-core is version 1.22.20 or later (Use Web Console: /system/console/bundles).

 <dependency> <groupId>com.adobe.aem</groupId> <artifactId>uber-jar</artifactId> <version>6.5.21</version> <scope>provided</scope> </dependency>

• Related to Oak
  From Service Pack 13 and above, the following error log has begun to appear which affects the persistence cache:

  code language-shell

  org.h2.mvstore.MVStoreException: The write format 1 is smaller than the supported format 2 [2.0.202/5]at org.h2.mvstore.DataUtils.newMVStoreException(DataUtils.java:1004) at org.h2.mvstore.MVStore.getUnsupportedWriteFormatException(MVStore.java:1059) at org.h2.mvstore.MVStore.readStoreHeader(MVStore.java:878) at org.h2.mvstore.MVStore.<init>(MVStore.java:455) at org.h2.mvstore.MVStore$Builder.open(MVStore.java:4052) at org.h2.mvstore.db.Store.<init>(Store.java:129)

  Or

  code language-shell
  org.h2.mvstore.MVStoreException: The write format 1 is smaller than the supported format 2 [2.1.214/5].

  To resolve this exception, do the following:

  1. Delete the following two folders from crx-quickstart/repository/

     • cache
     • diff-cache

  2. Install the Service Pack, or restart Experience Manager as a Cloud Service.
     New folders of cache and diff-cache are automatically created and you no longer experience an exception related to mvstore in the error.log.

• Update your GraphQL queries that may have used a custom API name for your content model to use the default name of the content model instead.

• A GraphQL query may use the damAssetLucene index instead of the fragments index. This action might result in GraphQL queries that fail, or take a long time to run.

  To correct the problem, damAssetLucene has to be configured to include the following two properties under /indexRules/dam:Asset/properties:

  • contentFragment

    • jcr:primaryType="nt:unstructured"
    • name="jcr:content/contentFragment"
    • propertyIndex="{Boolean}true"
    • type="Boolean"

  • model

    • jcr:primaryType="nt:unstructured"
    • name="jcr:content/data/cq:model"
    • ordered="{Boolean}true"
    • propertyIndex="{Boolean}true"
    • type="String"

  After the index definition is changed, a reindexing is required (reindex = true).

  After these steps, the GraphQL queries should perform faster.

• When trying to move, delete, or publish either Content Fragments, Sites, or Pages, there is an issue when Content Fragment references are fetched. The background query fails. That is, the functionality does not work.
  To ensure correct operation, you must add the following properties to the index definition node /oak:index/damAssetLucene (no reindexing is required):

  code language-xml
  "tags": [ "visualSimilaritySearch" ]"refresh": true

• If you upgrade your Experience Manager instance from 6.5.0 - 6.5.4 to the latest Service Pack on Java™ 11, you see RRD4JReporter exceptions in the error.log file. To stop the exceptions, restart your instance of Experience Manager.

• Users can rename a folder in a hierarchy in Assets and publish a nested folder to Brand Portal. However, the title of the folder is not updated in Brand Portal until the root folder is republished.

• The following errors and warning messages may be displayed during installation of Experience Manager 6.5.x.x:

  • "When the Adobe Target integration is configured in Experience Manager using the Target Standard API (IMS authentication), then exporting Experience Fragments to Target results in wrong offer types getting created. Instead of type “Experience Fragment”/source “Adobe Experience Manager,” Target creates several offers with type “HTML”/source “Adobe Target Classic.”
  • com.adobe.granite.maintenance.impl.TaskScheduler: No maintenance windows found at granite/operations/maintenance.
  • Adaptive Form server-side validation fails when aggregate functions such as SUM, MAX, and MIN are used (CQ-4274424).
  • com.adobe.granite.maintenance.impl.TaskScheduler : No maintenance windows found at granite/operations/maintenance.
  • The hotspot in a Dynamic Media interactive image is not visible when previewing the asset through the Shoppable Banner viewer.
  • com.adobe.cq.social.cq-social-jcr-provider bundle com.adobe.cq.social.cq-social-jcr-provider:1.3.5 (395)[com.adobe.cq.social.provider.jcr.impl.SpiSocialJcrResourceProviderImpl(2302)] : Timeout waiting for register change to complete unregistered.

• Starting with AEM 6.5.15, the Rhino JavaScript Engine provided by the org.apache.servicemix.bundles.rhino bundle has a new hoisting behavior. Scripts that use the strict mode (use strict;) have to declare their correct variables. Otherwise, they do not get run, and end up throwing a runtime error.

• Installing tagging related out-of-the-box content by way of an official update package resets the languages property of the /content/cq:tags node to default. This action is true for Service Packs, Security Service Packs, Extended Feature Packs, Cumulative Feature Packs, patches, and so on. Therefore, it is necessary to add it from the properties before installation.

• SITES-17934 - Content Fragments - Preview fails due to DoS protection for large tree of fragments. See the KB article about Default GraphQL Query Executor configuration options

• In an Adaptive Form based on an XDP with embedded scripts on checkboxes, the scripts are not executed for elements after such checkboxes. (FORMS-14244)
• Users are unable to create a Correspondence Management letter. When a user creates a letter, an error with description “Object Object” appears and the letter is not created. Thumbnails for layouts also fail to load on the letter creation screen. You can install the latest AEM 6.5 Form Service Pack 20 (6.5.20.0) to resolve the issue. (FORMS-13496)
• The Interactive Communications service creates the PDF document, but the user’s data is not automatically populated in the form fields. The prefill service is not working as expected. You can install the latest AEM 6.5 Form Service Pack 20 (6.5.20.0) to resolve the issue. (FORMS-13413, FORMS-13493)
• The Review and Correct (RnC) editor of an automated forms conversion service fails to load. You can install the latest AEM 6.5 Form Service Pack 20 (6.5.20.0) to resolve the issue. (FORMS-13491)
• After updating from AEM 6.5 Forms Service Pack 18 (6.5.18.0) or AEM 6.5 Forms Service Pack 19 (6.5.19.0) to AEM 6.5 Forms Service Pack 20 (6.5.20.0), users encounter a JSP compilation error. They cannot open or create adaptive forms and they’re running into errors with other AEM interfaces like the page editor, AEM Forms UI, and AEM Workflow editor. You can install the latest AEM 6.5 Form Service Pack 20 (6.5.20.0) to resolve the issue. (FORMS-13492)
• Rows in the date picker widget are truncated when traversing through months in the pop-up widget for fields with Edit/Display pattern. (FORMS-13620)
• Form submissions are failing when trying to use the DOR (Document of Record) service in the backend. The error message encountered is: “Submit Action couldn’t complete because Form Resource isn’t correctly assigned.” (FORMS-13798)
• When an Adaptive Form is submitted from an Adobe Experience Manager Publish instance to an Adobe Experience Manager Workflow, the workflow fails to save the attachments. (FORMS-14209)
• On installing AEM 6.5 Forms Service Pack 20 package (AEM Forms add-on package for SP20), the AEM Sites user interface (UI) exhibits significant performance degradation. (FORMS-13791)
• The prefill service fails with a null pointer exception in Interactive Communications. (CQDOC-21355)
• Adaptive Forms let you use custom functions with ECMAScript version 5 or earlier. When a custom function uses ECMAScript version 6 or later, like let, const, or arrow functions, the rule editor might not open properly.

• List of OSGi bundles included in Experience Manager 6.5.21.0
• List of Content Packages included in Experience Manager 6.5.21.0

• Product download at licensing.adobe.com
• Contact Adobe Customer Support.

• Experience Manager product page
• Experience Manager 6.5 documentation
• Subscribe to Adobe Priority product updates