2 stk Jul 02, 2006 16:54
![](https://forums.b2evolution.net/media/users/stk/profile_pictures/.evocache/672979622420dae8d0001f.jpg/crop-top-80x80.jpg?mtime=1372015408)
Ahh...shit...
I tried that but I had the a.topmenutitle class backwards (I set it as .topmenutitle a or something) I'll have to try your way today and see if it works. If so, I'll have to go in and find all of the places where I added the class to the links in b2's files, then re-export my posts table and remove the class from that. I added it all in last night 8|
I'll give it a try - thx!
Yep (@ backwards class) :(
Don't sweat the extra class. There's no harm in having a class that isn't used. ;) (Other than just the extra characters it takes up)
Just plug in the code and you're good to go, no other changes necessary. I've already tested the code in FFox ... it works. ;)
BTW ... nice blog integration.
Update - your solution worked perfectly! Thx.
stk wrote:
BTW ... nice blog integration.
Thank you. This is V4 of our web site. B)
No sweat! Thanks for coming back to say so.
Gee, v4 ... ours is still on V1 :| ... we're definitely behind the times (or behind big? ... or maybe just a big behind?) :lol:
I'd recommend setting the generic links for your page/blog FIRST, then add the special ones for the navigation (and whatever else) AFTER that.
I played with it a tad and came up with the following, which *I think* will get you to the same point, but NOW all your regular blog/page links don't need any special class names. :D
Key Changes: (1) keep the generic link CSS FIRST, with any special link styling after that. (2) "topmenutitle is the class name for the anchor element, so your ".topmenutitle a" selector wasn't doing what you thought, as it should be "a.topmenutitle", instead. ;) (3) No longer a need for a special class for page/blog links (deleted a.three selectors) :D
Hope this helps.