Let me show what happened here. I have 2 computers, 1 with windows XP
- Internet explorer 6.0 without problems like this, but in another
computer, with windows Vista - Internet explorer 7.0, the problem was
occurs. I donīt know if the problem occurs with differents explorers
or window's versions, but I hope this information can be used to
advantage.
> There appears to be issues with the overview map. Try commenting out
> the addition of the overview and see if it makes a difference. Please
> report back! If it is that and you really need the overview map, you
> can fix v=2.115 in your API call, at least until the problem is
> resolved.
today I was worried why this error suddenly ocurred( this.Ve.width' is
null and GMarker was disappeared in IE,but in FireFox not
dissappeard)
but now reading your messege.
I tried commenting out.
// map.addControl(new GOverviewMapControl()
then resolved. ^^v
but I like this the overview map ,,,
so
fix v=2.115 and using it ^^
Yes there is an issue with the overview map control in the latest
version.
Apparently you have to set the map type for the window after you add
the control
to the map, but I tried this and did not work.
The best option as of right now is what you mention in your post; Use
v=2.115
Regards,
Sergio
> There appears to be issues with the overview map. Try commenting out
> the addition of the overview and see if it makes a difference. Please
> report back! If it is that and you really need the overview map, you
> can fix v=2.115 in your API call, at least until the problem is
> resolved.
On Jun 25, 7:27 am, Thor <thor.mitch...@gmail.com> wrote:
> This error occurs when using v=2 (or v=2.116 which is currently
> equivalent) and then adding a GOverviewMapControl to the same map more
> than once.
Hardly anyone does that, surely? But there are many reports of
problems. Or does changing map type cause the API to do that by
itself?
> Has anybody seen this error on a map which does not use
> GOverviewMapControl?
Commenting out adding the GOverviewMapControl makes the map work, but
it still throws an error complaining about Ve. I haven't done much
investigation into that, it was rather late last night here in the UK.
> There appears to be issues with the overview map. Try commenting out
> the addition of the overview and see if it makes a difference. Please
> report back! If it is that and you really need the overview map, you
> can fix v=2.115 in your API call, at least until the problem is
> resolved.
Commenting out GMap2.addControl(new GOverviewMapControl()); prevents
the error from occurring on phonelocator.mobi.
> Yes there is an issue with the overview map control in the latest
> version.
> Apparently you have to set the map type for the window after you add
> the control
> to the map, but I tried this and did not work.
> The best option as of right now is what you mention in your post; Use
> v=2.115
> Regards,
> Sergio
> > There appears to be issues with the overview map. Try commenting out
> > the addition of the overview and see if it makes a difference. Please
> > report back! If it is that and you really need the overview map, you
> > can fix v=2.115 in your API call, at least until the problem is
> > resolved.
We are enterprise user and we experienced same issue as Chris
mentioned.
Following Andrew's idea we commented out the overview map, everything
works fine now.
But whatever we specify the version to 2, 2.x, 2.115 or 2.116, if we
bring in Overview Map, we always experience different kinds of error.
When Goolge can fix this bug?
On Jun 24, 6:26 pm, "warden [Andrew Leach - Maps API Guru]"
<andrew.leac...@googlemail.com> wrote:
> On Jun 24, 11:23 pm, Chris <cca...@gmail.com> wrote:
> > I seem to be having a similar problem. Nothing has changed on my side
> > but all of a sudden I am getting an error in IE saying:
> > Line 711 Error: 'this.Ve.width' is null or not an object
> > Could something have changed with the API?
> v=2 now loads 2.116, changed from 2.115 today (as it's Tuesday).#
> There appears to be issues with the overview map. Try commenting out
> the addition of the overview and see if it makes a difference. Please
> report back! If it is that and you really need the overview map, you
> can fix v=2.115 in your API call, at least until the problem is
> resolved.
I too am getting this problem, I have multiple maps on the page, The
first one loads fine but any subsequent ones throw the error. If i
turn remove the overview map then all my maps work fine. (using v=2).