<?xml version="1.0" encoding="UTF-8"?> <jcr:root xmlns:sling="http://sling.apache.org/jcr/sling/1.0" xmlns:granite="http://www.adobe.com/jcr/granite/1.0" xmlns:cq="http://www.day.com/jcr/cq/1.0" xmlns:jcr="http://www.jcp.org/jcr/1.0" xmlns:nt="http://www.jcp.org/jcr/nt/1.0" jcr:primaryType="nt:u...

I want to make two modifications to the paraformat options within the AEM Rich Text Editor of the Core Text Component.I want to change the description of the blockquote node from “Quote” to “Blockquote.” Since I am overlaying the AEM Core Text Component, I assumed I could change the description valu...

On page creation, page move, etc., can an alert somehow be added to warn the author the page name already exists instead of AEM creating a page variation with a number at the end?

Thank you @Mahedi_Sabuj! This is exactly the information I needed to move forward.

The Quick Search Core Component does not return text results from within the Accordion Core Component. Is this by design, a limitation of the search, or am I missing a configuration somewhere?I found a similar question from 2017.https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manag...

Hi @sreenu539, What worked for us were two things:We missed adding core.wcm.components.image.v3 to the embed property of clientlib.baseWe had to rebuild the clientlibs after deploying. Once that was done, the images rendered correctly.Also, make sure your width and height properties are present.

Thanks. I assumed this was the case but was hoping to not have to create a custom component. One thing, AEM does not capture width and height properties of SVGs when we upload them into the DAM to then use in the component HTL. I assume this is intentional?

Lighthouse is listing "Image elements do not have explicit width and height" for SVG images on our site. I saw there is an open issue about missing width and height for SVG files, https://github.com/adobe/aem-core-wcm-components/issues/2270, but has anyone come up with a decent workaround in the mea...

I deferred upgrading this to work on other things but am now returning and the same issue is occurring. Hopefully this will bump the question back up in the list.

Thanks, @lukasz-m for the quick reply.   So, it’s a little more involved than just adding an include, then. It’s more of a case of adding code in a similar way to the core CF component?   Thanks again for the insight.