Preventing accidental deletion of referenced topics/files in AEM guides

Last update: Mon Nov 18 2024 00:00:00 GMT+0000 (Coordinated Universal Time)

This article addresses a known issue in Adobe Experience Manager (AEM). You can delete guides’ topics/files referenced in maps/rootmaps without receiving the Force Delete prompt to confirm the deletion. This happens when rootmaps contain errors.

Description description

Environment

Adobe Experience Manager (AEM)

Issue/Symptoms

When you delete guides’ topics/files in Adobe Experience Manager (AEM) that are referenced in maps/rootmaps, you should be prompted with a Force Delete option to confirm the deletion. However, you are able to delete these files without receiving the prompt, especially when rootmaps contain errors.

Symptoms:

You can delete topics/files directly without receiving the Force Delete confirmation.
References in maps/rootmaps are not detected, allowing deletions without warnings.
This issue primarily occurs when rootmaps contain errors.

Resolution resolution

Follow the below steps to prevent accidental deletion:

Ensure error-free content:
- Review and ensure that all rootmaps and content files are error-free.
- Errors in the content can prevent AEM from recognizing references.
Create an Assets Report:
- Utilize AEM’s reporting features to identify files with errors.
- Specifically, create a report on the Metadata jcr property fmErrors to find assets containing errors.
Configuration review:
- Verify that the AEM configurations related to file deletion are set up correctly.
- Check settings such as allow_unsafe_delete_for_all and allow_unsafe_delete_for_delete_assets_group to ensure they align with organizational policies.
User training and documentation:
- Provide training to users on the Force Delete mechanism and its implications.
- Update documentation to include steps for managing file references and deletions effectively.
Testing and validation:
- Conduct thorough testing in a staging environment to ensure that the error-free content behaves as expected.
- Confirm that the Force Delete prompt appears when attempting to delete referenced files.

Cause

The issue arises when rootmaps or content files contain errors. These errors prevent AEM from detecting references, leading to the absence of the Force Delete prompt during deletions.

For detailed steps on creating an Assets Report and managing configurations, refer to the AEM documentation on Preventing Deletion of Referenced Files.

recommendation-more-help