drewactual

just go with margin: auto, get rid of the 0

oh, whoops.. apparently my reading comprehension skills need work…

the safest thing to do is point to the complete url.. as in http: //blahblah.. that takes some of the guess work out of it for browsers.

if it is in the peer directory, /base.css will suffice.

link for us?

your images are protected. If you change the permissions you may find they work.

also, the declaration display:block; in the a:’s may need to be exchanged..

see if this helps.

drop us a link, it will be easier to diagnose. i’ve seen many things cause this, but to be brutally honest it is usually the crazy simplest thing in the world at the root… such is ‘de-bugging’ huh?..

go back and use full URL’s to eliminate that as a possible problem is where I would start…

instead of /img/img.img, use http: //page/blog/theme/img/img.img..

using climbers (i.e.: ../././img.img) or even pointing to a peer directory (i.e. : /img/img.img) has been an issue for me in the past, and I found that being precise about it helps.. Now why it does that i couldn’t tell you.. But I’m guessing it is my fault and not the computer’s ??

how about a live example? from the picture you linked to all that can be extrapolated is what it looks like.. from that it may be:

-a table with outlined cells, and fixed images in it.
-a row of images with properties declared by css
-a feed which is not of your own construct, but simply ‘placed’ in your theme somewhere from an ad service.

the html and declarations would likely be easy, but what your asking for is a great big unknown right now. Plus, your asking us to write something for you that will likely make you $$ which is kinda funny.

You gotta help us help you!

about the wrapper..

you can do it that way which works and there are no issues with doing so.. you simply open a div id =wrapper just below the body tag in the header.php, and add a /div right before your /body in your footer.php.

you then assign some values to the #wrapper declaration in your css.

before you try that though, try adding a width to your body declaration in your style.css. then dump the 0. in other words:

replace this:

body {
  margin: 0 auto;
  padding: 0;
  font-size: 62.5%; /* Resets 1em to 10px */
  font-family: 'Lucida Grande', Verdana, Arial, Sans-Serif;
  background-color: #49525B;
  color: #829BB0;
}

with this:

body {
  width: 80%; /*or play with it to find right fit*/
  margin: auto;
  padding: 0;
  font-size: 62.5%; /* Resets 1em to 10px */
  font-family: 'Lucida Grande', Verdana, Arial, Sans-Serif;
  background-color: #49525B;
  color: #829BB0;
}

good job on the page/theme!!

go to your header.php (or whatever that theme calls the file responsible for everything north of content)

find:
<li><a href="https://jennas-internetmarketingcenter.com"></a>HOME</li>

replace with:

<li class="page_item page-item-2"><a href="https://jennas-internetmarketingcenter.com">HOME</a></li>

you closed a link ‘/a’ before the end of the tag, and you didn’t assign it the proper ‘class’..

to add additional tags on that bar, copy and paste the line I rec’d as many times as you need a new link.. and then go to the code and change the text (home, ect) as well as the url… do these BEFORE the /ul /div tags.

this is the way to hard code it. if your using widgets or such to control them, this is going to confuse issues. I am not familiar with that theme so i don’t know which method your using.

good luck!

gallery2- google it. they have themes much like WP, and in the end it sounds like it may suite your purposes better with image tags such as f-stop, aperture, exposure, and a handful of other terms I don’t understand. ??

you make it real hard without a link…

the first place I would start (walking into this literally blind that is) is with this little tid-bit of info:

FF is a much more complient browser than IE. Safari is too though which means your problem likely has more depth to it that just this, but I would start with your index.php and see if the structure validates. If the doc type hasn’t been declared I could see it causing an issue, as well if it is something as simple as lacking a > at the end of opening your body.

tons of things it could be. likely easy to solve too.. with a link.. ??

looks like you need to put a /div at the end of your index.php instead of at the beginning of the sidebar.. my bad!

fwiw- inline css is style set from inside the page, not pointing to an external file such as your style.css.

it can sure confuse matters if you forget it is there.

the trick is the transparent declaration for background-color…

go back and delete the line display:none; and you will be golden… or kinda blue as it is… ??