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.
When using the Grouping field, clustering doesn't work. Disabling the grouping field allows clustering to work again.
Also, how do you assign a custom image to the cluster feature? I want to give it a specific image, rather than the default orange circle...
Comments
Comment #1
phayes CreditAttribution: phayes commentedThis is a bug in the clustering behavior, not the view. For anyone wishing to take on this bug, here is an example of it not working:
Comment #2
phayes CreditAttribution: phayes commentedupdating version...
Comment #3
phayes CreditAttribution: phayes commentedcrap. updated to wrong version... updating to correct version.
Comment #4
zzolo CreditAttribution: zzolo commentedhttp://drupal.org/cvs?commit=297066
I changed around the clustering logic pretty significantly. Before it was taking options from the behavior array and pushing them into the top level map options. Then it would create a cluster object for the vector layer based on those. I am not actually even sure if it was working.
Now, it is all based on layers (and should be only for Vector layers). So, a behavior is defined as a cluster with a layer defined. Then when Vector layers are made, they look for corresponding cluster behaviors.
This seems to be working fine with the test example I coded into the test module. But more testing would be great. Also, please note that this may break anyone currently using clustering.
As far as 2.x, I don't feel this is a very elegant solution, and I am not sure what is in the 2.x code as far as clusters, so I don't think there is any reason to port this.
Comment #6
Agileware CreditAttribution: Agileware commentedI have a WMS map with three layers grouped by a cck field and if I turn on the clusterer for the view
my template overridden colours are lost and popups don't work anymore.
As soon as I disable cluster it works again.
This is fine as I don't need it but I just wanted to report it.
This happens even with the current dev version.
Comment #7
Agileware CreditAttribution: Agileware commentedChanging component back
Comment #8
Agileware CreditAttribution: Agileware commentedActually I've resolved the popup issue I was having.
The colours thing is kind of a different issue to the one committed but the original poster also asked about it.
I can open a different issue for that if you like.
Comment #9
zzolo CreditAttribution: zzolo commented@agileware, if you are still having a problem and it is unrelated to this specific issue, then it would be cool if you started a new ticket. Thanks.
Comment #10
Agileware CreditAttribution: Agileware commentedNo worries
Comment #11
dasjoi am not shure if this matches the issue, but i am trying to cluster multiple layers. so that points of different layers could be clustered together. it doesn't seem to work and i suppose this is yet by design. could this be confirmed?
Comment #12
strk CreditAttribution: strk commented@dasjo clustering is per-layer by design. Doesn't match the issue.
Comment #13
dasjothanks strk, resetting this issue and opened a support request: #930864: clustering across multiple layers
Comment #14
dasjo