Skip to main content
M
mahim007
New Participant
October 14, 2022

Authoring Issue - Parsys can not be selected inside Tab Component

  • October 14, 2022
  • 3 replies
  • 1955 views

[UPDATE 1] - In we-retail project, I was authoring a Tab component. Inside the Tab component I added multiple Image components, Teaser component etc.
When an actual image is dragged into the Image component, the parsys became un-clickable. After some random try, I was able to click the component but the inline editor tools (edit, children-selector, copy, paste, parent etc) were not appearing.
I am attaching a video link for better understanding : https://www.loom.com/share/8488882368d6403bbf486f340b9b8a10

 

[UPDATE 2] - while investigating the previous issue, found some some glitches which may be related. The overlay for the 2nd image component somehow duplicated and copied to the top-left corner and remain invisible. And preventing selecting other component's parsys (preventing any click).

Attaching 2nd video link : https://www.loom.com/share/547d13c3147a4865bd796b1beaf10587

 

I am using the non-cloud version of AEM.
AEM version number : 6.5.14
We.Retail version : 4.0.0 (we.retail.all-4.0.0.zip)

Can anyone provide some feedback on how to resolve this issue?
Thanks in advance.

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

    3 replies

    Sady_Rifat
    Sady_Rifat
    New Participant
    October 17, 2022

    I also faced the same issue. In my case, it was not fixed by page refreshing. And it's not related to the we-retail and my local project. I found this in the core-components-library demo section also.
    My Steps:
    1. Add Tab/Carousel component
    2. Add Image component in every container. Probably after adding image in 2nd container the issue will be generated.
    Steps recording: https://www.loom.com/share/807092951323465ea48b6bd5e89d4c28

    There is an overlay of the 2nd container image. In that particular area, I was unable to edit any other component. I added a screenshot below.

      M
      mahim007Author
      New Participant
      October 17, 2022

      hi @sady_rifat 

      yours and mine is the same issue i guess.

        Aditya_Chabuku
        Aditya_Chabuku
        New Participant
        October 14, 2022

        Hi @mahim007 ,

        I tried with the same specs you mentioned above and saw your video. It's working completely fine for me. 

        Try to implement in any project other than we-retail, if you have access to cloud sandbox try there as well.

        Did you have any console errors or any error logs? check them as well.

         

        Regards,
        Aditya.Ch

        Thanks,Aditya Chabuku
          M
          mahim007Author
          New Participant
          October 17, 2022

          hi @aditya_chabuku ,

          I tried with other project first, then came to we-retail.

          Unfortunately, I do not have access to cloud sandbox.

          No error in the console.

            M
            malay_dube
            Employee
            October 14, 2022

            Hi @mahim007 
            Have you added cq:iscontainer value as true? If not please add and give a try.

              M
              mahim007Author
              New Participant
              October 14, 2022

              Hello @malay_dube ,
              Thank you very much for the quick response.

              cq:iscontainer value as true - it is already set in the Tabs component's property (In Core Component)



              It is automatically fixed when the page is reloaded.

                M
                malay_dube
                Employee
                October 17, 2022

                Hi @mahim007 ,
                I can see one clientLib in that particular component hierarchy, can you disable the clientlib and give a try ?

                I tried the same in my local and it's working fine for me.   

                  Terms & ConditionsAccessibility statement

                  Loading footer...