This location is within the granite:InternalArea meaning Nodes
classified as internal cannot be overlaid, inherited, or used directly.
These nodes are meant only for internal functionality of AEM. How do we
just comment and leave it there. is there a way to make the
functionality work with a fixed code approach..?
@sanjeevkumart45 1. you need to write custom JS code to add a button on
the CF editor screen or another way is just overlay
button. Use the following coral UI style guide to understand each CSS
2. The second thing is you need to write a custom servlet to handle the
I don't think it will be a trivial task to complete. Check the CF node
structure: - original
/content/dam/test/t3/jcr:content/renditions/original - version
/content/dam/test/t3/jcr:content/renditions/test_var_1 and teh metadata
placeholder is common for both variations:
Hi sanjeevkumart45948422 Even I have the same doubt, but when I spoke
with Adobe Target experts, they mentioned, currently AEM doesn't export
XF to any folder automatically. You may have option to move it to
folder, but that would be manual.If you figure out any solution for
this, please let me know.