Support » Plugin: Basic Google Maps Placemarks » 1.10 View on Map issue

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Author Ian Dunn

    (@iandunn)

    It works for me when I click on Alder Creek, Camden, and Chittenago; but not when I click on Orkanse, Oswago, or Rome.

    Are those last three included on the map? If not, then there’s no way that they can popup, since they don’t exist.

    If your map shortcode is only pulling in one category, then you should have the list shortcode do the same, so that the markers match up.

    I know the left side works (Alder Creek, etc.) I can’t figure out why the ones on the right don’t work (Oriskany, etc).

    The map shortcode uses the categories gas and gas2

    The list on the left is categories=”gas” and the one the right is categories=”gas2″

    Both categories are showing up on the map, but the right column (gas2) doesn’t work when you click View On Map.

    Here is the code:

    [bgmp-map categories="gas, gas2"]
    <table>
    <tr>
    <td align="center">
    [bgmp-list categories="gas" viewonmap="true"]
    </td>
    <td align="center">
    [bgmp-list categories="gas2" viewonmap="true"]
    </td>
    </tr>
    </table>
    Plugin Author Ian Dunn

    (@iandunn)

    Does it work if you disable Marker Clustering on the Settings page?

    When clustering is enabled, the markers set is converted into a different data structure to make it compatible with the clustering library, but I think that may break the mapping between the marker and the reference that the viewOnMap function is using to open it.

    I don’t have Marker Clustering enabled. I enabled it for the hell of it and View on Map still worked for the left column, even those inside a cluster. No change on the right column.

    Plugin Author Ian Dunn

    (@iandunn)

    I was able to reproduce this on my test site, and it turned out this was because the bgmp_list element was using an ID instead of a class, so it’s not supposed to be placed on a page multiple times.

    The ID can’t be removed because that would break backwards-compatability, but I added a class to it and updated all the internal references to use the class instead of the ID.

    That fixed the problem on my test test, and you can download 1.10-rc4 to test it on yours.

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘1.10 View on Map issue’ is closed to new replies.