AEM 6.5 LTS still renders the fragment, but editors cannot change it

An existing page still renders, yet an editor cannot select a replacement Content Fragment in the classic component dialog. Rendering and authoring are separate acceptance tests; one passing does not make the migration complete.

Identify the component before changing content

Inspect the page resource type and the installed Core Components version. Adobe says most Foundation Components are deprecated in 6.5 LTS and recommends Core Components. Check the fragment model, folder configuration and dialog validation on a copy of the page. A disabled control is a symptom, not proof of a specific AEM defect.

Compare authoring behavior side by side

Place the same fragment in a controlled test page using the Core Content Fragment component. Test initial selection, replacement, variation, publish, rendering and any data-layer consumers. Document what custom overlays or CSS depend on the legacy component before replacing it. That catches a visual regression that a dialog-only test misses.

Migrate by editorial need

Prioritize pages authors actively edit, then high-value templates. Give editors a supported replacement and a rollback route. Leave rendering legacy pages under observation while the migration is tested; the right pace depends on authoring demand and the support posture of the actual deployment.

Adovo’s view

A page that displays is not necessarily a page a team can operate. The migration contract must include the editor's next change, not just today's render. That is where legacy component debt becomes visible to customers.