I planned on using an image as the background on my index page but it only works in preview mode. It doesn't show up when i upload the files. I'd like to have the image cover the entire page and i'd add buttons to that. Shrinking the file way down doesn't help. I don't have a problem loading images for content or thumbnails. I've been offered suggestions elsewhere but nothing has worked so far. I'm not using css. I'm using a mac. Suggestions?
thanks

Several questions:

- Did you use relative addressing to point to the image? Or is the web page looking for it on your hard disk (where it can't be found by the ISP computer).

- Is the image in the same folder on the site, relative to the location of the index page, as it was in the test setup?

- Did you remember to make the image public on the ISP when you made the .htm files public?

- Are you exceeding the ISP maximum download size for a page?

- What type of image file is it?

- Is the image larger than the browser window? Some browsers refuse to display such images.

- Are you using the deprecated background="url" property inside the body tag? It was never fully implemented in all browsers. Use a style sheet instead.

- Did you forget to close a quote, or to put quotes around the url?

- Use one of the validator programs, and see if you forgot to close tags.

- Many ISPs are case-sensitive for filenames.

- Does the filename violate the ISP file-naming rules?

Sample rules for mainframe ISP file servers which are different than Windows or Mac names:

1. No spaces in the filename.
2. The first character must be alphabetic.
3. No more than 8 characters in a filename. (It will shorten it "for you").
4. No 4-character extensions (such as .jpeg).
5. No special characters other than the underscore.
6. Must be all-lowercase.

These are sample file-naming conventions. Find out what your ISP actually requires for a filename.

I have never done any web design on a mac but can't you just stick:

<style type="text/css">
body {
background-image: url(image/image.jpg);
}
</style>

just an idea. but obviously it is css.

Yes you can, if the image is in a folder called "image" which is inside the folder containing the web page.

Well you could just change that folder to whatever? you can obviously also link to a complete url from there.

<style type="text/css">
body {
background-image: url(http://www.myimagehosting.com/image/image.jpg);
}
</style>

{just an example!}

well i think i have more or less the same problem.

i have made a picture to be displayed on the background of the entire site but it didn't work when i included the code in an external stylesheet.
It did however work as a global stylesheet, decleared in the header of the site.

It should work as an external stylesheet. You need to make sure that you are getting the correct url from the folder that your stylesheet is in not the page it is displaying on.

Paste this in the head tags.
Remember ur image will wrap.

<!--
body {
    background-image: url(images/urimage.gif);
}
-->
</style>

It is a much better choice to do it in your external style sheet no in your head

Your image file descriptor must be designed to tell the stylesheet where the image file is from where the css file actually IS stored.

so if you have your html files in your top folder, with subfolders named css and images, you have to get from the css folder up to your top folder, and then down to the images folder. Like this:

url(../images/image.jpg)

the .. says go to the parent folder above the folder the file is in.

the /images says to go to the subfolder named 'images'.

the /image.jpg says to get the image file named 'image.jpg'.

Another way to specify it is:

url(/images/image.jpg)

The / as the first item in the url means to start at the root directory of your site.

the others are the same.

Just a thought, if your using a linux server, it might just be that the server is case sensitive and your WYSIYOG designer ignores that, had a similar problem a while back.

Just a thought, if your using a linux server, it might just be that the server is case sensitive and your WYSIYOG designer ignores that, had a similar problem a while back.

Very good point. I didn't think of that.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.