I have been trying to style the TreeMenu to look much nicer than the default skins.

I had a look at the new documentations and it seems that I can do much more now. However, I am finding difficulty in the Images

At first I thought it is going to be a piece of cake and for example in my skin i did skin.xml

< Setting >
< Name>NodeClosedImage< /Name>
< Value>Tree_NodeClosedImage< /Value>
< /Setting>

which has the associated to skin.css

.Tree_NodeClosedImage{ background-image:url(Images/folderclosed.gif); background-repeat:no-repeat;}


However the control is still pointing to

http://localhost/DNN43/Admin/Skins/Tree_NodeExpandImage

Which is not good

< Value>< ![CDATA[ in Skin.xml, instead of the class did not work either


So I assume the images are hard coded to theAdmin/Skins/ folder so the value of the NodeCloseImage has to be directly the gif associated with it in the admin/ skin folder.

This is ok if there is only one DNN per install so one puts all the necessary images in there. But ideally one should be able to put it in the skin folder.

Any Ideas is very much appreciated. May be I have missed something.

Salar

---

I mentioned in the other thread that the treeview skin object uses ResolveUrl, when it comes to these images.  This is the way it was originally coded, and the way it is today.   The only new feature added here was the ability to specify a different file name for these images.  Why it was coded this way I don't know, before my time on the project (skinning portions). 

Do I agree with the way it was coded? no. 

Why did I not change it when I went through the skinning cleanup? Mainly due to backwards compatibility concerns.  But also, there was so many changes I made at that time, this was not one that I knew about, and even if I did I probably would not have had time to.

Since an absolute url (those that are prefixed with / or ~/) are ignored by ResolveUrl, this appears to be the fix.  If there is some token that the skinning engine picks up that gives the skin path, then I would assume this would resolve your issue (you may need to prefix it with a / or ~/...   

---