Parsys is not working in AEM cloud | Community
Skip to main content
P
pradeepdubey82
Level 5
July 4, 2023

Parsys is not working in AEM cloud

  • July 4, 2023
  • 3 replies
  • 1497 views

Hi Folks,

 

I am using AEM cloud with latest June SDK. Parsys/container is not working in cloud, the moment I am clicking the container to add components in it, it is showing one small radio button sort of thing just above the parsys area in right side of the page.

Attached image for you guys reference.

 

Same code/content/policies etc is working fine in local cloud SDK with same version.

 

Any pointers to solve this highly appreciated.

 

Thanks,

Pradeep

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

3 replies

Rohit_Utreja
Community Advisor
Rohit_UtrejaCommunity Advisor
Community Advisor
July 4, 2023

@pradeepdubey82 

 

Can you please check and share logs while performing this activity?

    aanchal-sikka
    Community Advisor
    aanchal-sikkaCommunity Advisor
    Community Advisor
    July 4, 2023

    Hello @pradeepdubey82 

     

    - Are we talking about the old parsys (Static templates) or the Container (WCM core components)?

    - Is it an issue with all users?

    - Has there been any customization done?

    - Any errors in browser console?

    Aanchal Sikka
      P
      pradeepdubey82Author
      Level 5
      July 4, 2023

      Hi Aanchal

       

      This is WCM core component, my container component has super type

      core/wcm/components/container/v1/container

      I have not customized anything in container component. No container related errors on console or in log file.

      Yes this issue is there for all the users in AEM cloud.

       

      Thanks,

      Pradeep

        aanchal-sikka
        Community Advisor
        aanchal-sikkaCommunity Advisor
        Community Advisor
        July 4, 2023

        @pradeepdubey82 

         

        Container is used by majority of the customers. Any errors should have been reported by now.

         

        Also, you mentioned that no customizations have been done.

         

        Can you please try Invalidating cache and rebuilding libraries? After that, please try accessing in incognito mode via different browsers

        http://localhost:4502/libs/granite/ui/content/dumplibs.rebuild.html?rebuild=true 

        Aanchal Sikka
          Tanika02
          Tanika02
          Level 7
          July 5, 2023

          Hello @pradeepdubey82 - 

           

          • Verify that the allowed components are defined correctly and that the necessary policies are applied.
          • Double check for any error messages or warnings related to the Parsys/container component.

           

          Also, are you facing this issue across all environments?

            P
            pradeepdubey82Author
            Level 5
            July 11, 2023

            Hi Folks,

             

            Finally it is fixed. 

            Below is the resolution. It looks weird how parsys is linked to resource resolver configuration file.

             

            This issue is fixed after removing /content/test-project/:/ from resource resolver factory config file in author service.

             

            Thanks you all for looking into it.

             

            Cheers,

            Pradeep

              Terms & ConditionsAccessibility statement

              Loading footer...