GMapEZ 2.0 beta 4
Chouser
fixes, but most importantly a new format is required for the script
tags and the API key.
The new format looks like this:
<meta name="gmapkey" content="abcde" />
<script
src="http://bluweb.com/chouser/gmapez/gmapez-2b4.js"
type="text/javascript"></script>
The gmapkey must be given before the gmapez script tag. Replace
"abcde" with your Google API key.
Thre reason for this new syntax is to allow you to specify keys for
different sites. For example:
<meta name="gmapkey:http://localhost/" content="fghij" />
<meta name="gmapkey:http://192.168.1.123/" content="klmno" />
<meta name="gmapkey" content="abcde" />
<script
src="http://bluweb.com/chouser/gmapez/gmapez-2b4.js"
type="text/javascript"></script>
To do something like this, you'd have to obtain the three different
keys from Google. GMapEZ will then use the pattern given after each
"gmapkey:" to decide which key to use. The order of the meta tags
matters -- the first patten that matches the current page's url will be
used. The pattern is actually a JavaScript RegEx, but for most
practicle purposes you can just use any part of your page's url.
Beta 4 also has some other bug fixes. If you have any trouble getting
this verson to work, or my description above is too confusing, reply to
this topic.
--Chouser
Barton
script in my <body> tag. Everything seems to work just fine, but now it
seems I need to use the <meta> tag for the key.
The reason I don't put the script in the <head> is that my content
management system doesn't allow me too :(
Chris Houser
Hm. Well, that's exactly why this is beta. Can you try putting the
meta tag in the <body> as well? As far as I know, that should work
fine.
If that doesn't work for you, maybe I can support two methods of
providing the API key -- I just hate to have more compilcated options
than strictly necessary.
--Chouser
t
Chouser
What browser were you using?
--Chouser