--- title: "AEM Release 4.60.0" description: "AEM Release 4.60.0 - News: Find out about our latest Features, Enhancements, and Bug Fixes." path: https://www.eonshowroom.eon.com/en/about-foundation-2020/aem-release-notes/aem-release-4-60-0.html lastModified: 2026-01-19T13:55:32.415Z --- # AEM Release 4.60.0 ![](https://www.eonshowroom.eon.com/cdm-assets/is/image/eon/GettyImages-906577952-1%3A2-1?fmt=webp) ## AEM Release 4.60.0 Release Date: 16.12.2025 [Release Scope](https://confluence.eon.com/spaces/ddsmbfoun/pages/883629029/AEM-Releases+in+2025) [Register to our Release Notes](https://www.eonshowroom.eon.com/en/about-foundation-2020/aem-release-notes/release-notes-newsletter-registration.html) with UI-Kit ## 4.35.0 ## Execution of Migration Script To ensure not breaking your Content Headers or your Text Teasers with Number, please ensure corresponding Migration Scripts get executed ! The linked Page will list the Scripts associated with each specific Release. Always make sure to use only the Migration Scripts that match the Version currently running in your Environment. Using Scripts from a different Version may cause Inconsistencies or Errors. You can execute the Migration Scripts yourself or request Support from[ **Pranith Lingala**](mailto:pranith.k.lingala@accenture.com). Migration Scripts must be executed in parallel with the Foundation Release to ensure proper Compatibility and a Smooth Upgrade Process. → [List of Migration Scripts](https://return.eon.com/d/d.action?p000mvgi00j5e200d0000000000000000b0c3x2nd2rf6iweueg7zy3y0000b2000000dntzh2m) ## Technical Alert: Adobe Target & Experience Fragment Configuration For Solutions utilizing Adobe Target that encounter Issues with incorrectly externalized URLs (Broken Links) within Experience Fragments, please follow these Instructions: It is essential to verify that the Externalizer is accurately defined within the Experience Fragment Configuration. If this Field remains empty, Adobe will automatically select the first available URL from the Dropdown Menu, which may lead to Errors. To resolve this, follow these Steps: 1. Navigate to the **Experience Fragments Console** in **AEM**. 2. Locate the **Directory** containing your **Experience Fragment** and select it. 3. Choose the **Properties Option** from the **Toolbar**. 4. Switch to the **Cloud Services Tab** within the **Properties Dialog**. 5. Select the intended externalized **Domain** from the **Dropdown Menu**. ## Upcoming Breaking Change Please refer to our separate Deprecation Newsletter for detailed Guidance on upcoming System Changes. As Part of our Brand Revolution, the theme.json Color Palette will be cleaned up in the First Release of 2026, removing all Legacy Colors. We strongly recommend migrating your Custom Components and Background Settings to the current 2025 Default Values (e.g., *eon-white* and *eon-grey100*) immediately to prevent Display Issues. ## Default UI-KIT Version ##### Default Version for Release: eon-ui-kit v_4.35.0 All AEM Releases are tested against a default UI-Kit Version, which is set in CAC MultiBrandMainConfig as **Fallback**. If CAC MultiBrandMainConfig is not set manually, then this Version will be set for your Website. Solutions having their own UI-Kit (e.g. Suewag, Energiewacht) will always have to update manually. [Release Documentation in Git](https://statics.teams.cdn.office.net/evergreen-assets/safelinks/2/atp-safelinks.html) ## 1. Features All Features will be documented in the Foundation Showroom (latest three Weeks after the Release). #### Quote We implemented an AEM Editor Dialog for the Quote Component, grouping all supported Properties into clear Tabs for Image, Content, and Styling. This allows Content Editors to configure Quotes consistently across Brands with minimal Setup and safe Defaults. **Button** [DDSMBFOUN-12939](https://jira.eon.com/browse/DDSMBFOUN-12939?src=confmacro) #### Migration script for Component Policies: Allow Form Grid inside Dynamic Content Areas The implementation of a Migration Script for Component Policies allows the Form Grid inside Dynamic Content Areas. This enables Content Editors to structure optional Form Elements in two Columns. It is ensured that all listed Components are available (e.g., Date Picker, Form Checkbox, Image) and Form Values are submitted correctly, even when Elements are nested in multiple Layers. **Button** [DDSMBFOUN-13369](https://jira.eon.com/browse/DDSMBFOUN-13369?src=confmacro) #### Add Dialog Configuration for Click and Hover Events on Clickable Image We added Dialog Configuration for Click and Hover Events on the Clickable Image Component. This enables Editors to configure Interactions directly in the Component, supporting Events like clickableImageItemClick and clickableImageItemHover. **Button** [DDSMBFOUN-10284](https://jira.eon.com/browse/DDSMBFOUN-10284?src=confmacro) ## 2. Enhancements ## 2.1 Render link when image is hidden on mobile We ensured that Editors can configure a Link even when the Image is hidden on Mobile. When "Hide Image on Mobile" is active and a Link is set, We now render the Link (via eon-ui-link) instead of the Image on Mobile Devices, providing Users with a tappable Call-to-Action. [DDSMBFOUN-13159](https://jira.eon.com/browse/DDSMBFOUN-13159?src=confmacro) ## 2.2 Enforce fetchpriority for all hero images We enforced Fetchpriority for all Hero Images. We added Support for the fetchpriority Property to the eon-ui-image Component and automatically applied the Value "high" to all Images within the Hero Section. This measure helps Browsers prioritize Above-the-Fold Content to improve LCP (Largest Contentful Paint). [DDSMBFOUN-12608](https://jira.eon.com/browse/DDSMBFOUN-12608?src=confmacro) ## 2.3 Highlight Banner - Add Link to Experience Fragment in CAC We added a direct Link to the referenced Experience Fragment within the Highlight Banner CAC Dialog. This allows AEM Editors to quickly access and edit the linked Fragment without manual Navigation, significantly improving Workflow and Efficiency. [DDSMBFOUN-11786](https://jira.eon.com/browse/DDSMBFOUN-11786?src=confmacro) ## 2.4 Number - Add Alignment Option to Number Component We added an Alignment Option to the AEM Dialog of the Number Component. This allows Content Editors to configure the Alignment of the Component Text based on Brand-Specific Rules, with Options dynamically pulled from the Theme Configuration. [DDSMBFOUN-11634](https://jira.eon.com/browse/DDSMBFOUN-11634?src=confmacro) ## 2.5 Component Policies: Allow Form Grid inside Dynamic Content Areas We ensured that Editors can configure a Link even when the Image is hidden on Mobile. When "Hide Image on Mobile" is active and a Link is set, We now render the Link (via*eon-ui-link*) instead of the Image on Mobile Devices, providing Users with a tappable Call-to-Action. [DDSMBFOUN-11352](https://jira.eon.com/browse/DDSMBFOUN-11352?src=confmacro) ## 2.6 Enrich EnumInjector with subnodes Logic We enriched the EnumInjector with Subnodes Logic. This Means the Annotation EnumValueMapValue now supports the inclusion of Subnodes in its Name Property, allowing Developers to reference JCR Properties to reflect our Data Structure. [DDSMBFOUN-12449](https://jira.eon.com/browse/DDSMBFOUN-12449?src=confmacro) ## 3. Bug Fixes by Foundation & OPS Team ## 3.1 An extra Wrap (Padding) on the Container when the Number Component is left aligned We fixed an Issue where Extra Padding was added to the Container of the Number Component when it was left aligned. [DDSMBFOUN-13368](https://jira.eon.com/browse/DDSMBFOUN-13368?src=confmacro) ## 3.2 Quote Component broke when added Content Header, Offset Teaser and Box Components We fixed an Issue where Extra Padding was added to the Container of the Number Component when it was left aligned. [DDSMBFOUN-13303](https://jira.eon.com/browse/DDSMBFOUN-13303?src=confmacro) ## 3.3 Incorrect Payload sent for Unselected Radio Button with Dynamic Areas in Foundation Form We fixed an Issue where an incorrect Payload was sent for Unselected Radio Buttons within Dynamic Areas in the Foundation Form. Now, the Payload correctly includes Data only for the selected Option's Input Field, excluding Unselected Options and their null Values. [DDSMBFOUN-13270](https://jira.eon.com/browse/DDSMBFOUN-13270?src=confmacro) ## 3.4 Form Grid Button Margin We fixed several Issues in the Mobile Viewport regarding the new Header Component. Specifically, We removed the incorrect Dividers displayed at the Bottom of Mobile Flyout Menus and eliminated the non-functional Menu Item, ensuring a clean and functional Navigation on Mobile Devices. [DDSMBFOUN-13203](https://jira.eon.com/browse/DDSMBFOUN-13203?src=confmacro) ## 3.5 Incorrect Display of Dividers and non-functional Item in the Mobile Viewport We fixed an Issue where Extra Padding was added to the Container of the Number Component when it was left aligned. [DDSMBFOUN-129999](https://jira.eon.com/browse/DDSMBFOUN-12999?src=confmacro) ## 3.6 Dropdown | Chips for Selected Items not Displayed We fixed an Issue where Chips (Tag Pills) for preselected Dropdown Items did not display on Initial Page Load. We ensured that preselected Items correctly display their Chips immediately, resolving the Problem caused by missing value Attributes. [DDSMBFOUN-10876](https://jira.eon.com/browse/DDSMBFOUN-10876?src=confmacro)