The location where the browser looks for an image depends on how the image is being displayed and what its specified path is:

- Absolute path (i.e. http://www.xyz.com/images/myimage.gif) : The browser looks at the specified location.

- Relative path (i.e. images/myimage.gif) : This is relative to the location of the page (which would be default.aspx)

- Relative path in CSS (i.e. background-image: url(myimage.gif)) : This is relative to the location of the CSS file where the image is referenced

Do you see a broken image icon? If so, you can right-click it and obtain the location where the browser is trying to find the image.

A few other ways to determine where the browser is expecting to find the image:

- In FireFox, select Tools > Page Info - Media. Look for the image name in the list and you will see the path the browser is using.

- Using IE or FireFox you can use the add-on developer toolbar (Google for it) to examine properties for all elements of the page. View the properties of the image to find its path.

- Look at your server log and search for the image file name. The log entry will contain the path where the image was expected.

HTH.

Nik

Based on your earlier description, this is a client-side issue so the fact that the page is rendered by DNN isn't germaine to the problem. Once the page is rendered on the server-side and sent to the browser it is just ordinary HTML.

Since you have verified that the path is correct, I am inclined to believe that this is a timing issue. When Javascript code runs on the browser, any HTML elements the code is interacting with need to already exist in the browser. So, if the script that positions the markers is running before the HTML elements where they are to be displayed are rendered by the browser, you will see the problem you are experiencing. This is easy to verify --

1) Launch FireFox

2) Type "j a v a s c r i p t :" in the address bar and press Enter. This will bring up the messages window.
(Note: skip the spaces...the forum will not display the word if I type it as-is.)

3) Type in the URL of the actual page ni the address bar. The message window will log all the JS errors encountered.

If you see no errors, then the script has error-handling and is trapping them. In this case, the only way to determine the problem is to examine the source code.

Nik