Adobe Experience Manager 6.1 hotfixes

IMPORTANT NOTE

This page is the old version of the recommended hotfixes page, before the release of AEM 6.1 Service Pack 2. Please refer to this page for the Hotfixes that should be installed on top of SP1. Hotfixes below are already included in Service Pack 2 (except Forms and Communities), thus only applicable to AEM 6.1 + Service Pack 1 setup.

The Adobe Experience Manager 6.1 Service Pack 2 is now available on the Adobe Package Share and the release notes under https://docs.adobe.com/docs/en/aem/6-1/release-notes-sp2.html

The installation of SP2 is highly recommended as it includes security, performance, stability, and key customer fixes and enhancements released since the general availability of Adobe Experience Manager 6.1.  

SERVICE PACK 1

The Adobe Experience Manager 6.1 Service Pack 1 is available on the Adobe Package Share and the release notes under https://docs.adobe.com/docs/en/aem/6-1/release-notes-sp1.html

The installation of the latest Service Pack is highly recommended as it includes security, performance, stability, and key customer fixes and enhancements released since the general availability of Adobe Experience Manager 6.1.  

The hotfixes below should be installed on top of Service Pack 1. The ones with Bold are highly recommended. You can find the old content, which is all recommended hot fixes before the release of Service Pack 1 here.

Pastaba:

AEM hotfixes do not benefit from the same level of quality assurance as service packs or product releases, therefore must be always validated first on a staging environment as part of your quality deployment processes.

 

CORE HOTFIXES ACROSS AEM PRODUCTS (AEM PLATFORM)

Security vulnerabilities

For the protection of our customers, Adobe does not disclose any vulnerability details. 

Date

Name

Description

Fixed Issues

Replaces

Feb 4th, 2016

XSS vulnerability

CQ-70200 : Extra underscore added for anchor links

 

Feb 23rd, 2016

Extend content disposition filter protection to author

GRANITE-9550 : Extend content disposition filter protection to author

 

Oak

The current recommended Oak version is 1.2.28

Date

Name

Fixes

February 8th, 2018

Indexing

Date

Name

Fixed Issues

Replaces

August 1st, 2016

PDF indexing hangs

Hotfix 11074

Workflow

Date

Name

Description

Fixed Issues

Replaces

Feb 19th, 2016

XSS vulnerabilityHotfix for Links in email notifications are not url encoded

CQ-73491 : Links in email notifications are not url encoded

 

Dispatcher

Adobe recommends that you use the latest Dispatcher version. You could find the latest dispatcher here 

https://www.adobeaemcloud.com/content/companies/public/adobe/dispatcher/dispatcher.html 

Miscellaneous

Date

Name

Description

Fixed Issues

Replaces

Jan 27 2016

Package installation fails on AEM 6.1 with FileDataStore

GRANITE-10947 : Package installation fails on AEM 6.1 with FileDataStore

 

Jan 28 2016

Clustering:Non-primary server restart triggered the re-indexing on Primary server

SLING-5030 : replace isolated mode with (larger) TOPOLOGY_CHANGING phase

 

Feb 18th, 2016

JCR Installer paused by package install and never unpaused

GRANITE-10726: JCR Installer paused by package install and never unpaused

 

Jan 26th, 2016

Backport GRANITE-10700/CQ-65390 to AEM 6.1 - javax.inject conflicts

GRANITE-10700 : Upgrade org.apache.sling.scripting.java to the latest version

CQ-65390 : Update Sling Models to API 1.2.2

 

Jan 6th, 2016

GRANITE-8510 [i18n] xliff import/export is broken after switch to json dictionaries

GRANITE-8510 : [i18n] xliff import/export is broken after switch to json dictionaries

 

Pastaba:

 

  • You can access the Package Share with a registered user as mentioned here
  • Request the non public hotfixes via an AEM Support ticket.
  • Most hotfixes are stand-alone unless specified and can be installed in any order. It can be self-verified by looking at "Details" tab Dependencies element in package share.  
  • At the moment, the release notes of the public hotfixes are only available per request via the AEM Support Portal.
Pastaba:

 

  • If you have custom AEM projects template make sure after installing the Hotfix/Service pack (  that contains project fix) to validate the value of cq:allowedTemplates.
    • To do that Navigate to /content/projects/jcr:content. Edit the value of property cq:allowedTemplates by adding/verfying your respective template.

PRODUCT SPECIFIC HOTFIXES

 Adobe

Gaukite pagalbą greičiau ir lengviau

Naujas vartotojas?