{"scripts": ["create path /home/groups/test(rep:AuthorizableFolder)","create group test_users with forced path /home/groups/test","set properties on authorizable (test_users)/profile\n set givenName to \"Test AUthors\"\nend","add test_users to group contributor","create group TEST_USERS_1 with force...
we are using repoinit to initialize creating groups and maintaining permissions. This is working fine on initial creation. but on any change in the repoinit file I'm not seeing the permissions getting updated unless i remove the parent folder path.where all the users and groups are created Just wa...
I am seeing an response header being added (Expires:Thu, 01 Jan 1970 00:00:00 GMT) in AEM publish for all the requests like clientlibs/page requests and images. This is preventing the responses to be cached from dispatcher and cdn. I don't see this being set in code base or acs commons dispatcher co...
Followed steps for content sync with dyncamic media and connected assets1) Reprocess assets for bulk workflow in central dam, This will update the dam scene7 properties, Use Bulk asset workflow and change the scene7 config to sync immediately on reprocess2) Export metadata ("dam:scene7CompanyID","da...
we are using central dam which is connected to the sites dam, our central dam is configured with dynamic media. we have the latest content in prod which we want to sync to stage, the architecture is the same. How do we plan a full content sync to stage. so that the dynamic media references are no...
thanks for the reply, would it make sense to consolidate the component policy's once everything is live in production and clean up the duplicate policy's if there are any across templates.
We are planning to move from static templates to editable templates. As a best practice should we commit component content policy's that are defined for each components in code base or keep it editable for the authors. What challenges do we face with either approach.