Known Issues

You are reading the AEM 6.1 version of Known Issues.
This documentation is also available for the following versions:  AEM 6.2  AEM 6.0 

This page keeps a list of known issues from Adobe Experience Manager 6.1 that was released in May 2015. The list is split in known issues that are resolved via Service Pack or Hotfixs and issues that are still open.

Solution Available

Customers are recommended to install the latest Service Pack

It resolves following known issues:

  • Content Targeting: Can't edit/change default experience after targeting (CQ-42229)
  • Content Targeting: Can't disable targeting on a component that uses offers from library (CQ-42226)
  • Content Targeting: Can't rename existing experiences (CQ-41902)
  • Content Targeting: Can't get past the diagram step of the edit activity wizard when editing an existing activity in the personalization console (CQ-41901)
  • Adobe Target: The campaign synchronization to Target fail because it cannot create the offers (CQ-42702)
  • Adobe Target: Cannot add static parameters to an mbox call unless the "Accurate targeting" option is checked (CQ-41076)

Known Issues

Please contact support if you need more information about the known issues.

Release Install & Update

  • Update to 6.1 from 5.x and 6.0+CRX2 using crx2oak fails if installation path contains a space. Move quickstart folder into path with no space. (CQ-39859)
  • Update to 6.1 from 5.x and 6.0+CRX2 fails on Windows due to backslashes written to FileDataStore.cfg. Workaround is to modify the 'org.apache.jackrabbit.oak.plugins.blob.datastore.FileDataStore.cfg' file with datastore path before we run Migration command (CQ-42291)
  • Content Targeting: ContextHub is broken (JS error) after upgrading from AEM 6.0 to 6.1. (CQ-41697) Workaround:
    1. go to /crx/packmgr/index.jsp
    2. uninstall com.adobe.contexthub.content
    3. go to /crx/de/index.jsp#/libs/granite/contexthub
    4. remove /libs/granite/contexthub and save
    5. go to /crx/packmgr/index.jsp
    6. reinstall com.adobe.granite.contexthub.content

Platform

  • Apache Sling/Maintenance Dashboard: Failing task scheduler prevents its sequent executions. Contact support. (GRANITE-8776)
  • SAML 2.0 Authentication Handler: The description for 'Use Encryption' is misleading. Correct is: Whether or not this authentication handler expects encrypted SAML assertions. If this is enabled the SP's private key must be provided in the key-store of the 'authentication-service' system user (see SP Private Key Alias above). (GRANITE-8705)
  • Oak: Concurrency issues in RDB MK when cluster nodes are started simultaneously. Workaround is to start back-to-back. (GRANITE-8625)
  • Oak TarMK Cold Standby: standby.autoclean removes too many segments. Recommendation is to restart the standby prior to running cleanup (CQ-40862)
  • Replication: Activating a locked page might fail with error that version could not be created. Unlock the page before activating changes. (CQ-37720)
  • HTL: Missing scripting variables (editContext, resourceResolver) in JS (CQ-40324)
  • CRXDE Lite: Selecting the root node doesn't update the properties in the lower pannel (GRANITE-8180)
  • CRXDE Lite: URL <server>/crxde no longer working (GRANITE-7882)
  • Health Checks: HTML Library Manager Health Check doesn't work. Change the PID to com.adobe.granite.ui.clientlibs.impl.HtmlLibraryManagerImpl (CQ-42656)
  • Touch-optimized UI: on the number Input field - the +/- buttons don't work as expected with Microsoft Internet Explorer 9. Use IE 10+ or fill in number via keyboard. (CQ-36011)

Sites

  • Page Properties: Bulk edit doesn't work in Microsoft Internet Explorer 11. Please use other browser. (CQ-42070)
  • Page Authoring: An error is thrown when trying to edit a component that is included in a component and it not yet present in the jcr:content of the page. Make sure the template adds the resources when the page is created (CQ-36949)
  • Page Authoring: cq:actions are not properly parsed - "copymove" action not working (CQ-40917)
  • Page Authoring: Edit mobile site in 'Adaptive Mobile Editor' is not supported in Touch-optimized UI. Please use the Classic UI (CQ-18198)
  • Page Authoring: Extension point for the header bar in Page Authoring is broken (CQ-41697)
  • Launches: Promote Launch from editor.html does not work if server is running on context path (CQ-42046)
  • MSM: Suspendng or stopping a background rollout will end with exception (CQ-17743)

Integration with Marketing Cloud

  • Adobe Target: Offers replication agents fails if more and one Cloud Service config is assigend to Campaign (CQ-34835)
  • Adobe Analytics: Importing a trended report via Report Importer throws an error (ArrayIndexOutOfBoundsException). Regression from moving to Analytics API 1.4 (CQ-37432)
  • Adobe Audience Manager: Integration doesn't work if 3rd party cookies are blocked in browser (CQ-38238)

Assets

  • Send Assets per Email: Email is not sent out when running on context path (CQ-40273)
  • Catalog Producer: Only property names are shown during mapping of product to template in Catalog Producer (CQ-42651)

Dynamic Media

  • Dynamic Media: After making changes in viewer editor, updates will not appear when previewing assets with that viewer until the browser cache is cleared. (CQ-40267)
  • Mixed Media Set: Embedd Code yields non-functional video (CQ-41360)
  • YouTube: Error when adding tags to a YouTube Cloud Service Configuration (CQ-40695)
  • Video encoding: video encoding workflow keeps on triggering multiple times for same video until the workflow is terminated manually. (CQ-40485)
  • Video: asset with localized name (special characters) can't be used in the Dynamic Media component (CQ-39939)
  • Video: Native HTML5 video does not play with Dynamic Media Component (CQ-40106)
  • Scene7: Polling importer doesn't sync assets back to AEM Assets (CQ-39607)
  • Scene7: Assets uploaded to S7 with localized names (special characters) are not displayed correcty within the S7 UI (CQ-39861)

