Snapsis Menu problem

I'm using the CSSNavMenu to setup a menu whereby the root menu items will be images and the submenus as normal. According to the documentation I read so far, this can be achieved by setting the HideTabNamesByLevel = "0-0", DisplayIcon = "True". But this makes the submenus unreadible, i.e. I cannot see any page names on he submenus. I can still navigate the submenus but I don't see any text on the submenu items.

Any idea why this is happening, I'm using a version that was posted on the forums but would like to buy the product if this issue is resolved.

Thanks

John,

I'm using NavType = "Hover". I don't understand what you mean by the text being in the html. The text I'm referring to is the submenus which is derived from the child page names. The submenu is displayed on hover but it's not readable. I hope I'm clear. Following is the skin.css code: I've just modified the default hrizontalhover skin that comes with the product.

I just went back and looked at the code and that property "HideTabNamesByLevel" is only used with the NavType="Tabs"

If you want to do that with a hover/flyout menu then you'll need to use a template type menu.

There is a suckerfish template example that you can use and it's very easy to remove the {Tab.Name} token from the root level and replace it with the {Tab.IconFile} token.

I tried using the template, instead of displaying the image, the filename of the image is displayed when replacing Tab.Name with Tab.IconFile.

You'll need to wrap it in an image tag.  The token is just a replacement for the src part of the image.

Something like this:

< img  src="{Tab.IconFle}" alt="{Tab.Name}" title="{Tab.Description}" />

That is just an example, you can use any markup you want.

Thanks, got that working. Funny though that I got the skin working on my local host installation but when installing the skin on my live webserver the following error occurs:

String was not recognized as a valid DateTime . What does that mean.

That sounds unrelated, unless maybe it was the demo version that you were using and something was wrong with the dates I used in your environment.

John,

The error does not occur with the version I bought. Thanks for your support.