Yea, that's an issue with OpenLayers' Virtual Earth layer. It has 
issues with late binding to the dom element. I have an open bug with 
openlayers, and track it on our ticket tracker here: 
http://bugs.horde.org/ticket/9111

You're right, thanks.
Google map provider/geocoder work great now.  I also tried VE/Bing and 
I received this error:

Webpage error details

User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; WOW64; 
Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 
3.0.30729; Media Center PC 6.0)
Timestamp: Sun, 27 Jun 2010 20:06:28 UTC


Message: Object doesn't support this property or method
Line: 45
Char: 17
Code: 0
URI: https://presslab.us/horde/js/hordemap/ve.js


It's fine though, as long as one of them works that is great.

You didn't update the config/*.php files after you pulled.

The latest git pull causes an error with Kronolith and a bunch of 
other modules as well:

[27-Jun-2010 11:43:22] PHP Fatal error:  Call to undefined method 
Horde_Auth::ge
tAuth() in /usr/src/horde/kronolith/config/prefs.php on line 208

I can't even get to the portal page.  It looks like something changed 
in the framework and the other modules are not updated yet?

Updated to 2.9.1. Can the OP please verify if this issue is resolved 
or not now?

Possibly related to:
http://trac.openlayers.org/ticket/1910

though the ticket seems to have been ignored lately as none of the 
devs can reproduce currently either.

As I still cannot reproduce this in any browser I've tried, this will 
likely stay open until Bug: 9044 is dealt with....

With the previous error I was using Google for both.  If I select 
Virtual Earth for both I get this error:

User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; WOW64; 
Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 
3.0.30729; Media Center PC 6.0)
Timestamp: Wed, 19 May 2010 15:55:10 UTC


Message: Invalid argument.
Line: 217
Char: 5
Code: 0
URI: https://presslab.us/horde/js/hordemap/ve.js

Which seems to be a similar problem.

...and what mapping provider are you using, and what geocoding service 
(if any)?

Still cannot reproduce using IE 8 - or any other browser for that matter.

Sorry, I was being lazy.  To get the error I had to copy back the old 
file, clear my caches, etc.  That error is:

User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; WOW64; 
Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 
3.0.30729; Media Center PC 6.0)
Timestamp: Tue, 18 May 2010 22:59:58 UTC


Message: Invalid argument.
Line: 11970
Char: 13
Code: 0
URI: https://example.com/horde/js/hordemap/OpenLayers.js
When I create a new entry, put in an address, and then click "Find in 
Maps."  The map tab does not open up and I get the javascript error.

Thanks for your help.

FYI Ticket: 9044 has been added for updating to 2.9.x

...and that error is?
Yes, there is a newer version available, but our code was written 
against the version we distribute.  I do have it on my list to update 
the script, but there are a number of customizations we have done that 
would have to be ported/tested.
What is the behavior that works incorrectly in the version we distribute?
We purposely don't link to the file for a number of reasons.  First 
and foremost is the huge size of the full openlayers file. We 
customized the bundled files to include only the features that are 
absolutely needed, when they are needed.
That may be true for 99% of the cases, but it's not true if hosting 
your own GIS server to provide custom map tiles.

I'm not seeing any issues with the kronolith map code. Perhaps if you 
provide the exact error messages you receive, when you receive them, 
along with the details of the map providers you are using, I can try 
to track down the issue you are having.

When trying to access a map, it gives a javascript error.

The problem is that the /horde/js/hordemap/OpenLayers.js is outdated.   
The new version from http://www.openlayers.org/api/OpenLayers.js works 
correctly.

Perhaps instead of using the static file, Horde could link to 
http://www.openlayers.org/api/OpenLayers.js - after all, internet 
access is required to make the maps work in the first place.   
OpenLayers encourages linking as noted on this page: 
http://openlayers.org/