Disabled component on XF does not link to another page (general template)

Hi @minimeatball 

It is a designed behavior in Adobe Experience Manager (AEM) when authors create an Experience Fragment (XF) template containing both disabled and active components. When linking the XF template to another page under the sites, the disabled component will not be rendered on the page view in both wcmmode=disabled (Edit mode) and publisher view. Instead, there are visual indicators to convey the presence of the XF container on the page and its association with disabled content.

To clarify further, let's explore the visual indicators and how they manifest:

• Visual Indicator for XF Container: When a page contains an XF container that links to an XF with disabled content, AEM usually provides a visual indicator within the authoring interface to signify the presence of the XF container. This indicator might be an overlay, an overlaid message, or an icon that shows authors that an XF is present on the page.
• Indication of Linked XF: In addition to the visual indicator for the XF container, AEM may also display an overlay, an icon, or a path to indicate that the XF container links through to an XF with disabled content. This visual cue helps authors understand that the XF container is associated with disabled content and provides context for its usage.

These visual indicators serve as a means of communication to authors, ensuring they are aware of the disabled content's presence within the XF and its relationship with the XF container on the page. While the disabled components do not appear in the published page view, these indicators enable authors to preview the XF's content and understand how it contributes to the overall page layout during the editing process.