Fixed issues in Service Pack 20
Sites
Admin User Interface
- The
Workflow Title
field is marked with*
as required, but there is no validation. (SITES-16491)
Content Fragments
- Nested configuration folders were no longer supported and Content Fragment model folders were no longer visible after upgrading to AEM 6.5.18 or to AEM 6.5.19. (SITES-18110)
- Some subfolders are not able to pick from inherited Content Fragment models. It must support folders without having a
jcr:content
property, even if the DAM folders created by way of the user interface have such a node. (SITES-17943)
Content Fragments - GraphQL API
- When executing a GraphQL query to filter results using optional variables, if a specific value is not provided for the optional variable, then the variable is ignored in the filter evaluation. (SITES-17051)
Content Fragments - REST API
- With the upgrade of the
org.json
library, there was a change in how decimal numbers were deserialized. Before they were converted “by default” into Doubles and now into BigDecimals. Instead, the metadata property values, stored by way of the REST API, should get converted to Double from BigDecimal. (SITES-16857)
Core Backend
- When Quick Publish of a Content Fragment is used, it continues loading and does not get published. That is, Quick Publish is not working for Content Fragments after a service pack upgrade from AEM 6.5.7 to AEM 6.5.17. When the user tried managed publish, it worked. However, when they tried Quick Publish, it was not getting published. Specifically,
com.day.cq.wcm.core.impl.reference.ActivationReferenceSearchBuilder
caused the system to thrash. (SITES-17311) - Content fragments are not serializable with Jackson exporter: The page load breaks when there is a Content Fragment referred to in a page (uses Jackson exporter code) and any tag added to a Content Fragment. (SITES-18096)
Core Components
- Installing CIF Core Components package on AEM causes
:type
value of existing components to change. The change means that they no longer render on pages that they have been added to. (SITES-17601)
Campaign integration
- AEM was using an allowlist–also known as a
whitelist
–due to a vulnerability report. The allowlist was preventing customers from using needed functionality. (SITES-16822)
Experience Fragments
- MSM for Experience Fragments now supports bulk-rollout to Experience Fragment content structures including folders and subfolders. (SITES-16004)
MSM - Live Copies
- An “
Is not modifiable
” exception is thrown when rolling out component. Specifically, anorg.apache.sling.servlets.post.impl.operations.ModifyOperation
exception is experienced during response processing. (SITES-18809) - Unable to roll out changes to specific Live Copies of Experience Fragments. (SITES-17930)
- When a user adds an annotation to a component on a blueprint page, and then rolls it out, the annotation count on Live Copy is displayed incorrectly. (SITES-17099)
- The MSM Rollout button from parent page to child page is broken in the touch graphical user interface; when selected the following error is displayed:
Uncaught TypeError: _g.shared is undefined
. (SITES-16991)
Page Editor
- Forms Theme Editor preview is broken. When Preview is selected, only a loading icon is visible. (SITES-17164)
Assets
- Unable to validate rule-based fields in metadata editor helper and displays an error message “Missing required fields”. (ASSETS-31396)
- After a PDF is moved to another location, the View Page option disappears. (ASSETS-30538)
- Unable to select an image with read permissions. (ASSETS-32199)
- Unable to change card size in view settings. (ASSETS-31667)
- Upload fails while uploading .oft file type. (ASSETS-30109)
- When you try to add a custom metadata field as an additional column to the report, the checkboxes are not selected. (ASSETS-31671)
- Asset move operation does not work appropriately in Experience Manager Service Pack 16. (ASSETS-30598)
Dynamic Media
-
Effective May 1, 2024, Adobe Dynamic Media is ending 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
See also Dynamic Media Limitations.
-
-
When an asset is uploaded to AEM, the
Update_asset
workflow is triggered. However, the workflow never finishes. The workflow only completes up to the product upload step. The next step is the Scene7 batch upload, but that process is not getting pulled into AEM. (ASSETS-30443) -
Need a better way to handle non-Dynamic Media videos gracefully in the Dynamic Media component. This issue was giving an exception instantiating
dynamicmedia_sly.js
. (ASSETS-31301) -
Preview works for all assets, adaptive video sets, and videos. However, it throws a 403 error for
.m3u8
files (which, incidentally, still work by way of public links). (ASSETS-31882) -
The
scene7SmartCropProcessingStatus
status corrected. Smart Crop video metadata used to show failure even when it was successful. (ASSETS-31255)