Proxy component not appearing in Author instance components list | Community
Skip to main content
M
mrtestermanitest
New Participant
June 5, 2023

Proxy component not appearing in Author instance components list

  • June 5, 2023
  • 2 replies
  • 952 views

We have built a proxy component of the Tabs core component, it works fine locally.

However when we deploy a package to our Author environment the users are not able to see the new proxy component as an option in the left-hand side component list when authoring a page.

 

We have checked the page template policy includes the new proxy component.

We have checked the componentGroup name is correct.

 

Any advice thanks.

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

2 replies

ksh_ingole7
ksh_ingole7
New Participant
June 5, 2023

Hi @mrtestermanitest 

 

Please do the below checks :

1. See if the relevant code is deployed. Check if the component is present in CRXDE under /apps.

2. Cross check the componentGroup. 

3. On template level check if that componentGroup is allowed. If yes see if the other components from that group are visible in the left trail. 

4. Go to design mode on page and open the parent parsys and see if the component is in checked state. 

 

Let me know if all the above checks are done and the component is still not visible. 

    M
    mrtestermanitestAuthor
    New Participant
    June 5, 2023

    Hi ksh_ingole7

    Thanks for reply,

     

    1. See if the relevant code is deployed. Check if the component is present in CRXDE under /apps.

    • I will confirm, i don't have this access.

    2. Cross check the componentGroup. 

    • I will confirm in CRX/DE, i don't have this access.

    3. On template level check if that componentGroup is allowed. If yes see if the other components from that group are visible in the left trail. 

    • The componentGroup is allowed as various other components belonging to the group are available.

    4. Go to design mode on page and open the parent parsys and see if the component is in checked state. 

    • Not exactly sure what you mean but the page parent parsys does not give me the option to add our new component.

    Thanks

      aanchal-sikka
      aanchal-sikka
      New Participant
      June 5, 2023

      Hello @mrtestermanitest 

       

      1. Are you able to see the component listed in the Left component rail of the template ?

      2. Are you able to drag it in the relevant container on template?

      3. Have to tried creating a new page and check if the component is listed?

      4. If listed on new page, verity if the container where the component is added, is available in existing pages. If not locked, it might have been deleted

      5. Try add the component to the Root container and check if component is loaded. Its easy to get confused between the container and policy mappings, during check-ins

      6. Try to deploy the same code on another developer's system, are you able to replicate the issue? If yes, then some mapping between container and policy isn't correct.

      Aanchal Sikka
        M
        mrtestermanitestAuthor
        New Participant
        June 5, 2023

        Hi aanchal-sikka

        Thanks for the reply,

         

        1. Are you able to see the component listed in the Left component rail of the template ?

        • No cannot see the proxy component in the template editor.

        2. Are you able to drag it in the relevant container on template?

        • No as above, cant see it.

        3. Have to tried creating a new page and check if the component is listed?

        • Yes, new page created, our new component still not available.

        4. If listed on new page, verity if the container where the component is added, is available in existing pages. If not locked, it might have been deleted

        • As above, can't add component to new page.

        5. Try add the component to the Root container and check if component is loaded. Its easy to get confused between the container and policy mappings, during check-ins

        • The proxy component is actually visible in the "Allowed Components" area of the root template container.
        • However it does not appear in the left hand component list for template editor or page authoring.

        6. Try to deploy the same code on another developer's system, are you able to replicate the issue? If yes, then some mapping between container and policy isn't correct.

        • Will see and confirm.

        Thanks

          Terms & ConditionsAccessibility statement

          Loading footer...