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.

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.

We have multiple reps and for each rep we will have a bio that we are storing in content fragments. I want to include this bio on an AEM page based on a passed-in value. Each content fragment will be named according to a unique rep value, like a rep number. For instance, the path would be something ...

We are working on upgrading our image component from V2 to V3. I’m running into an issue with the images our on our site displaying larger in height and out of proportion. I am wondering if anyone else has experienced this and/or knows of a solution.  We do have widths set in the image component pro...

Thanks, @lukasz-m. I knew this was deprecated, but I was hoping in V3 there was an alternative similar to what @GabrielWalt wrote here, and I just missed it, but I guess that didn't make the cut. Thanks again. Jon

We are upgrading our page component to version 3. When I test this locally, I notice the Open Graph meta tags are no longer present in our page source. The head.socialmedia.html file is gone in V3, and this seems to be what included it before. Is there a new include I need to apply, or do I need to ...