RedirectTarget Not Working in AEM 6.2 | Community
Skip to main content
A
ankurk67503819
Level 4
November 7, 2016

RedirectTarget Not Working in AEM 6.2

  • November 7, 2016
  • 2 replies
  • 9667 views

Hi Team,

Page properties redirectTarget property is not working in AEM 6.2.

Even it's not working on we retail reference site.

If someone have faced this issue.Please help us.

Regards

Ankur

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

2 replies

Feike_Visser1
Adobe Employee
Feike_Visser1Adobe Employee
Adobe Employee
November 7, 2016

Can you share more details?

    A
    ankurk67503819Author
    Level 4
    November 7, 2016

    Feike Visser wrote...

    Can you share more details?

     


    Hi Feike,

    I have created a page component same as we retail reference site then using this page componenti have created a template using template editor.

    Using which i have created a page .

    On this page if we go to page properties -->advanced tab ----> redirect path property and configure a path , page should be redirected to corresponding page but it's not happening in my custom template and even on reference site.

    Regards

    Ankur

      A
      ankurk67503819Author
      Level 4
      November 11, 2016

      start AEM: java -jar cq-quickstart-6.2.0.jar -r publish -p 4503

       

      then this redirection works for me: localhost:4503/content/geometrixx-outdoors.html


      Feike Visser wrote...

      start AEM: java -jar cq-quickstart-6.2.0.jar -r publish -p 4503

       

      then this redirection works for me: localhost:4503/content/geometrixx-outdoors.html

       

      Hi Fieke,

      Please try on  atemplate which inherits wcm/foundation/components/page and not foundation/components/page.

      As it works on foundation/components/page.

      Thats why its working on geometrixx outdoors and not on we -retail.

      Regards

      Ankur

        M
        maximg79918503
        January 30, 2018

        So any outcome? Is this going be fixed in any of the CFPs? or in AEM 6.3, 6.4?

        A client was asking about this functionality and I had to tell them Adobe is aware that this is an issue and is working on it.

          Terms & ConditionsAccessibility statement

          Loading footer...