Timo, you mentioned that nothing has changed and asked that we post new threads to focus on individual problems.

The following link is to a VERY VERY basic skin I started to begin testing things. The CSS only includes 4 items body, search, .MainMenu_MenuItem, and .MainMenu_RootMenuItem.

http://www.sylvanglenhomeownersassociation.com/LinkClick.aspx?fileticket=AXUBR1hiHTY%3d&tabid=36

The skin.xml only defines that the search token should use the search css class.

In the past the .MainMenu_MenuItem class would control the root menu font and the submenu fonts. All you had to do was have that in the css file and it would work, you did not have to wire it up through the skin.xml.

Now, with this basic package, installed through the extensions page the root menu fonts are not picking up the .MainMenu_MenuItem. The submenus are though.

I added the .MainMenu_RootMenuItem class just to see if they had been split up in some way, but it doesn't look like that is what is happening.

Can you let me know if you see what's up?

Thanks,

John

So where does the Provider information get placed?  In the skin.xml or in the manifest file?

In the skin.xml file, i'll test the example skin later today and post my findings