Markers/Errors

[Billw]

I'm getting the following javascript errors, and while the marker settings display and save properly in the admin, only the google default location marker (and no origin marker) appear on the map.

Message: 'GIcon' is undefined
Line: 693
Char: 1
Code: 0
URI: http://.../lr_v32/warpcore/literadius/views/map_assets/js_css/xml_g_maps.js


Message: 'ELabel' is undefined
Line: 526
Char: 3
Code: 0
URI: http://.../lr_v32/warpcore/literadius/views/map_assets/js_css/xml_g_maps.js


Message: 'Ca' is null or not an object
Line: 728
Char: 35
Code: 0
URI: http://maps.gstatic.com/intl/en_us/mapfiles/242c/maps2.api/main.js



The marker  .png image files all seem to be present where they should be and do appear in the admin configuration.

[Billw]

An export of lr_v32_config_vars further reveals that ui_map_marker and ui_user_origin do change with the admin settings.

example:
ui_map_marker   ui_user_origin
marker_29.png   origin_04.png

[Support]

If the default Google marker is showing up on the map the path to the LiteRadius marker directory might be invalid. If you have moved your locator template page relative to the installation you will also need to update the lr_path and icon_path in xml_g_maps.js

[Billw]

I have
var icon_path = 'lr_v32/warpcore/literadius/views/map_assets/js_css/markers/'; 

which seems correct.  There are two additional copies of xml_g_maps.js in my install, apparently older versions, with different paths.  One does not even have an lr_path:

var icon_path = 'map_assets/js_css/markers/';
var icon_path = 'ci/warpcore/literadius/views/map_assets/js_css/markers/';

[Billw]

Replacing all the xml_g_maps.js copies with the latest  October 12, 2009 version with the seeming correct paths did not solve the problem.

var lr_path = 'lr_v32/literadius.php?/locator/';
var icon_path = 'lr_v32/warpcore/literadius/views/map_assets/js_css/markers/'; 

[Billw]

Thought I found the problem - there is no xml_elabel.js file in my installation, nor does one extract from the zip file.  there is an elabel.js  (no xml_) so I tried referencing that, but still no markers.

[Support]

It appears that some files are missing. I can't say how that would happen but to sort things out I would download the latest version of LiteRadius, install it in a different directory than your current LiteRadius install, then upload the default us_filter.txt data set. Geocode the data and see if everything works. Then switch to manual mode and change some of the location icons.

[Billw]

I've tried unzipping lr_v3_2.zip on two different computers with two different unzip programs - there is no xml_elabel.js file in any subdirectory.  How can I get this file?

[Support]

LiteRadius does not contain a xml_elabel.js file so it is still unclear what error message is reporting this.

If you downloaded the latest archive and worked your way through the installation procedure (http://demo.escaperadius.com/literadius/warpcore/admin/views/docs/get_started.htm) at what step are you encountering difficulties?

[Billw]

In the LiteRadius documentation under customize the look and feel, on the page:

lr_v32/warpcore/admin/views/docs/style.htm

it says to add into the html document head the following:

<script language="JavaScript" type="text/javascript" src="lr_v32/warpcore/literadius/views/map_assets/js_css/xml_elabel.js"></script>

[Support]

You are right, we are wrong ; there is a typo in the documentation.

The docs should read elabel.js not xml_elabel.js so the included script should look like:

<script language="JavaScript" type="text/javascript" src="lr_v32/warpcore/literadius/views/map_assets/js_css/elabel.js"></script>

Sorry for the inconvenience this has caused you. We have updated our documentation.

Go figure, after all these years someone actually read the documentation. 

[Billw]

I already tried elabel.js instead of xml_elabel.js, but it did not solve any of the errors nor make the (non-default-red-with-black dot) markers appear.  Whatever file declares the GIcon class, I think that's what I need.

[Billw]

Ok...it turns out the script with the google maps key must appear first (or at least not last, like in the documentation).  The markers are working now!

[Support]

The order in which the scripts are inserted in the header should not have an impact on functions as they are called. The browser cashes .js files and unless a browser refresh in initiated the cashed script file would be called. You must have refreshed the browser at some point. But glad it's working now.