Experience Fragment - URL Encoded Issue | Community
Skip to main content
nafeeskhanp7683
New Participant
Nov 29, 2018 6:06 PM UTC
Solved

Experience Fragment - URL Encoded Issue

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.

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 )

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

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
smacdonald2008
smacdonald2008Accepted solution
Level 10
Jan 10, 2019 4:09 AM UTC

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.

View reply

6 replies

smacdonald2008
smacdonald2008Accepted solution
Level 10
Jan 10, 2019 4:09 AM UTC

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.

Translate
    Shashi_Mulugu
    Shashi_Mulugu
    New Participant
    Jan 7, 2019 8:46 AM UTC

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

    Translate
      nishantg4411613
      New Participant
      Jan 7, 2019 7:21 AM UTC

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

      Translate
        nafeeskhanp7683Author
        New Participant
        Nov 30, 2018 5:13 AM UTC

        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.

        Translate
          smacdonald2008
          smacdonald2008
          Level 10
          Nov 30, 2018 4:06 AM UTC

          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

          Translate
          Mallik-Vamaraju
          Level 3
          Feb 15, 2020 3:21 AM UTC
          We are on 6.4 (service pack 2.0) and yes we are still facing this issue. We are not facing this issue on our local instances. It is happening on our QA and staging environments. Please let us know if anyone figured out anything particular about this issue.
          Translate
          Terms & ConditionsAccessibility statement

          Loading footer...