Please please please update to more recent version. AEM 6.0 is out of support for quite some time, and AEM 6.5 has fixed many of these issues you are facing with Oak 1.0.x.)   (And even if you cannot update immediately: There are much newer Oak versions available for it. I know of at least Oak 1.0.4...

Hi,   this is not possible, because the publish instances do not know each other. Also depending on the type of deployment their number can vary. In would always recommend to execute such activities on author whenever possible.

What do you mean with "sections"? If it's about designs and layouts, you could try it with editable templates, and if it's about content Content Fragments/Experience Fragments are probably the way to go.

Why do you want to re-create a property with a different value? If that node belongs to your custom application, then change it there and not via repoinit. And you should not be required to change a property which is part of the product.

The problem is the definition of "currentPage" and how it is calculated.   As far I understood, it is always relative to the current resource which this SlingModel is adapted from; that can be the page which is requested, but it could also be any other page; this depends solely on the rendering proc...

IIRC DynamicMedia requires a dedicated license. But I am not familiar with licensing aspects, sorry.

If you want to write the short-path as URL within the page itself (or a different page), just write the "long" path there. If a mapping exists AEM will do that for you automatically. At least for pages, not for JSON payloads etc.   For these you need to use the ResourceResolver as indicated above.

For reference: If you use the latest Core Components and Dynamic Media, a WebP image will be delivered by DM if the browser can handle that. And to make that work you don't need to do anything (but using DM and Core Components).

In that case you need the resouceResolver.map() API call.

The spec does not mention any limits, but of course the implementation makes some assumptions about sizes; exceeding them can cause memory problems or make your system slow. That means that if you know that the size of the data you want to store can exceed 100k or more, I recommend to store it in a ...