I just had a thought....

What implications would there be if you created your pages for the menu, assigned an icon to each page, and then went into the database to remove the page name from the Tabs Tab name column?

When you create the page, it will force you to have a tab name, so I put one in, assigned the aspnet.gif icon to it and placed on the menu. Then went into the DB and removed the Tab Name from the Tabs table. Went back into the portal and the image was visible. I tried this on a local install and it worked as expected. My Sol Menu css is setup to display the arrow, so it displayed that. adjusting the css to hide the arrow would be the only thing left for me to do to hjave a image driven menu.

Am I mising something here, or is it just that easy?

It's not the title that it removing. (if I understand correctly), but the tab name. It doesn't remove the page title.

Here's the results of the change on the local machine. The test page still has a title, keywords, and all the meta tags.

<meta id="MetaDescription" name="DESCRIPTION" content="Test"><meta id="MetaKeywords" name="KEYWORDS" content="Test,DotNetNuke,DNN"><meta id="MetaCopyright" name="COPYRIGHT" content="Copyright 2006 by My Website"><meta id="MetaGenerator" name="GENERATOR" content="DotNetNuke 4.3.4"><meta id="MetaAuthor" name="AUTHOR" content="My Website"><meta name="RESOURCE-TYPE" content="DOCUMENT"><meta name="DISTRIBUTION" content="GLOBAL"><meta name="ROBOTS" content="INDEX, FOLLOW"><meta name="REVISIT-AFTER" content="1 DAYS"><meta name="RATING" content="GENERAL"><meta http-equiv="PAGE-ENTER" content="RevealTrans(Duration=0,Transition=1)"><style id="StylePlaceholder"></style><link id="_dnn_Portals__default_" rel="stylesheet" type="text/css" href="/dnn/Portals/_default/default.css" /><link id="_dnn_Portals__default_Skins_DNN_Blue_" rel="stylesheet" type="text/css" href="/dnn/Portals/_default/Skins/DNN-Blue/skin.css" /><link id="_dnn_Portals__default_Containers_DNN_Blue_" rel="stylesheet" type="text/css" href="/dnn/Portals/_default/Containers/DNN-Blue/container.css" /><link id="_dnn_Portals_0_" rel="stylesheet" type="text/css" href="/dnn/Portals/0/portal.css" /><title>
 Test
</title></head>

Hi jballhrb,

I had the same issue as you. After several hours of trying to make the SolPartMenu work, I decided to create my own Skin Object using the ASP.NET Menu control (built in to ASP.NET 2.0).

This control is way easier to use than the DNN built in. Also there is good documentation on the web. With a little engenuity, you can make it work.

Check out the last example on this page (graphic fly out menu):

http://msconline.maconstate.edu//tutorials/ASPNET20/ASPNET12/aspnet12-02.aspx

Here is a good example of how to make a skin object:

http://www.wwwcoder.com/tabid/68/type/art/parentid/224/site/6373/default.aspx

You can connect to the db (Tabs table) and write a script to get the children of each parent, and dynamicaly add menu items.

Like everything DNN, I find the API super complex and never acounts for obvious issues (like this one!). Good thing you can build from scratch....

J