Re: Access to PNG images

You should really post a link to your problem page.

I am guessing that you are having problems with:
http://www.mariaandadam.com/sfsGoogleMapAPIwithPDmarker.html
so that images and even the pdmarker.js script are not loading.

That page's headers say it is hosted on an apache web server running on
unix.

The physical location of your page on that unix server, is in a
directory such as $HOME/public_html and your default page, the one that
shows when we go to http://www.mariaandadam.com/ is
$HOME/public_html/index.html. I'm just guessing here, based on a common
mapping between physical and virtual page locations (actually my pages
are layed out in a similar scheme on my ISP's web server). $HOME is
determined by you ISP's web host name and your account name and
configuration.

Your page is requesting the PdMarker script from "include/pdmarker.js".
This virtual location maps to $HOME/public_html/include/pdmarker.js so
you need to create the include directory, and copy the script from it's
home location into that directory.

Likewise, when you try to use an image from "images/dd-start.png", for
instance, you need to create the $HOME/public_html/images directory,
and copy the dd-start.png from Google's location into that directory on
your web server (copyright issues aside).

I use the FileZilla application from
http://sourceforge.net/projects/filezilla to copy files from my local
workstation to the ISP's web server. It has a nice user interface to
facilitate moving files between two locations, and makes it very easy
to create the directories on the web server and move files there
without learning ftp or unix commands. It is much easier to use than
the web interface provided by my ISP.

I configure it with the same password as I use with ftp, or with the
web application that my ISP provides.

If the page locations is correct, there are a couple of other issues
that can arise to cause pages that look like they are in the correct
location to not appear on the web.

First, file and folder names on the web, and in unix are case
sensitive, while file names in the windows environment are case
preserving. A windows file named AbC.txt can be found as abc.txt,
ABC.txt or aBc.txt; on the web and unix, the case must match exactly,
so that a file named AbC.txt will only show up when you look for
AbC.txt - the other variations name different files.

Second, web servers implement a rich set of security permissions to
control and limit access to files and folders. Files and folders can be
hidden, so that from the external internet, they appear not to be
there. This is a very complex issue, but if you have not modified the
default settings, this is not likely the problem. If you have modified
the security settings this may be hiding your pages and folders from
the net.