Skip to main content
Mohammed-Skouti
Level 3
November 20, 2023
Solved

I can't reach the child component on form

Hello!

I can't reach the child component on form on author 

By clicking on them 

I should click on them using Content tree

What's wrong

And how to solve this 

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Mohammed-SkoutiAccepted solution
Level 3
November 23, 2023

It was about css on other component which was hidden the cq overlay 

View in thread

9 replies

A_H_M_Imrul
Community Advisor
A_H_M_ImrulCommunity Advisor
Community Advisor
November 20, 2023

@mohammed-skouti 

Probably the child resource is getting overlapped with others. You have to get hold of it from the content tree (until you fix it). 

Or you can put a placeholders (such as a label) and make sure to write the logic to make it visible in the edit/author mode.

 

 

Translate
    Mohammed-SkoutiAuthor
    Level 3
    November 20, 2023

    @a_h_m_imrul when i chang the panel layout to anything else than Responsive -everything on one page without navigation it works

    But i still can't add a component from the page without using Content tree 

    Translate
      partyush
      Community Advisor
      partyushCommunity Advisor
      Community Advisor
      November 20, 2023

      Hi @mohammed-skouti 

       

      Can you please share the screenshot of your issue, Like where you facing such type of issue. 

       

      Thanks

      Translate
        Mohammed-SkoutiAuthor
        Level 3
        November 20, 2023

        @partyush 

        Translate
          Mohammed-SkoutiAuthor
          Level 3
          November 20, 2023

          When I deleted the resource super type  for guideFragmentContainer 

          It somehow works but its not showing right

          So something on this core component caused this

          Any idea

          @partyush @a_h_m_imrul 

          Translate
            Mohammed-SkoutiAuthor
            Level 3
            November 21, 2023

            After all I still have the issue about the editor still looked

             

            Translate
              Mohammed-SkoutiAuthor
              Level 3
              November 22, 2023

              @aanchalsikka do you have any idea?

              @aanchal-sikka 

              Translate
                kautuk_sahni
                Adobe Employee
                kautuk_sahniAdobe Employee
                Adobe Employee
                November 23, 2023

                @mohammed-skouti 

                The issue you're experiencing with the child component on the form in Adobe AEM seems to be related to the interaction between the guideFragmentContainer component and the Responsive panel layout. When you use the Responsive panel layout, the child component becomes inaccessible by clicking on it and can only be accessed through the Content tree. This behavior is likely due to the way the Responsive layout manages components and their interactions.

                Deleting the resource super type for guideFragmentContainer might have temporarily resolved the issue by altering the component's behavior within the Responsive layout. However, this is not a recommended solution as it could lead to unintended consequences and potential compatibility issues.

                 

                To address this issue effectively, consider the following approaches:

                1. Utilize a different panel layout: As you mentioned, switching to a non-Responsive panel layout, such as Basic or Flow, resolves the issue with accessing the child component. This could be a suitable option if you don't require the Responsive layout for the form.

                2. Investigate component configurations: Check the configurations of the guideFragmentContainer component and its child components to ensure they are properly configured for interaction within the Responsive layout. Look for any settings that might be restricting access to the child components.

                3. Custom CSS adjustments: If necessary, you could explore using custom CSS to override the default behavior of the Responsive layout and allow access to the child components. This approach requires caution and a thorough understanding of CSS and AEM component rendering.

                Remember, modifying core components or their super types can introduce compatibility issues and should be considered as a last resort. Prioritize using supported configurations and layouts whenever possible.

                Translate
                Kautuk Sahni
                Mohammed-SkoutiAuthorAccepted solution
                Level 3
                November 23, 2023

                It was about css on other component which was hidden the cq overlay 

                Translate
                  Terms & ConditionsAccessibility statement

                  Loading footer...