Hi @pradeepdubey82
You can try importer tool built by Adobe for EDS migration.
https://experienceleague.adobe.com/en/docs/experience-manager-learn/sites/document-authoring/how-to/migration-using-importer
Note : it may not work 100% .
Hi @AlexNathanson
As @konstantyn_diachenko mentioned EDS also required IT resources but eliminate the backend/CI-CD overhead. It doe ssupport MSM with EDS-xwalk and also the feature similar to experience-fragment.with EDS you can decide to use :
- Document-based authoring : Since content is being h...
Hi @Shwetha1994
Please check here
https://medium.com/@lathamanivannan/building-the-perfect-rte-in-aem-step-by-step-with-plugin-exclusion-ui-settings-toolbar-7837f8b9d4a1
Hi @bosschaert
You must be pushing the non-editable properties to AEM since those are imported as part of json. Can you try removing the other properties and just push the content property?
Hi @kamalakannank62
Use Repoinit - https://sling.apache.org/documentation/bundles/repository-initialization.html
Example org.apache.sling.jcr.repoinit.RepositoryInitializer~my.cfg.json
"create service user my-service-user with path system/cq:services/myusers",
"set ACL for my-service-user\n allow ...
Hi @Murali__D
AEM requires a valid CSRF token to be sent for authenticated POST, __PUT, or DELETE HTTP requests to both AEM Author and Publish services.
The CSRF token is not required for GET requests, or anonymous requests.
Do you have AEM authentication/CUG on publisher as well?
Hi @SudarshanV1
No, this is not possible, each templates required a policy node with references.You can't refer/inherit template policy from another node except policy itself.
Hi @RohitKu17
Here’s my take:
If you’re technically strong, you should consider roles as either an AEM Backend Developer or an AEM Frontend Developer.
That said, the learning curve for AEM Backend is quite steep—it often takes years to become proficient. Additionally, Adobe is shifting focus with o...