After upgrading from 7.x-2.0-alpha2 to 7.x-2.0-beta1, all my maps disappeared.

I have taken these steps with partial success but still have no maps where the layers extract styles and attributes from kml files....

1. Installed 2.11 OL locally to replace an older version
2. Switched to Google maps API v3.5 which recovered my base maps
3. Tried various setting changes with OL image and css locations with no success
4. Tried re-creating maps with new layers etc - but no layers that extract styles and attributes from a kml file will display.

I don't want to assign a style to these layers as I have many tracks using different coloured lines and multiple non-default icons - and the styles were being picked up with no problem before the upgrade.

I woud appreciate any help/ideas/advice on this please. Thanks

Comments

nod_’s picture

nod_
Primary language French
Location Lille
commented

Do you have any kind of error, JS or PHP ? I haven't seen this before so I don't know where it could be from.

Did you check your layer configuration ? you should have a checkbox that handle this.

Patroclas’s picture

Patroclas commented

I am getting 'Layer not found' in my logs. I have tried re-creating the layers and used absolute and relative paths to the source kml file but no difference. It seems that OL is looking in the wrong place for the layers???

It's strange that most of the layers that use OL styles are found but those where the style is extracted from the kml are not.

I am not sure what you mean by "Did you check your layer configuration ? you should have a checkbox that handle this."

Patroclas’s picture

Patroclas commented

I have done some more testing on this...

I have changed all settings to use the hosted version of OL but with no difference so I assume that my local version is OK.

I can get kml layers to show but ONLY if they are not set as activated in the map's layer settings. When they are set as initially activated, they don't display, but they are shown as selected in the switcher check-box.

If the layer is not set as activated in the map's layer settings it will display when selected via the switcher.

The 'zoom to layer' behaviour only works when the layer is activated via the switcher.

So there does appear to be a problem with the 'activated' setting in the map interface, and/or with the zoom to layer behaviour.

I would appreciate any further ideas on this but it looks to me as if it's a bug?

If it makes any difference, I do have many layers and maps on my site so the scripts in the head are pretty huge. I am not a javascript coder so don't know if this could cause the problem - its just a thought. If anyone has any suggestions on how to debug this further I would welcome them as I have no experience of debugging much beyond css and html.

Thanks!

tomsherlock’s picture

tomsherlock commented

Just wanted confirm that I also have the same problem with 7.x-2.0-beta1: no maps.
I also have the same error message in my log: 'Layer not found'.
Additionally I have multiple, 'Dependency not found: ' errors found in the Map's Behavior section.

tomsherlock’s picture

tomsherlock commented

I'm happy to say that I figured out why the map wasn't showing for me.
Under admin/structure/openlayers the directions for OpenLayers Source suggest:

For instance, you could use a Drupal relative path like: sites/all/libraries/OpenLayers-2.11/OpenLayers.js

Instead I had put: '/sites/all/libraries/OpenLayers-2.11/OpenLayers.js'.

I had prepended an extraneous forward slash. With the offending forward slash gone, I'm able to see map.

Patroclas’s picture

Patroclas commented

Unfortunately that is not the case with my set-up.

The base maps are displaying (after changing to GoogleMaps 3.5) and the layers are there but they are not displaying if they are set as 'activated' in the map settings.

The error message 'Layer not found' has this detail:

admin/structure/openlayers/layers?render=overlay

Relating to the previous post, it has always been the case with my set-up that the url to create a layer does need the prepended slash, but the path to OL does not. But changing that makes no difference to my issue, except that the layer is not created at all without the slash in it's url.

Patroclas’s picture

Patroclas commented
Title: No maps after upgrade » No maps after upgrade [solved]

I think I may have solved this.

I have found that changing the layer order will display the missing layers. I did have most of my layers well down the stack (starting at -10) and bringing them up to a higher level works.

Toktik’s picture

Toktik commented
Title: No maps after upgrade [solved] » No Google Map after upgrade

Other maps working OK, but google maps doesn't.

here are javascript error.

openlayers.js:104
TypeError
arguments: Array[2]
get message: function getter() { [native code] }
get stack: function getter() { [native code] }
set message: function setter() { [native code] }
set stack: function setter() { [native code] }
type: "non_object_property_call"
__proto__: Error
Toktik’s picture

Toktik commented
Title: No Google Map after upgrade » No Custom Layers after upgrade

It seems that all my custom layers are not working.

Message in Logs.

Layer profile_map_view not found.

codi’s picture

codi commented

I seem to be having the same issue.

I can create a clone of any existing map leaving all options as default except I've enabled and activated my data overlay. Click save, assign the map I've just cloned to the page view and I get a map with properly placed pins. ANY other modifications to the map and it disappears from view. Even something as simple as enabling popups in behaviours or setting a width other than the default causes the map to not render.

Nothing in the db log, but I do get a TypeError in my javascript console.

Toktik’s picture

Toktik commented

Still issue. Any ideas?

codi’s picture

codi commented

I've still got this issue. Thinking about trying the dev release again. I was on the dev release initially and had the same problems, but I've seen a few patches go through since I last tried. Can any of the devs confirm one way or the other that this is a problem?

codi’s picture

codi commented

Sooo... upon further review. It looks like the map was being rendered. Just hidden. Changing the height or width fields caused it to render hidden, but changing the values in inspector fixed it. Also, leaving the height and width as defaults, but changing any other fields worked. Not sure if the problems other people on this thread are having are related. Could you guys give it a try. If it's the case them it might be any easy enough fix.

zzolo’s picture

zzolo commented
Version: 7.x-2.0-beta1 » 7.x-2.x-dev
Status: Active » Postponed (maintainer needs more info)

Hi @codi. Can you provide an export of your map? Also, is you KML file local or remote? The dev has some fixes that might address.

basvredeling’s picture

basvredeling
Primary language Dutch
Location Amsterdam
commented
Issue summary: View changes
Status: Postponed (maintainer needs more info) » Closed (won't fix)

Cleaning up the issue queue for #2670484: Stable 7.x-2.0 release.