When a Custom Skin is Added, Static File Publishing Errors Appear in log Caused by Digital Asset Manager (DAM) (Doc ID 1400296.1)

NOTE: There are multiple errors each time the static files are published. The static file publishing is looking for a <XXXXXX> directory inside the ECM HOME (Oracle_ECM1). This is never going to exist.

This has been tracked down to the dam_PublishedStaticFiles table inside <DOMAIN>\idc\components\DigitalAssetManager\resources\dam_publish.htm.

<@table dam_PublishedStaticFiles@>
<table border=1><caption><strong>
<tr>
<td>srcPath</td>
<td>path</td>
<td>class</td>
<td>loadOrder</td>
<td>doPublishScript</td>
<td>canDeleteDir</td>
</tr>
<tr>
<td>publish/all-layouts/@@LmLayoutSkinPairs.skin@@/base/dam/</td>
<td>@@LmLayoutSkinPairs.skinDir@@/@@LmSkinVariants@@/dam/</td>
<td>resource:layout:@@LmLayoutSkinPairs.layout@@</td>
<td>30</td>
<td><$doPublish = "@@LmLayoutSkinPairs.enabled@@"$></td>
<td>1</td>
</tr>

It is written to try and publish a copy of its static files to the skin folder for any skins registered with LmLayoutSkinPairs. the custom skin needs to be registered with LmLayoutSkinPairs to get the skin to function properly.

It is assumed that it is trying to publish its images to the skin folders so that new skins do not have to include a copy of the DAM images. It could be changed to publish its files to a directory for the skin in the weblyaout directory such as cs/resources/layouts/Top%20Menus/<Skin_name>/dam.