You can try to set permission with regex globbing pattern on the JCR node - on any node in the hierarchy. 

You can try relay replication. A publisher can be configured to relay replicate the content it received on activation from author. One aspect to take care is typically you would be having multiple publishers. You would have to designate one and configure it for relay replication as otherwise every p...

Check the oak run version you are using. The check mode was introduced in later versions of oak run tool.

One option is to edit the journal.log by deleting the last few entries to take the repository to a previous state. This is a crude way of restoring and not sure if Adobe supports this approach. Take your Adobe support advice before trying this. For a try, you can take a copy of your AEM and try. Not...

Think the key difference is with reusing the same asset in other pages / sites.Images maintained under  /content/dam/  can be reused across multiple pages. Typically these image assets is maintained by separate team. Also only the images under  /content/dam/ show up on the damadmin console for manag...

The enableTTL configuration available in the dispatcher configuration works based on the cache control response header for the pages served. This can be used if the application is setting the correct header values for page expiry. If the application is not setting the cache control headers, we can u...

You can use the resource resolver[1] to check how these 2 paths are getting resolved. Sometimes you might have some alias or vanity url pointing to /hello [1] http://localhost:4502/system/console/jcrresolver

If the volume of content changes is low, you can also setup replication agents to replicate content to lower environments based on events (activated, modified...). 

These 2 nodes has the property to enable lock/unlock functionality./libs/wcm/core/content/damadmin/actions/lock/libs/wcm/core/content/damadmin/actions/unlockSet the property 'disabled' under these nodes to true or false to disable or enable the respective functionality,

We had the same issue and found that when 6.1 is installed with nosamplecontent runmode, activate tree functionality is missing. We can package these nodes from another instance (without nosamplecontent runmode) and install it to get it working.