TwelvestoneFront End

CSS-type question


Sign in

  • Waiting for Godot ( 720 k posts )
    Just conversation.
  • Thunder Dome ( 23 k posts )
    Photoshop Tennis and Collabs.
  • Photography ( 4.8 k posts )
    For all you shutterbugs, sh...
  • Flash ( 18 k posts )
    ActionScripting to tweens, ...
  • Front End ( 5.8 k posts )
    general front end design an...
  • Back End ( 9.6 k posts )
    serverside scripting, progr...
  • Projects and Theory ( 12 k posts )
    This forum is for discussio...
  • FAQ ( 269 posts )
    All those nagging questions...
  • Design ( 17 k posts )
    graphics & all aspects of g...
  • Purgatory ( 3.6 k posts )
    12stone Jail, feel free to ...
Candy Beard
 
2010-05-07

I'm over my head, as usual. I'm deploying a custom 'skin' to a pre-bought theme in WordPress.

One of the plug-ins the blog uses: slashdigglicious is behaving badly in the new theme.

It is not my skin that's borking it; the master theme is similarly borked.

the plug-in puts this guy at the bottom of every post. http://www.econsultant.com/images/wordpress-plugin-slashdigglicious.jpg

If you go here, you'll see it working: http://www.employeefactor.com/

If you go here, you'll see it not working: borkened.

It seems that slashdigg is picking up some extra formatting from the theme, somehow, that's rendering it vertical, rather than horizontal.

Chromes debugger shows it picking up formatting from .entry img (I think.)

Is there some way for me to figure out what's happening and over-ride it for slashdig in my new CSS file?

Danke.

Tha.Riddla
 
2010-05-07

Move your "slashdiggalicious" span outside the "clearfloat" div.

Candy Beard
 
2010-05-08

I'm not sure I can do that, as it's a farking WordPress plug-in.

I was hoping to maybe do some kind of formatting over-ride within my style sheet to get it to ignore whatever's effing it up. :shrug:

Jenn
 
2010-05-08

Did you take it down? I don't see the links.

Tha.Riddla
 
2010-05-08

I'll take a longer look at it on my laptop later today, but just off the top of my head, you could probably add one of these in your css:http://testblog.markclarkson.com/wp-content/themes/EmpFactor/style.css

totally untested and off the cuff

span.slashdiggalicious { clear: none; }

span.slashdiggalicious { display: inline; }

basically, you want to override either the float clearing properties or the block properties (or both) of the .clearfloat div that your .slashdiggalicious div is containted in...those definitions are in this file that you're importing: http://testblog.markclarkson.com/wp-content/themes/mimbopro/style.css

Candy Beard
 
2010-05-09

Thanks, guys. I did disable the plug-in temporarily so it wouldn't 'distract' the client. Riddla, that's the kind of thing I was hoping would work for me, so I'll give it a try, soonest.

Danke.

Candy Beard
 
2010-05-10

span.slashdigglicious is getting me nowhere. At least, as I've got it set up: span.slashdigglicious { display: inline; border:6px solid #f00; }

I added the border so I could see if anything at all was happening, and I don't even get the border. When I inspect the element, tho, Chrome and Firebug both insist that it _has _a red border. See "computed styles" at far right. http://markclarkson.com/Temp/noredborder.gif

I'm sure that it's my fault and I am stoopid, but I'm lost.

wowbagger[tip]
 
2010-05-10

The icon img's in the span are getting a display:block value from the .entry img{.. } declaration causing them to stop behaving inline. There's your problem.

Be aware that the .entry img{ .. } declaration appears twice in your stylesheet. k

A fix would be to add something like :

.slashdigglicious img { display:inline; margin:2px; }

You should also see the generous red border now, and remove it at your leisure k

Tha.Riddla
 
2010-05-10

:thumbsoup: thanks wowbagger, I knew I was on the right path...just didn't get to check.

Candy Beard
 
2010-05-10

Originally posted by: wowbagger[tip] The icon img's in the span are getting a display:block value from the .entry img{.. } declaration causing them to stop behaving inline. There's your problem.

Be aware that the .entry img{ .. } declaration appears twice in your stylesheet. k

A fix would be to add something like :

.slashdigglicious img { display:inline; margin:2px; }

You should also see the generous red border now, and remove it at your leisure k

You are genius+hero+wings/wind! I knew entry img was farking me up, and I knew that if I was actually competent at CSS like you guys I could fix this, and I was fumbling around in the right place, but it would have taken me a long time to semi-stumble on the answer. Danke!

Sorry, you must be a member to post to a conversation. Either log in or sign up to get involved.
TwelvestoneFront End

CSS-type question