Marker clusters broken in Chrome

Viewing 5 replies - 1 through 5 (of 5 total)
  • modernwoe

    (@modernwoe)

    1 day, 3 hours ago

    Confirming this issue in the latest version 2.3.21 https://www.pasteboard.co/pEI3sTwaUu8U.png. Is there a working demo of this? The one on https://wpstorelocator.co/demo/ doesn’t have clusters turned on.

    Custom markers defined with WPSL_MARKER_URI also don’t display.

    I’ve previously been lockedo n version 2.2.236 which works as expected.

    • This reply was modified 1 day, 3 hours ago by modernwoe.
    Plugin Author Tijmen Smit

    (@tijmensmit)

    18 hours, 49 minutes ago

    I had one other user point this out, and in his case a greedy js script on the page grabbed all images and removed the dimensions cause the marker images to appear broken.

    The quickest way to narrow down if this comes from your theme, or another plugin is for a second test a default theme, or disable all other plugins. It can also be a css file that forces a different dimension on the image ( max width or so )

    I enabled the marker clusters option on the demo page and they look fine. I can also select the cluster images with the dev tools on my demo page, but for some reason this fails on your site @andymacb . Any chance you have an url where this happens @modernwoe ?

    • This reply was modified 18 hours, 48 minutes ago by Tijmen Smit.
    Plugin Author Tijmen Smit

    (@tijmensmit)

    18 hours, 33 minutes ago

    If you don’t mind and let me know which theme + other plugins you’re using, then I can try and replicate this and potentially add something to the store locator code that makes it harder for the marker images to break.

    modernwoe

    (@modernwoe)

    14 hours, 38 minutes ago

    I can no longer replicate the Markerclusters issue. I couldn’t track it down but I think it was a caching issue on my local causing the CSS to break. It happened with _s and twentytwentyfive with no other plugins installed but not when I tested on a staging server. This would make sense why the OP only has the issue in Chrome.

    The markers issue is a v odd one. We can no longer use custom markers if their filenames overlap with default plugin colors (like dark-blue.png) if they use the @2x.png retina naming convention. When a custom icon matches any name in the $plugin_markers array, create_retina_filename() forces the 2x suffix instead of preserving @2x and the markers don’t display!

    modernwoe

    (@modernwoe)

    41 minutes ago

    @tijmensmit The markerclusters bug started again on my staging server when I used filters but I think I’ve tracked it down. This fixed it for me.

    1. markerClusterer.getClusters is not a function error in Console – refers to old API

    change:
    const clusters = markerClusterer.getClusters();
    To:
    const clusters = markerClusterer.clusters;

    2. Because the new createClusterRenderer() uses base64-encoded SVGs, the default Google Maps hardware-accelerated engine miscalculates their bounding boxes during rapid redraws. Add optimized: false to render them as standard DOM elements

    return new google.maps.Marker({
    position: cluster.position,
    optimized: false

Viewing 5 replies - 1 through 5 (of 5 total)

You must be logged in to reply to this topic.