Forms

  • Text editor In Correspondence Management doesn't support compounding numbering capability (LC-3909949)

Communities

FP7 Known Issues

  • When creating a site for enablement, the choices for the Community Enablement Managers group are presented from the publish environment, instead of the author environment (CQ-4207318).  To workaround this, use the security groups console (select Tools, Operations, Security, Groupsnot  the Communities Groups console) to manage the members of the group.

FP6 Known Issues

  • Not able to use Firefox browser to edit a site.  Options are to use a different browser or contact your account representative for a more recent build of the feature pack. (CQ-108285)
  • Existing community site's moderation dashboard layout is broken after upgrading to FP6.  (CQ-4197955)
    • solution is to ensure coralui3 is added to clientlibs list for the site's Administration page
      example location : /content/sites/<sitename>/en/moderation/jcr:content/shell2/jcr:content/head/clientlibs
      categories :
        [coralui3,
        coralui2,
        granite.ui.foundation,
        granite.ui.foundation.admin,
        cq.common.wcm,
        cq.ui.social.core.communities.filters,
        granite.ui.notifications]

FP5 Known Issues

  • Private messages are not actually private as an entry is generated for activity streams (CQ-96741).  Workaround : To ensure activities are not created, from web console /system/console/components - stop and start the com.adobe.cq.social.messaging.impl.MessagingActivityStreamProviderExtension component.

FP4 Known Issues

  • Search for keyword yields incorrect results when search with tag filter (CQ-85186)

FP3 Known Issues

  • Enablement : Having an apostrophe/Chinese character in user name assigned to a Resource causes the Resource to become unusable until user name is unassigned.  (CQ-64097)
  • Enablement : Workaround for publishing Resource or Learning Path when 'send enrollment email' is checked (CQ-63807) :
    • on publish only, add allow/jcr:read credential for user 'social-enablement-replication-user'
  • Enablement : SCORM resources are not registered if SCORM package installed after Community Site is created (CQ-63404) :
    • manual fix : on publish only, use the Security console to add user communities-scorm-user to group communities-<site name>-<uid>-members
  • Enablement : When a Resource title contains high ASCII or double byte characters, a search for the Resource may only be a substring containing only ASCII (7-bit) characters, else the search will fail.  (CQ-53800)
  • Enablement : Community Site's member group is not selectable for Resource assignment. (CQ-51857)
  • Enablement : SCORM Resource fails to play when served with https (SSL) (CQ-69206)
    • manual edit to httpd.conf on Dispatcher - add these lines :
      {{SetEnvIf X-Forwarded-SSL on HAVE_SSL
         Header edit Location ^http:// https:// env=HAVE_SSL}}
  • Catalog : Anonymous site visitors are unable to view Resources in a Catalog.  (CQ-53036)
  • Blog : The Geometrixx Blog sample is based on the deprecated author-side Blog feature from AEM 6.0 and earlier, and will not work properly until fully migrated to the new publish-side Blog feature of AEM Communities 6.1.
  • Requires installation of AEM 6.1 HotFixes 6640 and 6680 on AEM GA prior to installing Feature Pack 3.
  • SCF : Custom server-side Handlebars Helpers encounter binding/linking errors at runtime (CQ-74751).

FP2 Known Issues

  • Enablement : Having an apostrophe/Chinese character in user name assigned to a Resource causes the Resource to become unusable until user name is unassigned.  (CQ-64097)
  • Enablement : Workaround for publishing Resource or Learning Path when 'send enrollment email' is checked (CQ-63807) :
    • on publish only, add allow/jcr:read credential for user 'social-enablement-replication-user'
  • Enablement : When a Resource title contains high ASCII or double byte characters, a search for the Resource may only be a substring containing only ASCII (7-bit) characters, else the search will fail.  (CQ-53800)
  • Enablement : Assignment report column selection does not persist when the pagination link is selected to show the next page of rows.  (CQ-52534)
  • Enablement : Community Site's member group is not selectable for Resource assignment. (CQ-51857)
  • Catalog : Anonymous site visitors are unable to view Resources in a Catalog.  (CQ-53036)
  • Blog : The Geometrixx Blog sample is based on the deprecated author-side Blog feature from AEM 6.0 and earlier, and will not work properly until fully migrated to the new publish-side Blog feature of AEM Communities 6.1.
  • Requires installation of AEM 6.1 HotFixes 6640 and 6680 on AEM GA prior to installing Feature Pack 2.

FP1 Known Issues

  • Enablement : The time taken to serve Community Site pages to a user increases, as more enrollment notification emails are sent to this user.  (CQ-45023)
  • Enablement : When using Internet Explorer 10 (IE 10) browser, some Resource types will launch in a new window.  Video and PDF Resources will play inside the frame.  (CQ-40257)
  • Enablement : When a Resource title contains high ASCII or double byte characters, a search for the Resource may only be a substring containing only ASCII (7-bit) characters, else the search will fail.  (CQ-53800)
  • Requires installation of AEM 6.1 HotFixes 6640 and 6680 on AEM GA prior to installing Feature Pack 1.
​