Expand my Community achievements bar.

Dive into Adobe Summit 2024! Explore curated list of AEM sessions & labs, register, connect with experts, ask questions, engage, and share insights. Don't miss the excitement.
SOLVED

AEM6.0, SP1: Favicon not showing up properly when using vault

Avatar

Former Community Member

We are experiencing a weird issue around a website's favicon. It's located under /etc/designs/abc/clientlib/favicon.ico. On the local system the file is OK, not corrupted and shows up just the way it should. When build to the AEM instance though, it seems to become scrambled/corrupted:

[img]Screen Shot 2014-10-16 at 1.26.16 PM.png[/img]

There's no errors when building. We are using the latest AEM 6.0 with SP1 installed. This happens with all .ico files that I tried. Other images in the clientlib folder are fine. Any idea what this could be?

1 Accepted Solution

Avatar

Correct answer by
Level 10
  • Is the image path of favicon is correct?   If not verify the header component and probabily change to use from dam rather than clientlib.  OR
  • If you want to grap  favicon from the webserver instead of aem change veriy the Maven build - "filtering" property value for resource.

View solution in original post

2 Replies

Avatar

Correct answer by
Level 10
  • Is the image path of favicon is correct?   If not verify the header component and probabily change to use from dam rather than clientlib.  OR
  • If you want to grap  favicon from the webserver instead of aem change veriy the Maven build - "filtering" property value for resource.

Avatar

Former Community Member

Yes, the path is correct, otherwise it wouldn't show an image at all I believe. I figured it's a design element, not a content element so it should be in a clientlib. I tried it with a DAM asset which works fine, but that's not ideal I think. I'm just suprised it doesn't seem to work for .ico files but all other layout images we pull in from the clientlib folder (jpg, png, etc.) work just fine. It just seems to mess with the .ico files.

I realize there's plenty of work arounds but they don't really make it manageable in our build.