Hi @vaibhavjain2565 ,Please check if you have cq:LiveSyncConfig node present under the live copy in which you are trying to make the changes. Also, If the node is present there, check for the following propertiescq:master : should be pointing to the parent page/blueprintcq:deep : truecq:rolloutConfi...

Looks like the dialogs were not revamped correctly. Try pasting an OOTB cq:dialog inside your component and see if it shows up now.If it does, you may need to check the dialogs which you have revamped. Try this for migrating dialogs/templates from classic to touch UI: https://experienceleague.adobe....

So you're getting the same error in Postman, after allowing empty in the Sling?The filter code looks good, but what about the servlet code? Is it implementing SlingAllMethodServlet? Also, if the request doesn't get blocked, even if the servlet doesn't have a doPost method, it is not blocked, rather ...

Can you try this and see if it works:http://localhost:4502/system/console/componentsGo to "Apache Sling Referrer Filter"Select "Allow Empty"If your requests are getting blocked, this should fix it. - Please check if you have implemented SlingHttpSafeServlet or AllMethodServlet in your servlet.- Try ...

Have you deleted the existing changes which you have already done. Maybe one of them is causing this. Also, the path should include my-site/it/*, to make sure it only picks up pages inside it. I have used this way for CUG login multiple times(6.5.8,6.5.10,6.5.11), and it works.  

You can always overlay the component and make changes, just keep the OOTB component as the sling:resourceType for your component, and make only the required changes. This will keep all the existing properties as it is. And just to make sure that this issue exists in vanilla, try the same in a vanill...

Yes, there are many ways, but what we were trying to do was find the root cause of the issue. Whether it lies within the component or within something which we have overlaid.  If you want to use a different way altogether, you would need to write HTL for the container component and call the image te...

Okay, now to even further reduce the number of places you need to look.Try both the components, but within WKND site page. This can let you know whether the issue is with the template or some overlay which has been done to OOTB feature.

I'm not sure if interrupting the thread would be the best approach.Instead, what I can suggest is, instead of this approach, what you can do is create a workflow launcher which can auto-trigger based on node changes in the particular path/paths. HelpDoc: https://experienceleague.adobe.com/docs/exper...

What you're seeing is an encoded URL in src. You would need to check where it is getting encoded.Can you please check the underlying code, If the SRC is going through any java code which is encoding it.If the SRC is obtained from or processed through any JS code which has encoded it.Also, try to do ...