Support Forum
No problem! Was it not yourself I spoke with the other day in the other thread?
Yes you should be able to use the CSS editor for this, just make sure you include the closing bracket as you've missed it off there, not sure if that's just a result of copy and paste though..
#spMainContainer a.spButton { color: #4C5D77 !important; }
Then does it all work OK?
No problem, glad it all works!..
Like I said though, make sure your rule has a closing brace ' } ' at the end - as it does in the CSS I posted (on line 3 of the code block). Twice what you've posted hasn't, but like I said not sure if that's a result of you copying and pasting it from your custom CSS box.
If it doesn't have a closing brace, anything you add after it will be invalid.
Sorry after closer inspection it seems that rule is having an impact all over the forum and it's going to be far too much trouble changing each individual rule to compensate for the themes irresponsible override. I did receive your PM but it would be way too much work for me to put right in the forum theme itself and adding something to the CSS box is pretty easy.. So you have two choices as far as I can see.
1. Contact the theme developer and ask them the best route to get rid of the !important rule on the a tag. This might involve making a child theme or the theme may come with a CSS override box of it's own which you can put some custom CSS In place to prevent it.
2. Create a universal a and a hover rule for the forum which may or may not work, but it might be worth a shot. The downside to this is that every link would end up being the same colour and hover colour but it might just get around the themes awful use of CSS. So for this, can you try adding the following to the custom CSS box.
#spMainContainer a { color: #4C5D77 !important; } #spMainContainer a:hover { color: #8EA0BD !important; }
Fingers crossed that should do the trick, and of course you can change those colours to whatever you'd like using something like ColorPicker to select your hex values.
If you'd rather contact the theme developer, you can reference this huge block of code that stamps all over every other use of the a tag, and ask them exactly why they felt the need to use !important.
body.dark-skin a:hover, body.dark-skin p.post-meta a:hover, body.dark-skin .author-comment cite, body.dark-skin .post-title, body.dark-skin #tabbed-widget ul.tabs li.active a, body.dark-skin textarea:focus, body.dark-skin input[type="text"]:focus, body.dark-skin input[type="password"]:focus, body.dark-skin input[type="email"]:focus, body.dark-skin input[type="url"]:focus, body.dark-skin input[type="tel"]:focus, body.dark-skin input[type="number"]:focus, body.dark-skin input[type="date"]:focus, body.dark-skin input[type="file"]:focus, body.dark-skin input[type="search"]:focus, body.dark-skin input[type="color"]:focus, body.dark-skin input[type="datetime"]:focus, body.dark-skin input[type="datetime-local"]:focus, body.dark-skin input[type="month"]:focus, body.dark-skin input[type="range"]:focus, body.dark-skin input[type="time"]:focus, body.dark-skin input[type="week"]:focus, body.dark-skin select:focus, body.dark-skin .top-nav ul li a:hover, body.dark-skin .top-nav ul li:hover > a, body.dark-skin .top-nav ul:hover > a, body.dark-skin .top-nav ul li.current-menu-item a, body.dark-skin .top-nav ul ul li a:hover, body.dark-skin .top-nav ul ul li:hover > a, body.dark-skin .top-nav ul ul:hover > a, body.dark-skin .top-nav ul ul li.current-menu-item a, body.dark-skin .cat-tabs-header li.active a, body.dark-skin a.more-link, body.dark-skin .page-title { color: #FFF !important; }
1 Guest(s)