All of the pages on my site have their own sling types set up, and the sling:resourceSuperType inheritance is:   myapp/components/pages/page-type --> sling:resourceSuperType --> myapp/components/page --> core/wcm/components/page/v3/page   Now, I am trying to create a model for myapp/components/page ...

I have a pathfield where I am allowing the user to select one or more templates in my site:   <templates jcr:primaryType="nt:unstructured" sling:resourceType="granite/ui/components/coral/foundation/form/pathfield" emptyText="Optional template(s) to filter results by" fieldDescription...

I am seeing log files grow to multiple GBs daily reporting errors out of GraphQL:   [POST /content/_cq_graphql/<mysite>/endpoint.json HTTP/1.1] com.day.cq.dam.commons.metadata.SimpleXmpToJcrMetadataBuilder property [imageFeatures] doesn't have namespace prefix, skipping. metadata node: [/content/dam...

Hi Kiran,   Do you have an example of how to do this?  That documentation doesn't specify how to send the resource to sightly, just the properties of the dialog field.   Additionally, in case the user picks a dam asset, is there a way I can grab the alt text from that asset to also render in sightly...

I have a need to add an extra image field to Teaser components.  Basically, I am trying to create a By Line type effect that can be added to teasers.   The problem I am having is that both the Teaser and By Line components are inheriting from the core Image Component via their sling super type.  I w...

I just upgraded to 2.21.2 and the issue still occurs locally with the cloud quickstart jar.

This issue only occurs in AEM SDK v2023.1.10675.  I have confirmed that it does not occur in any 2022 release.  This issue is confirmed on both cloud managed environments as well as with the quickstart JAR.   When using the Text Component, I am settings some text to be aligned in the center.  When I...

So I've added a client lib and set the margin-inline to align with my grid.  This works until you go into the layout mode, in which case all of the component overlays (e.g., cq-draggable elements) have their boxes drawn incorrectly with margin offsets.  I can't seem to target these in CSS and adjust...

That's a good idea- basically influence the CSS of the overlay?  Where would this CSS snippet go?  e.g., how do I get custom CSS added to the editing interface?

Did you ever find a solution to this?