Kat,
I think that what you need to do is move your MENU stuff up near the beginning of your INDEX.PHP before the content stuff.
If you do this, the menu gets place first and then everything flows from there. You can probably get rid of the position:absolute in #menu. I use simply float:right to push the menu over. To push the menu down below the header, I use padding. You could pad it or use a margin. Use the same values as your top and right declarations.
In #menu, you have background-color: #ooo (oh, oh, oh) instead of #000 (zero, zero, zero).
I outlined your block level elements, and your .storyContent class DIV is the width of the whole page. Like I said, if you move the menu stuff UP in your INDEX.PHP, you will likely fix that. I hope. 🙂
Also, you declare a font-family for p, .storyContent and then a few lines down you declare a font-family again for .storyContent. You should be able to get rid of the second declaration without worry.
I always suggest COMMENTING OUT your CSS until you get it working, rather than deleting. That way you save yourself a lot of grief. It wouldn’t hurt to work to back up your original file anyway! 🙂
Hope this helps.
Craig.
I understand what you are saying but my .css worked in every browser yesterday. Webtv and all. It would just “fit” no matter the screen res. Now, it’s screwey. I will try your way and see what happens. I saved my layout anyway in case it goes south. Thanks.
Did not work. grr. I think I need to back away from it. It’s going to cause a blood vessel to burst.
Kat,
When you upgraded, did you keep your old INDEX.PHP file or did you go to the new one? If you used the new one, then it went back to the default layout and set-up. If you still have the old INDEX.PHP file, then I guess you could do a side-by-side comparison to spot any differences. When I upgraded, I had to re-order and re-do my layout because I used the new INDEX.PHP.
I gotta head back to work now, but I’ll check in this evening to see if you made any progress. I’ll have another look at the site then. I suspect it is probably a combination of CSS and your INDEX.PHP page that is causing this, and not simply the CSS.
Stepping away from it for a while will help, too! 🙂
Have fun!
Craig.
Looks fine for me (Firebird 0.7 browser)
Craig, I upgraded her. I used the new index.php with her old .css and worked my way back to the way it was. Having it viewable in Web TV is important as that’s how her parents view her site.
It looks fine in IE and Mozilla Kat.
So-gal,
Cool! When I looked at the site in Firebird today at lunch, there was definitely some text overlap, though. I had to scroll a ways down to find a post that did, though.
Craig.
It’s pretty much fixed now, she’s just fooling with little things. 😉
Well, the category and archive lists are still screwed up in a box shape instead of a list. Can’t fix that. Had to add a width of 70%; to both story content and content in layout to stop the overlap. The posts that didn’t overlap, are the ones that I manually fixed.
thanks for everyones help. I’ll figure out the list issues.
and the category section :
Categories:<br>
- <?php list_cats(0, ‘All’, ‘name’); ?>
Search:
<form id=”searchform” method=”get” action=”<?php echo $PHP_SELF; /*$siteurl.”/”.$blogfilename*/ ?>”>
<div>
<input type=”text” name=”s” size=”15″ />
<input type=”submit” name=”submit” value=”search” />
</div>
</form>
Archives:<br>
<?php get_archives(‘monthly’); ?>
kat,
Instead of using like 10 br’s in the menu div at the top, couldn’t you add padding or margin and accomplish the same thing?
I suppose I could but have no idea how. I am still just learning how to do this and that is why I am asking for help. I really am not trying to be a pain. I can’t figure out the problem and there are no help sites for WP other than this. What I mean is , there is no place that just has a list of codes and tell you what they do. Thanks.
