I imagine HouseMenu would work for the container's action menu, but I have never tried it. You can try by just using the HOUSEMENU token on a container skin with the appropriate settings declared in the xml file and see what happens. If I get the chance, I'll try it and report back here, but it may be a few days.

Has anyone else tried this?

Tim

Thanks, I'll try it out.

UPDATE:

I tried this and it just renders the page navigation menu in the container - not what I intended.

I realized what I'm actually looking for is a CSS-based replacement for the SOLPARTACTIONS menu. I'm pretty sure there's no way to do that with the HOUSEMENU as written. Is there any means to get a container's ACTIONS menu to render as a UL? -- So it can be nicely formatted in in CSS suckerfish style.

Thanks

I'll have to investigate this a bit more. I'll try to have something figured out over the weekend.

Tim

FYI, I have not been able to look into this yet, but it's still on my list!

I typically use the [dropdownactions] token instead of actions token for my container menus when building CSS based skins / containers. No its not pretty and yes you have to click on the "go" / arrow to make the function / selection work, but.... it does do it a bit more efficently. Renders in a dropdown box with list items being the selections. Now there is good news the next release of DNN 5.0+ which is soon to be released will have a new / redone menu which will be CSS based / offer a CSS based option of unordered lists. So might just have to suck it up for a month or two more. I shared your idea but as you quickly found the skin object appears to be purely written for navigation only, and is not bi-versitile like solpartmenu is.