TOPIC: Location of "not_found" / Cause - ref map running hotspots

Hi my map is showing "not found" messages at the moment. Im assuming this may be because the points added do not have "addresses" assigned to them, they were added in the backend of the system. What would we do to fix this? Also could this lead to the map slowing right down?

I appreciate any thoughts, so close to going live we're a little jittery.

The map page is living at: californiaclassics.co.uk/index.php/reel-locations

Adding a pic to an item *seems* to have made the whole map freefall. Not sure if that is our web connection as we're having internet connectivity issues here :/

Kate

Several things.
Check your configuration.php file and look for the variable live_site? Do you see it there? What does it have?
There is a cross domain javascript problem.
Long story short.
You call your site without www.
But the ajax requests are called with www. and the browser things that something is wrong and doesn't allow it.

On the other hand if you call the page trough:
www.californiaclassics.co.uk/index.php/reel-locations
then the requests are exectured, but there is a javascript error:

ProgressbarControl is not defined
progressBar = new ProgressbarControl(map, { ....

So what have you changed in the settings?

About the map not found message - find the marker that generates it and change it location (although this sounds somehow strange - with version 1.0 you should be able to show the markers even if the google geocoder doesn't know the location).

Heck I hadnt noticed the www. / without www. thing! I will get that changed right away. Re progressbar I'll have a look I think all Ive done is add code to put text in the add marker and map slides. Will check that out.

Very many thanks for the heads up on the cross domain thing I simply hadnt noticed the inconsistency was linked to using www. and not :/ about a million thanks, much appreciated.

Kate

Btw if anyone else reads this I think its possible the "not_found" message was appearing on our site because we had SEF problems, having switched back to insanely long URLS its disappeared. :/

Just a heads up in case anyone else finds this thread / something worth checking.

Kate

I cannot imagine that this has anything to do with the problem.