Hi @rakesh_h2 ,   Did you check https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/infinity-json-in-publish-instance/m-p/422820#M120437 this thread ?

Hi @martin_ecx_io , As an AEM as a Cloud Service customer, you do not have direct control or visibility over the specific region where the offsite backup is stored. The purpose of this approach is to ensure that your AEM content is securely backed up and available for recovery in case of any unfores...

Hi @arkive1 ,   The warning messages you are encountering suggest some deprecated packages and potential compatibility issues with the versions of Node.js and npm you are using. Make sure you have a supported version of Node.js installed. It is recommended to use a stable version of Node.js. You ca...

Hi @kjj , Yes, the com.day.cq.contentsync.handler.util.RequestResponseFactory class is deprecated in AEM. The recommended substitute for this class is to use the org.apache.sling.api.request.RequestResponseFactory interface instead. To obtain an instance of the RequestResponseFactory interface, you ...

Hi @Katinka , @kautuk_sahni  The concept is interesting, but it appears to have limited applicability. Is there a way to make it more generic and applicable to a wider range of scenarios?

you have to remove the protection from the jcr:created property, then only you should be able to restore the version of the page successfully using the pageManager.restore() method.   Check if the page has the jcr:created property marked as protected. If it does, remove the protection before restori...

In AEM, certain properties like jcr:created are marked as protected to ensure their integrity and consistency. These properties are typically auto-generated and managed by the system, and modifying them directly is restricted to maintain data integrity.   To resolve this issue when using pageManager...

It is strange ,because the cq.authoring.dialog category is a default category that is commonly used for dialog fields that are intended for authoring purpose. But using categories="[cq.authoring.dialog.all]", you are including all available dialog field types in the category selection for your dialo...