[SOLVED] Formatting Userlist(s) - Component vs. Called in Content

I have multiple userlists on my site. The main / default one is fine - it formats as normal, and picks up all CSS from the Joomla template without issue:

template.knightrealms.com/forum/userlist.html

I have an Article (Content) that calls a series of smaller Userlists inside it, to display them as one extended page. For some reason, this is not picking up the formatting from the Joomla template, or rather, I think that CB's CSS is taking priority over Joomla's for just this scenario, for some reason:

template.knightrealms.com/main-menu/marshals.html

This wasn't always the case - I suspect this behavior started with an update, and I just noticed it now.

Is this a bug, or can something be done to change this and make the second setup apply the Joomla CSS template as priority?

Thank you!

CBs CSS and JS always loads after Joomlas (in all cases) and should be the case for every Joomla extension. Ensure your CSS selectors are strong enough to account for this. Your issue appears to be due to adding CB CSS overrides through your Joomla template, which may load before or after CBs headers depending on when CB is loaded into the buffer (in this case it's loaded late as Components Anywhere is loading CB and not Joomla directly). Try adding CB specific CSS overrides using CBs built in CSS override functionality as shown below.

www.joomlapolis.com/blog/kyle/18711-template-css-overrides-made-easy

Your alternative is to make your CSS selectors stronger. For example in your override code you've ".cb_template .cbUserListDiv.cbUserListLayoutList > .cbUserListRow:hover" to override the hover background color, but it's the exact same selector in CB so which is used comes down, entirely, to load order of the CSS files. If you increase its selector strength to ".cb_template.cbUsersList .cbUserListDiv.cbUserListLayoutList > .cbUserListRow:hover" it'll always override as it's has more weight.

Got it, thank you. This is an old, old site - back from the Joomla 1.0 days (!), and has evolved several times. The CSS is a legacy from before the current CB version, and needs to be migrated to its own template eventually. This just reinforces that need to do it properly.

Thank you for the clarity!

Apparently, it was the Components Anywhere plugin - an update just resolved this.

Thank you for the guidance!