Experience Fragment - URL Encoded Issue

Avatar

Avatar

nafeeskhanp7683

Avatar

nafeeskhanp7683

nafeeskhanp7683

29-11-2018

Hi Team,

We have been working on experience fragments in AEM 6.3 using custom dynamic templates. We modified the cq:allowedTemplates to give the custom template path. Everything is working fine except for one issue which is the following.

When I create XF using the custom template, it shows the following prompt.

Screen Shot 2018-11-29 at 11.27.17 AM.png

Once I click on Open, I see the there is a console error due to encoding issue in the URL(http://localhost:4502/editor.html%2Fcontent%2Fexperience-fragments%2Ftest%2Ftest.html )

Screen Shot 2018-11-29 at 11.57.42 AM.png

Has someone faced this issue and any piece of advice on solving this would be helpful? kautuksahnismacdonald2008

Accepted Solutions (1)

Accepted Solutions (1)

Avatar

Avatar

smacdonald2008

Total Posts

12.7K

Likes

1.4K

Correct Reply

2.3K

Avatar

smacdonald2008

Total Posts

12.7K

Likes

1.4K

Correct Reply

2.3K
smacdonald2008

09-01-2019

Looks like a bug - please check with customer support. Like i said earlier - i use the existing templates when using Ex Fragments and have never seen an issue.

Answers (4)

Answers (4)

Avatar

Avatar

Shashi_Mulugu

MVP

Avatar

Shashi_Mulugu

MVP

Shashi_Mulugu
MVP

07-01-2019

Yes. Issue exists in AEM 6.4 as well using any template.

Avatar

Avatar

nishantg4411613

Avatar

nishantg4411613

nishantg4411613

06-01-2019

I am facing the same issue. But same is observed when I am using We-retail template.

Avatar

Avatar

nafeeskhanp7683

Avatar

nafeeskhanp7683

nafeeskhanp7683

29-11-2018

No. I don't see any issue with the existing templates.

We have used one of our existing custom template for experience fragments creation. Only the success prompt OPEN fails, rest others (like editing, etc) works perfectly.

Avatar

Avatar

smacdonald2008

Total Posts

12.7K

Likes

1.4K

Correct Reply

2.3K

Avatar

smacdonald2008

Total Posts

12.7K

Likes

1.4K

Correct Reply

2.3K
smacdonald2008

29-11-2018

When you use one the existing templates - are you seeing this issue?

Also - when i have created EF - i use the OOTB template and never had an issue. See how we create EF here -- Working with Experience Fragments and the Experience Manager ContextHub