AEM not displaying png's | Community
Skip to main content
S
sdoyle_FoxRentACar
September 21, 2022
Solved

AEM not displaying png's

  • September 21, 2022
  • 1 reply
  • 2060 views

We have an instance of AEM that, seemingly randomly, stopped displaying new png's loaded into the system. Old png's appear fine, but when uploading new png's, only the default document icon appears. These images will not appear on the published site either. We've tried different versions of these files and saving in various png formats, but no change. Jpg's display fine... in fact, we can manually change each png file extension to jpg and it will display. This happened once before about a year ago and it seemed to fix itself without any real intervention. Any thoughts on this?

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 digarg17
  • Can you recheck dam update asset workflow - "Process Thumbnail step" and check if it has been modified/updated? It has options to skip few mimetypes. See reference pics.
  • Also check metadata property esp . fileType dc:format or mimetype property getting stored in crxde after asset upload and compare it with old png assets metadata property. Do you see any difference?
  • Check dam:failedrendition node in crxde.
  • Is the metadata property showing assets as processed - check dam:assetState property I think under jcr:content node ? If these are unprocessed, you could try rerunning the dam update asset workflow and see if it works.

/conf/global/settings/workflow/models/dam/update_asset.html

1 reply

D
Adobe Employee
digarg17Adobe EmployeeAccepted solution
Adobe Employee
September 22, 2022
  • Can you recheck dam update asset workflow - "Process Thumbnail step" and check if it has been modified/updated? It has options to skip few mimetypes. See reference pics.
  • Also check metadata property esp . fileType dc:format or mimetype property getting stored in crxde after asset upload and compare it with old png assets metadata property. Do you see any difference?
  • Check dam:failedrendition node in crxde.
  • Is the metadata property showing assets as processed - check dam:assetState property I think under jcr:content node ? If these are unprocessed, you could try rerunning the dam update asset workflow and see if it works.

/conf/global/settings/workflow/models/dam/update_asset.html

    Terms & ConditionsAccessibility statement

    Loading footer...