I'm sure this must be a known problem, but search did not yield any helpful results.

Icons in DNN 5 skins display fine on local server but not on production server.

To solve this problem, is it necessary to do a clean install of DNN 5 on the production server rather than moving from the local server?

Or alternatively, is it related to the source paths for the skins in the SkinSrc column of the dnn_Skins table?

Is there a way to fix the problem manually? Or do the skin packages need to be re-installed? If so, are the DNN 5 default skins MinimalExtropy available as a separate package?

You're right. I'm sure it's a path problem. That's why I was asking about SkinSrc in dnn_Skins table, etc...

And yes I did attempt to copy from development to production servers. Apparently that's a "no no".

But I was hoping to avoid re-doing a new installation. Is there any forum post or FAQ on DNN 5 skins that explains the different places in the code and/or database that control how the path for skin icons is managed?

The problem is that the skins themselves are displayed but not the skin icons, especially the DNN icons for the DNN *.ascx controls used by all skins....

Timo,

Thanks for checking in here on this matter. I did some more work to track down the problem, and posted what I learned as a Gemini issue.

Please see http://support.dotnetnuke.com/issue/ViewIssue.aspx?id=9327&PROJID=23 for details. If you have any questions, I'll answer with more comments in reply on the Gemini issue.

CT