Getting 404 when try to add some fragment in the deployed package

[#1]

Hi Members,

I have created one package of experience fragment content and deployed it in another environment, when I try to create some more experience fragment in the deployed package in another environment, on click on the OPEN button after creation, it gives sometime 404 error. But when click on DONE button then open it for editing it works fine.

If anyone can share some idea what may be causing the issue?

Both of the environment is having AEM 6.4 with service pack 6.4.6.

Thanks

Umesh Thakur

[#2]

Hello @TUmesh,

Can you please provide some error.logs and review the stack trace. I am suspecting that you might not have copied over some resources, such as the editable templates or components.

[#3]

Hi,

You had created Experience Fragments in Last version then you added that particular components, same as the procedure you have to follow in new instance also create a Experience fragments after that add the reuired components on that one and try to drag and drop into your Front End Location.I think this one will work for you.!

[#4]

Hi,

It is a known issue and not fixed until 6.5.1

You can open a daycare ticket to check the status of the fix.

[#5]

I could not find any issues logged internally for this issue. @Arun_Patidar  - Do you have any ticket reference that I can use to check?

That said, All bug fixes in the latest SP release for 6.5 are mentioned at [1]

[1] https://docs.adobe.com/content/help/en/experience-manager-65/release-notes/service-pack/sp-release-n...

[#6]

Sure @jbrar, please find details below:

Adobe CQ Ticket : 201359

The issue you report is a known one that is already solved in the current master, internal reference: CQ-4266556 Due to the low priority and the low impact, this will unfortunately not be backported to 6.5

A support fix for 6.5.2 The modification is done in the node "/libs/cq/experience-fragments/content/v2/experience-fragments/createxfwizard/jcr:content/body/items/form/successresponse" where the value or the property "open" needs to be changed to "/bin/wcmcommand?cmd=open&_charset_=utf-8&path={Path}"

[#7]

There is a workaround for this mentioned on the below link:

https://helpx.adobe.com/in/experience-manager/kb/URLs-with-encoded-slashes-do-not-work-in-AEM.html