Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Right after a cvs update, while testing for the fix for http://drupal.org/node/825098 I noticed a weird
behaviour on editing a MULTIPOINT geometry.
To reproduce:
Manually type MULTIPOINT(0 0, 10 10) in the WKT field, save.
Go to EDIT again, use the 'move feature' tool to move one of the features.
Result: the feature being moved is NOT highlitghed, the other IS
Expected behaviour: the feature being moved is highligthed.
Comments
Comment #1
tmcw CreditAttribution: tmcw commentedFrom a cursory glance, isn't this an upstream OpenLayers bug, rather than a module bug?
Comment #2
zzolo CreditAttribution: zzolo commentedI can confirm this behavior.
This does not happen if you do not use MULTIPOINT, so I would assume this has to do handling arrays created from the GEOMETRYCOLLECTION. I still don't think we should support different data formats (#801108: Address Manual WKT CCK Input)
Comment #3
tmcw CreditAttribution: tmcw commentedDuplicate of #801108: Address Manual WKT CCK Input: somewhere down the line we need to make this work with all kinds of WKT input, despite the sad amount of javascript creep this will involve.