I stumbled on a fix for this — I think. I hope this is the link to it
http://wordpress.org/support/topic/40132#post-227287
I got it right the first try!
Good for you! And thanks for posting the solution. It helps others with the same problem.
Thread Starter
Zapa
(@zapa)
Hi all and thank you for your answers. (wow… one month since my first post, i’had almost forgotten it)
All right! This is the most accurate solution till now. As you can see in my blog http://enezeta.com/zapateces The categories are indented and now the bullet of the parent is aligned with the title of the parent category. Thank you!!
I have modified slightly the code of the solution and tweaked it to match the best appearance. The code i¡’ve used is
#links li {
list-style-image: url(images/links_bullet.gif);
padding: 2px 0 2px 0;
margin: 5px;
}
Now my problem seems to be that there is no margin between the bullet and the left border of the side bar. I’ve tried to increase the margin value but when i do this the interline increases too porportionally.
If i want to preserve the interline space i have to put margin value =0, so there is no space between the left border and the bullet. Any idea how i can fix it? the same line or something like that?
Thank you again!
You know I hadn’t noticed that till you mentioned and now it is driving crazy. I tried a few (quite a few) tweaks but things are getting worse not better. Notice the column is wider now. I’m thinking the .line div is related. I was going to suggest specifying
margin-right: 5px;
but it didn’t really help and it didn’t appear to harm it either when I upped the numbers. I did just notice the negative top margin on the .line class and using it on at top ‘pulls’ the sidebar into place better.
Here is a shot in the dark — try moving the #links ul section above the #links li section in the cascade. There’s a theoretical reason that might make a difference though I’ve yet to prove it myself. Sorry it is too late for me to try it myself.
BTW thanks a heap for making the wider column so obvious to me now — it’ll make me nuts till I figure it out or give up and switch to tweaking a different theme more. 😉
Thread Starter
Zapa
(@zapa)
No prob… thanks to you for the code!
It seems to be a problem with your blog as I can only display it as plain text with Firefox. With Internet Explote there’s no problem to watch it in all its glory. Maybe our problems are related with the browser??
I returned to my stylesheet to chek out what yo’d said about moving the #links ul section but it’s already above #links li! I have moved it under instead and have no effect. The result is the same so i have moved it back again to its original position.
Well… it is not the best margin size for the bullets and the interline space but it is significantly better than before. I know nothing about php or javascript so I have no idea what to touch to improve it. If you think on something i’ll be pleased to check it and help you (us 😉 )
C u!
asparagus, I’m not seeing a styled page at all in FF1.06, and you have a couple of tag errors you should probably fix, which might help: http://validator.w3.org:8001/check?uri=http%3A%2F%2Fwww.oldnewbie.org%2FWP%2F
Look’s like the stylesheet call is okay, checking source, but it’s definitely not styling the page in FF or Opera 8.02.
Thanks, VKaryl, I had seen the failedvalidation and was too tired and upset to worry further about it the other day.
It complained of a missing close tag for an ul — but having no Pages was leaving the list with not li – or child items. So I added a dummy page.
I was stumped by the second error which sometimes reported a missing close tag for a div and sometimes reported no close tag for body. The line numbers weren’t much of a help. I tried the close div in a few spots but settled on putting in the footer.php above the footer opening comment.
That fixed the page for the validator. FF still renders text only but Opera 7.54 likes what it sees. FF also has trouble with oldnewbie.org that also validates. In FF none of the template renders and even WordPress Default is mangled and I didn’t alter them (except to add the Theme Changer.) Without opening a browser skirmish, I’m not so impressed with the fox.
Yeah, browser stuff is always YMMV…. I don’t honestly have a clue about why FF would choose not to display your styles. It’s very strange…. I don’t see anything with the FF web dev extension that would be suspect, and it’s a beccary theme, her stuff is SO good…. it’s today’s gremlin I guess!
And to top it all off, it looks fine in Op 7.23…. man, I can hardly wait for someone to figure THIS one out! Ummmm….. Okay, even weirder…. you can see it just fine, styled, if you use the web dev extension for “edit css”.
Oy.
So the fox is not perfect (hush the Linuxen may hear.)
I’m not a CSS expert and browser vagaries mystify me but around 5AM I got a thought I haven’t looked into about @import – I was too busy to look into because I was moving the direct out of the root folder to /wpblog/ for no pressing reason but to avoid messing with a .htaccess in the root, where my Host has a tool to write into it and I just knew in my guts it would cause a mess.
