SVG icon not visible in AEMaaCS publish environment. | Adobe Higher Education
Skip to main content
K
KarthickVe
Level 4
September 12, 2023
Répondu

SVG icon not visible in AEMaaCS publish environment.

svg icon not visible in AEMaaCS publish environment but in author it works fine.

 

is there any specific configuration need to be allowed?

Ce sujet a été fermé aux réponses.
Meilleure réponse par arunpatidar

This is an apps path which is blocked in publishers(by dispatcher as well as publish permission)

You have to create a proxy cleintlibs here to fix this. 

 

/apps/settings/wcm/tatar/test/clientlib-site/css/resources/icons/default.svg

 

6 commentaires

A_H_M_Imrul
Community Advisor
A_H_M_ImrulCommunity Advisor
Community Advisor
September 12, 2023

Hello @karthickve,

 

Looks like a permission issue. Make sure you have read permission (on the asset) for anonymous user on publish instance.

 

Thanks   

    sherinregi-1
    Community Advisor
    sherinregi-1Community Advisor
    Community Advisor
    September 12, 2023

    Hi @karthickve 

     

    Are you getting broken images or its not at all loading . If its not due to permission you can look for the below post also could be due to some minifications or js/css issues.

     

    https://github.com/adobe/aem-core-cif-components/issues/63

     

     

      K
      KarthickVeAuteur
      Level 4
      September 12, 2023

      Hi @sherinregi-1 , Its not at all loading and i could see other images which are authored loading, only svg icons are not loading.

      I had also check before minified version there also same issue 

        A_H_M_Imrul
        Community Advisor
        A_H_M_ImrulCommunity Advisor
        Community Advisor
        September 12, 2023

        Hello @karthickve,

         

        I assume the svg icons are loading from code (not authored), in such case check the following

        - make sure the folder name the icon is loading from is resources and the folder has a .content.xml in it

        - with jcr:primaryType="cq:ClientLibraryFolder"

        - with allowProxy="{Boolean}true"

        - etc Node has read permission for anonymous user (on publish server)

         

        Let me know if that helps..

         

         

         

         

          arunpatidar
          Community Advisor
          arunpatidarCommunity Advisor
          Community Advisor
          September 12, 2023

          Could you please share the path of SVG which is not loading in publishers?

          Arun Patidar
            K
            KarthickVeAuteur
            Level 4
            September 13, 2023

            @arunpatidar @aanchal-sikka , The svg icon are loading in publish instance when we author form dam folder but not from DataSource dropdown list which is populated from servlet.

            screenshot:

             

             

            observations 1: When we author svg icon from dam folder and try to publish its listing as asset were we can see the svg icon.

            Observation 2: When we author from DataSource dropdown list which is populated from servlet and try to publish its listing as asset where we can't see svg icon asset in list.

            Note: currently migrating AEM on premise to cloud.

              arunpatidar
              Community Advisor
              arunpatidarCommunity Advisor
              Community Advisor
              September 13, 2023

              Hi @karthickve 
              Are you referring to the reference search?

              Can you try publishing assets separately that was populating using datasource?

               

              Also can you share the paths of the assets which are used in the page via dropdown, just to make user the paths also correct.

              Arun Patidar
                Mahedi_Sabuj
                Community Advisor
                Mahedi_SabujCommunity Advisor
                Community Advisor
                September 12, 2023

                To troubleshoot the issue, You can review the following steps:

                1. Permissions: Ensure that the SVG images have the read permission to the anonymous user. You can validate this by logging in as an admin user. If it's a permission problem, SVG images should load correctly for the admin.

                2. Content Replication: Verify that the SVG images are being replicated to the publish environment correctly. Again, you can inspect Asset folder while logged in as an admin user.

                3. Dispatcher Configuration: If you are checking using Dispatcher, ensure that SVG images aren't blocked by any filter rules. You can verify by checking dispatcher.log file.

                 

                Mahedi Sabuj
                  aanchal-sikka
                  Community Advisor
                  aanchal-sikkaCommunity Advisor
                  Community Advisor
                  September 13, 2023

                  Hello @karthickve 

                   

                  I guess you would be accessing the pages via publish dispatcher.

                  Please try following:

                  • Try accessing SVG via its DAM URL on publish/dispatcher
                    • If its accessible means image is available on publish
                  • Please check for any rewrite rules, which might be affecting SVG files.
                    • Verify dispatcher logs for any rules blocking SVG
                    • Verify publish logs, if the request is reaching there. And whats the URL of the SVG

                  Regards,

                  Aanchal

                  Aanchal Sikka
                    kautuk_sahni
                    Community Manager
                    kautuk_sahniCommunity Manager
                    Community Manager
                    September 14, 2023

                    @karthickve Do you find the suggestions from users useful? Please let us know if more information is required. Otherwise, please mark the answer as correct for posterity. 

                    Kautuk Sahni
                    K
                    KarthickVeAuteur
                    Level 4
                    September 15, 2023

                    @kautuk_sahni Yes, it was very helpful. Thank you all for your support.

                      Conditions d'utilisationAccessibility statement

                      Loading footer...