Thank you. Where do I see the changes you made?

HiWe have the following step in our DAM update asset workflow.I cannot find any support for DMImageProcess and understand what are the individual metaData. What I know is that it creates a rendition cq5dam.web.1280.1280.jpeg. Can you please explain. Thanks.<dmimageprocess jcr:created="{Date}2015-...

Hi,I ended up setuping a new instance and installing SP23 on top.Thanks for all your answers and best regards.

Hi @MukeshYadav_  Yes we have in the main pom the following property and we deployed it to the instance:<uber.jar.version>6.5.23</uber.jar.version>

Hi @ButhpurKiran Thanks a lot for your reply.Here are my answers:1) Bundle information: 650 bundles in total - all 650 bundles active2. I stopped the AEM instance, deleted 900 elements in <your-local-aem-install-path>/crx-quickstart/launchpad/installer, restarted the instance and installed AEM-6.5-S...

Hi all,I upgraded my local instance of AEM from SP21 to SP23 using the AEM-6.5-Service-Pack-23-6.5.23.zip package.The http://localhost:4502/system/console/status-productinfo still shows  Adobe Experience Manager (6.5.21.0)Any suggestions why the productinfo does not show 6.5.23.0? This is the output...

Hi @AmitVishwakarma  Just for my understanding, I am wondering if your code is actually implementing your second suggested option (2. Post-process HTML output)?If that is the case, I was wondering if you could suggest how would you go about implementing your first suggested option => 1. Switch seria...

Great thank you very much @AmitVishwakarma I implemented and tested your code for  self closing void elements:// Replace self-closing void elements with HTML5-compliant onesString updatedContent = originalContent .replaceAll("<br\\s*/>", "<br>") .replaceAll("<meta([^>]*)\\s*/>", "<meta...

Thanks so much for your detailed answer.@AmitVishwakarma can you please suggest how would you go about customizing the response (your suggested option 1) 

In my AEM 6.5 template, I have the following code snippet. When it gets rendered on the publish instance, the <br> tag is automatically converted to a self-closing <br/>tag, even though no self-closing tag is present in the original template. The same behavior occurs with the <meta...> tag, which is...