Updating to the latest version of Views breaks my OpenLayers views. I believe this is due to the changes made in Views 6.x-2.7: http://drupal.org/node/621428

I tried changing the view to use an unformatted or table layout (as per Merlin's suggestion), but couldn't as I kept getting this error: An error occurred at http://brat.info/admin/build/views/ajax/display/Maps/page_4/style_options.

Comments

wisu’s picture

StatusFileSize
new137.11 KB
new68.79 KB

I think Views 6.x-2.7 it also broke mine... as it was the previous action i did.. not sure on how to test...

before upgrade each marker will show the title and an image of the node... now its missing...

using OpenLayers 6.x-1.0-beta3... any pointers?

delykj’s picture

Same bug here.

jerdavis’s picture

This might help:

http://drupal.org/node/614292#comment-2225422

This patch corrects a similar problem with view driven node and user reference fields. I'd applied the patch to resolve those issues and my openlayers maps are working correctly.

jerdavis’s picture

Status: Active » Needs review
StatusFileSize
new2.22 KB

Actually, I was seeing this problem too when rendering the entire row to the popup. Implementing the same code in that patch for CCK resolves this issue. Patch against 6.x-1.x CVS branch attached.

wisu’s picture

@jerdavis - I confirm that the patch solves the issue...

Thanks!

phayes’s picture

Status: Needs review » Fixed

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

agileware’s picture

Status: Closed (fixed) » Needs review
StatusFileSize
new1019 bytes

The committed fix for this issue doesn't properly fix the problem.

Just incrementing a counter for the index doesn't keep the index in line with the current view row.

This means when I'm rendering the entire row as a popup the data in the popup is not necessarily from the same row as the lat/lon point.

This patch fixes this issue fully.

It's against 6.x-1.x-dev.

phayes’s picture

Status: Needs review » Fixed

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.