Exprience fragment not loading images once published | Community
Skip to main content
MauG
MauG
Level 2
October 7, 2024
Solved

Exprience fragment not loading images once published

  • October 7, 2024
  • 2 replies
  • 1170 views

Hi all,

I'm creating a target experience fragment in AEM and publishing in Adobe Target. Text and icons are loading properly and quickly, however, the image is not loading until I zoom in/zoom out the page or inspect the image.

Any clue about why this is happening will be much appreciated.

 

Thanks!

 

 

 

    Best answer by MauG

    I found out there was a missing HTML code line that when added manually to the experiece, the image loaded corrrectly. I asked the IT team to look closely to this.

     

    Mau.

     

    2 replies

    pradnya_balvir
    Community Advisor
    pradnya_balvirCommunity Advisor
    Community Advisor
    October 7, 2024

    Hi @maug ,

    Exporting an Experience Fragment to Adobe Target you need to check below.

    For media assets, such as images, only a reference is exported to Target. The asset itself remains stored in AEM Assets and is delivered from the AEM publish instance.
    Due to this, the Experience Fragment, with all related assets, must be published before exporting to Target.
    Can you please check this from your end.
      Gokul_Agiwal
      Community Advisor
      Gokul_AgiwalCommunity Advisor
      Community Advisor
      October 7, 2024

      Hi @maug 

      Yes, I had faced the same issue last month, in my case it was an issues with scene7 URL and the image not published through assets. once published able to see the experience fragment with image content.  

      For troubleshooting - inspect the image location in your browser and see from which path the image content coming on the page. If you're using AEM and DAM environment then you can access the location else speak with your team member who has AEM or DAM access. 

      Hope this helps. 

        MauG
        MauGAuthorAccepted solution
        Level 2
        October 24, 2024

        I found out there was a missing HTML code line that when added manually to the experiece, the image loaded corrrectly. I asked the IT team to look closely to this.

         

        Mau.

         

          Terms & ConditionsAccessibility statement

          Loading footer...