What version of AEM are you on?

Hello, That's a very interesting question!  It actually inspired me to write a tutorial on nested Multifields. It is pending publication for the moment, but I'll add it as a comment later when it's out.However this question goes a bit beyond what's in the tutorial so let me explain.To access proper...

Hello, Your question inspired me to write a tutorial on how to show/hide or enable/disable fields based on a checkbox (or any other widget).Have a look: https://levelup.gitconnected.com/aem-conditionally-show-or-hide-a-field-based-on-a-checkbox-widget-or-anything-else-6b23b2515810

Hello,One way you could do this is by looking at the dam:size property of the asset, which is the size of the image in bytes. It does not change if you add or edit metadata (eg: Title), but it will change if authors edit the image. You won't be able to tell what changed specifically (could be flip, ...

As far as I know there is unfortunately no easy way to do this. You'll have to write some code.You can find an answer here: https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager-assets/asset-editor-cropping-in-aem-6-3/qaq-p/277716 

Out of curiosity, how did you customize it?

Hi Daniel, From what I understand of your situation, no.data-sly-use is a backend feature with lets you use either the Java or Javascript Use-API (you can see a comparison of the two here). However, whichever Use-API you decide to go with, they are both executed in the backend, before your HTML file...

Hi,What do you need help with specifically? As you mentioned, you currently are overriding nodes that should not be overridden. The CAV page describes the final area:/**  * Defines a node as final, so that it cannot be overlaid  * or inherited by sling:resourceSuperType.  */ [granite:FinalArea] ...

Do you have any errors in the browser console or in error.log?

What version of AEM are you on?