Last post Jan 16, 2006 05:43 PM by jhenning
Jan 03, 2006 10:23 PM|pcrel|LINK
Wonder if anyone else has run into this yet - surely they have! Here's an example:
In a 3.0.13 portal, I have a skin which specifies Parent items in the skin object:
rootmenuitemcssclass="MainMenu_ParentItem" rootmenuitemactivecssclass="MainMenu_ParentSel" rootmenuitemselectedcssclass="MainMenu_ParentHover"
Then, of course, in the stylesheet, these styles are defined. Works great in 3.0.13 and previous versions - even 2.x...
In DNN 3.1 + versions, when a child item is Active (selected), the Parent Item reverts to the MainMenu_MenuItem class instead of the stated MainMenu_ParentItem stated in the .ascx file.
I can't find any documentation why this has changed and therefore assuming that either 1) It's a bug, or 2) I'm smoking crack...
BTW, the same exact skin is being used in both (actually every version from 3.0.13 to 3.22) with the same exact code. Has anyone heard of this being addressed or know a workaround?
Jan 04, 2006 08:10 PM|jhenning|LINK
Jan 14, 2006 05:25 PM|pcrel|LINK
Hi John... I apologize for this being so late...
Here's a good example:
I can sure email the skin as well...
Jan 16, 2006 05:43 PM|jhenning|LINK