--- title: "AEM Release 4.66.0" description: "AEM Release AEM Release 4.66.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-66-0.html lastModified: 2026-09-23T10:08:53.808Z --- # AEM Release 4.66.0 ![](https://www.eonshowroom.eon.com/cdm-assets/is/image/eon/GettyImages-906577952-1%3A2-1?qlt=50&fmt=webp) ## AEM Release 4.66.0 Release Date: 02.07.2026 Build-Version: 4.66.0-14264545 [Release Scope](https://confluence.agile.eon.com/wiki/spaces/ddsmbfoun/pages/975440417/AEM+Release+4.66.0+02.07.2026) [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.44.0 ## Information Automated Asset Monitoring for Productive Images To ensure consistent **Image Quality** and proper **Rendering** across all **Channels**, we are introducing an automated **Scan** of productive **Image Assets**. From now on, you will receive a periodic **Email** from the **ESP GitLab Sender** containing: - An **Overview** of affected **Assets** - A detailed **Technical Report** as an **Attachment** **Required Actions for Listed Assets:** If any **Assets** are flagged in the **Report**, please ensure they are properly processed or re-uploaded in **AEM** if necessary. This **Process** helps maintain optimal **Image Delivery** and avoids visual **Disruptions** on live **Websites**. ## Default UI-KIT Version ##### Default Version for Release: eon-ui-kit v_4.a.b 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://git.eon-cds.de/repos/eon-is/frontend/eon-ui/eon-ui-components/-/releases/4.4.2) ## 1. Features All Features will be documented in the Foundation Showroom (latest three Weeks after the Release). #### 1.1 Structured Data (Schema.org via JSON-LD) Best-Practice POC This Spike establishes a decoupled Proof-of-Concept (POC) and developer guidelines for generating standardized Schema.org Structured Data in AEM. It defines a distributed SchemaProvider interface pattern, allowing components to contribute typed data fragments while a central Page Aggregator compiles them into a single, valid @graph JSON-LD output per page. The spike includes architectural documentation (ADR), mapping rules for entities (such as WebSite, Organization, BreadcrumbList, and ImageObject), and a validation checklist for Google Rich Results Compliance. [EONWCMS-367](https://jira.eon.com/browse/EONWCMS-367) ## 2. Enhancements ## 2.1 Grid Control Compatibility for Footer Bar This Enhancement expands the Layout Flexibility of the Footer Bar by allowing it to be placed inside a Grid Control as a parent Component. This update enables Website Owners to position additional Content (such as a Widerruf-Button) directly next to the Footer Bar within an Experience Fragment. It updates the necessary Component Policies to support this nested Hierarchy while ensuring that existing page implementations and analytics Tracking remain completely unaffected. [EONWCMS-1231](https://jira.eon.com/browse/EONWCMS-1231) ## 2.2 Color Scheme Options in Navigation Editor This Enhancement exposes new Color Scheme options directly within the Navigation Editor dialog. It allows Content Editors to select background and border styles (such as grey100 and white, dynamically populated from the theme.json file) for both the main website navigation and the toolbar components. The Dialogue includes a system hint noting that the feature requires UI Kit 4.44.0 or higher, while ensuring all existing configurations default gracefully to undefined and remain completely unchanged. [EONWCMS-1229](https://jira.eon.com/browse/EONWCMS-1229) ## 2.3 Solr Core and Content Path Binding Integration This Enhancement introduces a strict Code-Level Validation Check to permanently prevent Cross-Core Indexing within Solr Search Operations. By modifying the Indexing Execution Flow, the System now validates each Content Path against configured Path-to-Collection Mappings before initiating the Indexing Process. This ensures that Content is only mapped and indexed to its own authorized Tenant Core or Collection, making Search Indexation across different Brand Environments highly secure and foolproof. [EONWCMS-1192](https://jira.eon.com/browse/EONWCMS-1192) ## 2.4 Contact Bar Link Target Option Enhancement This Enhancement adds an Option to the Contact Bar Item Component Dialog, allowing Editors to choose if a Link opens in a New Window by rendering the target="_blank" Attribute. The Update also enforces /content as the default Link Target Root to provide better Editor Guidance while keeping existing productive Page Content and default same-tab Link Behavior completely unchanged. [EONWCMS-1102](https://jira.eon.com/browse/EONWCMS-1102) ## 2.5 Dummy Product Component & Data Ownership Definition This Enhancement introduces a dedicated Dummy Product Component that serves as a non-rendering Data Provider for Structured Data (Schema.org) integration. It acts as the single source of truth for Product and Offer details—such as Price, Brand, SKU, and Availability—overriding standard Page Properties to ensure consistent JSON-LD output for Search Engine Crawlers. [EONWCMS-913](https://jira.eon.com/browse/EONWCMS-913) ## 2.6 Auto-Selection for Related Articles Teaser Wall This Enhancement introduces an automated Auto-Select Mode for the Related Articles Teaser Wall Component (displaying 3 or 6 items). Instead of manual curation, the System automatically queries candidate pages below a designated Root Path, excludes the current article, and ranks relevant content based on Tag Overlap combined with a Freshness Boost (recency scoring). This ensures related content stays dynamically updated and highly relevant for users, while fully preserving legacy Manual Selection Mode for existing setups. [EONWCMS-28](https://jira.eon.com/browse/EONWCMS-28) ## 2.7 Accessible Footnote Support in RTE This New Enhancement introduces semantic, bi-directional Footnote Support within the Rich Text Editor (RTE) and a dedicated Footnote Component. Editors can insert inline footnote references via a custom RTE Plugin dialog, which automatically aggregates, numbers, and renders footnotes at the bottom of the page. The System provides fully accessible ARIA Attributes, keyboard navigation, editable headline settings, and full i18n Localization Support across supported brand languages. [EONWCMS-89](https://jira.eon.com/browse/EONWCMS-89) ## 2.8 Schema.org Freshness Signals for AI & LLM Crawlers This Enhancement extends the global Page Sling Model to automatically expose explicit Page Freshness Signals (datePublished and dateModified) formatted in ISO-8601. The values are delivered directly via Server-Side Rendered (SSR) HTML Meta Tags and within the WebPage Schema.org JSON-LD structure. This allows AI Systems and LLM Crawlers to reliably verify Content Recency (such as tariffs and pricing) without requiring client-side JavaScript Execution. [EONWCMS-352](https://jira.eon.com/browse/EONWCMS-352) ## 2.9 Central JSON-LD Aggregation & Rendering Architecture This Enhancement introduces a centralized SchemaAggregatorService that shifts JSON-LD Structured Data generation exclusively to the Page Wrapper. Instead of individual components rendering their own script tags, components now expose Schema Data Fragments (such as ImageObject, Place, or ContactPoint) via Sling Models. The System aggregates these contributions into exactly one unified *