I upgraded our site to DNN 5.6.1 and custom classes in my portal.css now have lower precedence than, say, a regular selector (a:link) from the portal.css or a:link from the skin or default stylesheets.  Using Firebug, I can see that the custom class is available, but much lower in precedence.  The css worked great in 5.0.4 before I upgraded to 5.6.1.

I've run the portal.css through W3C's stylesheet check and it shows no errors.

Any ideas on what I can do to regain control on my page with custom classes?

Could you post a link to the site and indicate what classes you are talking about?
(so we can have a look, as there were some changes to default.css)

---

I think I see it: the format for link in the default, a:link, has a stronger presence than just a.  Change default.css or redefine your style as a.CrossChildPageListLine

Timo, should we remove format this for future versions or remove the block altogether?