DAM Asset shown as broken in publish when published | Community
Skip to main content
P
pn_2007
Level 3
June 8, 2020
Solved

DAM Asset shown as broken in publish when published

  • June 8, 2020
  • 5 replies
  • 7222 views

I am facing a strange issue as below with DAM assets.

Have created a new DAM Folder in author and added some images. Tried publishing just one image from author.

Though replication logs say it is successful, when I open the DAM folder in Publish instance. I am seeing the image as broken as below:

Though it has been literally published, because I can see the file  and file name etc. The image is showing as broken image.

Another observation is that - I tried to inspect the broken image and could understand that it is referring to 1280*1280 rendition image. This rendition image is geeting downloaded in author instance, when we hit direct rendition image. But in publish direct rendition image is giving 404, though the physical rendition node 1280*1280 exist in JCR.

 

Can someone help me what I am missing here?

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

Thank you all for your valuable comments on this issue.

 

But the issue was at clouf front level. We had to add another beviour to pass the cookies from cludfront as that was a restrcited access folder.

5 replies

VeenaVikraman
Community Advisor
VeenaVikramanCommunity Advisor
Community Advisor
June 8, 2020

@pn_2007 Is this happening in your local ? can you check below 

  1. Did you check the asset in the publish instance ? Is the node created with jcr:data in the original ?
  2. If yes, can you click on the jcr:data and open that file and check if the image is opening for you . If not , your image might not have been published completely , or there might be some issue with your publish.
  3. Did you restart the instance and check publish again and see if it is working fine ?

 

Thanks

Veena

    P
    pn_2007Author
    Level 3
    June 8, 2020

    @ Veena_Vikram This is happeing in QA. I did check your points 1 and 2 and everything is there. BUt still image is showing as broken.

    arunpatidar
    Community Advisor
    arunpatidarCommunity Advisor
    Community Advisor
    June 8, 2020

    It seems assets renditions are not getting created. Check DAM update assets workflow.

    Compare the renditions at publishers.

     

    Are you able to see actual images on the page?

    Arun Patidar
    P
    pn_2007Author
    Level 3
    June 8, 2020
    No. Image is not rendering in the page neither. compared both publisher and in both I can see the rendition nodes. Compared them as well
    Harwinder-singh
    Community Advisor
    Harwinder-singhCommunity Advisor
    Community Advisor
    June 8, 2020

    @pn_2007   When you first uploaded the image on the Author, did you get any error in the DAM asset update workflow execution ? May be that is a good starting point to check if the workflow finished without any errors on the Author.

    Are you able to access the mentioned image rendition on the author?

      P
      pn_2007Author
      Level 3
      June 8, 2020
      Did not see any error while uploading in author and able to access image rendition in author
      khamat_bn
      khamat_bn
      Level 4
      June 10, 2020

      Hi @pn_2007 

      From the question and discussion, I got that problem is with a rendition of the image.

      1) Can you please look Dam update asset workflow.

      2) Also, you can cross-check that for other rendition image is replicating, able to see the image in page -by selecting mobile phones version instead of desktop.

      3) have you tried with other images, -though image size doesn't matter when you upload but just give a try.

      Mostly Focus on the workflow.

       

      let us know 🙂

        P
        pn_2007AuthorAccepted solution
        Level 3
        June 10, 2020

        Thank you all for your valuable comments on this issue.

         

        But the issue was at clouf front level. We had to add another beviour to pass the cookies from cludfront as that was a restrcited access folder.

        Terms & ConditionsAccessibility statement

        Loading footer...