About To Upload My First Sale Page Site? Please Help

Hi,

You also have to upload the images, and the other pages...that should solve your problem.

1. Create a folder named [images]
2. Put all the images in there.
3. Upload that folder via your ftp
4. In your Frontpage, make sure that the images in your sales page are linked to:

http://www. yourwebsite.com/images/yourimage.jpg

but not: c://yourcomputer/somefolder/images...

(same goes for the links to your other pages)

Note: (replace "yourimage.jpg" with your actual image file name(s)

5. Once the images are correctly linked to the actual live domain name and folder,
and not to the folder on your computer, simply upload that sales page again.

This should do the trick.

Make sure you search for yourdomainname.com/theother page to find the other pages, and also have an images folder in the same place as your page files. Put all your images in there and you should be okay.

This is a bit long, but I've had this headache before and thought maybe I could help.

Most likely either the image files didn't get uploaded to the web server or the web page is not looking for the images where you think it is.

Some things to check first:

1. Log in with your FTP software and verify that the image files are all on your web server.

2. Check the names of the directories and files on the server and in the web page. Most web servers are case sensitive, so "Images" is not the same as "images." If the case in the file or directory name does not match the way it is in your web page, it would work fine in FrontPage on Windows but not on the web server.

3. Do you have spaces (or other characters other than letters, numbers, hyphens, or underscores) in the directory or file names for your images? Windows may allow this, but it will mess up web files. Use a hyphen or underscore instead if you want the effect of a space. If you have to change directory or file names, be sure to change them in the web page too.

=====

If it's not one of these problems, it's probably that FrontPage (or you) accidentally specified the path to the images incorrectly. This is a pretty common mistake. But you will need to look at the HTML code created by FrontPage and you will need to have some idea what it means. So this next part is more complicated if you don't understand the code behind things.

You can right click on your web page on the server in your browser and view the page source, or you can look at the HTML code in FrontPage.

Look at the file paths for image tags The image tags will look something like:

<img src="yourimagedirectory/yourfilename.jpg">
OR
<IMG SRC="yourimagedirectory/yourfilename.jpg">

The tags may have other attributes included like width, height, alt text, etc. That's ok, you are concerned with what is in the quotes after src=. That's the path to the image file.

Check the following:

4. Be sure the file path does not start with "file:///" because that would mean it is trying to find the image on your hard drive, not the web server. You have to be sure the file path points to the file on you web server. Sometimes web page editing software is configured to specify the link "relative to the document" which makes it set links to point to your hard drive. I forget how to change that in FrontPage, but I'm sure you can Google it and find out how to change this setting.

5. If you still haven't found it, it's probably a less obvious mistake if you are new. You have to understand a bit how absolute and relative links work. There are different ways to write a link, and they are easy to mess up.

For example, if your web page is in the root directory on your web server (named public_html or www or something else) and your images are in a subdirectory of this named images. The path might look something like this:

/images/mypicture.jpg

The leading slash means that the images directory is directly (absolutely) under your root directory.. The slash is an abbreviation for your root directory.

Or your path could look something like this:

images/mypicture.jpg
OR
./images/mypicture.jpg

Those are relative paths. In the first example, the lack of a leading slash means the images directory is relative to the current directory, the directory the current web page is in. It means the images directory is a subdirectory of the current directory. If your web page is in a subdirectory of your root directory but your images directory is also a subdirectory of your root directory, this would cause your problem.

The dot slash (./) also means the same thing. A single dot is an abbreviation for the current directory. A double dot is an abbreviation for the previous directory one level higher.

Or your path could look something like this:

http://www.mydomain.com/images/mypicture.jpg

This specifies the URL of the image. It works as long as the address is correct, but it is a bit less efficient for the server. It is processed by the web server rather than by the operating system.

The only other thing I can think of that it might be would be file permissions, if the image files weren't set to allow people to read the image files. But this is very unlikely I think. You can check file permissions with your FTP software if nothing else works.

I'm pretty sure one of the things above will be your answer, but good luck!