Restore Tree and Restore version in siteadmin

[KannanCh2]

Hi All 

When I open the asset restore options in SiteAdmin, both the "Restore Tree" and "Restore Version" options are disabled. Why are these options disabled, and is there any way to enable them?

what is the use case of those ?

Aem version : 6.5.20

Thanks

[Jörg_Hoh]

Are there any versions available for this page at all?

[KannanCh2]

For page level , we can able to see that options .But when we go with assets , both options are always in disabled .So just want to know the use case and how to enable that options ..

[Jörg_Hoh]

Do you have versions created for assets?

[Harwinder-singh · Accepted solution]

@KannanCh2 The reason most likely is that there are no versions that exist to which the restore can happen. The restore basically helps to restore the state of the AEM resource to a specific version. If there are no versions then there is nothing the system can restore to.

[gkalyan]

@KannanCh2 

There is no "restore" for assets. You are trying to open DAM assets in siteadmin, according to your screenshot. If you try to open same file in Damadmin, you won't see the "restore" option in the tools. 

This you see Touch UI as well, you can see "/content/dam/project" will not have "restore" while "/content/project" will have restore option.

To restore assets, you can try to use "timeline" in touch UI.

[HrishikeshKa]

Hi @KannanCh2 ,

In AEM 6.5.20, the "Restore Tree" and "Restore Version" options in SiteAdmin being disabled typically indicates that there are certain conditions or configurations not met to enable these options. Let's delve into the possible reasons why these options are disabled and how you might enable them.

Possible Reasons for Disabled Options

1. Permissions and User Privileges:

   • Ensure that you have the necessary permissions to perform restore operations. Users need to have specific rights to access versioning and restore functionalities.

2. Node Versioning Not Enabled:

   • The content nodes or assets might not have versioning enabled. AEM must have versions of the assets or content trees to restore to a previous state.

3. Workflow Lock:

   • If the content is locked by a workflow or any process, restore options might be disabled until the lock is released.

4. Path Configuration:

   • The path or the specific node you are trying to restore may not be configured correctly for versioning or may not have any versions created.

Use Cases for "Restore Tree" and "Restore Version"

Restore Tree:

• Use Case: When you need to restore an entire subtree of content to a previous state, which is helpful in cases where multiple changes were made to a section of the site and need to be reverted.
• Example: If multiple pages under a specific section were edited or mistakenly deleted, you can restore the whole section to a previous state.

Restore Version:

• Use Case: When you need to restore a specific version of a content node or asset, useful for rolling back to a previous version after an undesired change.
• Example: If an image asset was replaced or edited incorrectly, you can restore it to a previous version to correct the change.

Steps to Enable "Restore Tree" and "Restore Version"

1. Check Permissions:

   • Ensure your user account has the necessary permissions. Check your user group settings and permissions in AEM.

2. Enable Versioning:

   • Make sure versioning is enabled for the content nodes you wish to restore. This can typically be checked and enabled in the properties of the nodes.

3. Create Versions:

   • Ensure that there are previous versions available to restore. You can manually create versions of nodes or configure workflows to automatically create versions upon changes.

4. Release Workflow Locks:

   • Check if the content is locked by a workflow. If it is, complete or terminate the workflow to release the lock.

Steps to Verify and Enable Versioning

1. Check Node Type and Mixins:

   • Verify that the nodes have mix:versionable or appropriate versioning mixins enabled.

2. Manual Version Creation:

   • In CRXDE Lite, you can manually create versions by right-clicking the node and selecting "Create Version."

3. Configure Automatic Versioning:

   • Configure workflows or event listeners to create versions automatically upon changes.

Example Workflow to Create Versions Automatically

<workflow>
    <step type="participant">
        <process name="Create Version">
            <property name="command" value="createVersion"/>
        </process>
    </step>
</workflow>

To enable the "Restore Tree" and "Restore Version" options in AEM 6.5.20, you need to ensure that:

• You have the necessary permissions.
• Versioning is enabled for the relevant content nodes.
• There are existing versions available to restore.
• The content is not locked by workflows or other processes.

By addressing these areas, you should be able to enable and use these restore functionalities effectively.

[kautuk_sahni]

@KannanCh2 Did you find the suggestions from users helpful? Please let us know if you require more information. Otherwise, please mark the answer as correct for posterity. If you've discovered a solution yourself, we would appreciate it if you could share it with the community. Thank you!