Yesterday's version of the 2.x-dev version breaks GeoField and IP_GeoLocation

I've seen the same, but do not have IP Geo installed, just Geofield. (i get an error on adding a node with a geofield).

I can confirm this too. I am using Geofield, not IP_Geolocation.
After updating to dev version from 2013-Feb-27, if I edited a map there was no available map layer. No map projection radio button was selected.
Selecting the EPSG:900913 one, and saving the map, I have all my base layers back, but I have to configure back the default one and the enabled ones.

May be the update script should be more specific. For now it shows:

7204 - Renamme the 'baselayer' in 'isBaseLayer' in layers.
7205 - Change the case of machine_name for layers, maps and styles. Warning, it can break things.

I too am getting:

There's a problem in the plugin definition of the layer type openlayers_layer_type_MY_MODULE. The layer will be disabled.

The regular release seems to break this as well.

The new release is now using projections as they should and modules providing layers and map needs to be updated in order to function properly.

Read: #1940174: Projection EPSG:4326 requested but not supported in openlayers_get_projection_by_identifier() and #1331410: Better Handling of Projections.

Is there any way to fix a previously-working configuration? I've only got two views using openlayers maps that I really care about, but not sure how to fix them. As I understand it it has to do with some modules specifying projects by just a number when the preferred has the 'EPSG:' prefix. Is there any way to track down which modules are not conforming?

(I'd guess it's IP Geolocation, but I'm not sure.)

Only hit for 'openlayers_layer_type_MY_MODULE' in my code base is in the file 'ip_geoloc_openlayers.inc'. I tried prepending all references to projections in that file with 'EPSG:' with no change in errors or behavior.

Sorry, double post.

Yes exactly,

A documentation page has been written, it explains to module developers how to update their code.

Read also why we did this here: #1943968: Layer Projections defined without projection authority cause "Exception: Projection 900913 requested but not supported".

I've updated my copies of the IP Gelocation and Geofield modules, but maps are not displaying at all. I'm going to try rebuilding a map later to see if it is something map-specific.

Also updated Geofield module, still no map is rendered. Created a new map, to no avail.

Has anyone found a solution to this problem?

Please recheck with 780da150a5ba36e1e0015aa15ce5b3315315f4de applied which should give more precise error messages.

I've recently applied mods to IP Geolocation Views and Maps, 7.x-1.x-dev, so that you can use it with the latest OpenLayers, i.e. 7.x-2.0-beta5 or later.
With IP Geolocation Views and Maps, you can pick any coordinate storage module you like, including Geofield.