Unable to move map.

[jaycollier]

Hi!

After the last upgrade, one of our embedded maps can no longer be moved around on some browsers. (Ok on Chrome, not on Firefox or Safari, both with cleared caches.)

These work great!

• Regions: https://www.mcht.org/visit-a-preserve/regions/southern-maine/
• Preserves: https://www.mcht.org/preserve/long-point/

However, our main map does not move via mouse drag like the others:

• https://www.mcht.org/visit-a-preserve/

This is the shortcode: [mashup query="post_type=preserve" width="100%" zoom="7" maptypeid="preserves1"]

Do you have any suggestions?

-Jay

 

[Chris]

Hi,

Sounds like maybe the page is being cached or there’s a JavaScript error from another plugin.  I do see some errors in the console.

Please give this a try:

1. Disable all plugins except MapPress.  Check your maps again.  If they’re working, re-activate one by one until you find the error.
2. If that didn’t help, try a standard theme.  Install and activate one of the WordPress themes, like “twenty twenty”.  Check your maps again.  If they’re working, it’s a theme problem.

[jaycollier]

Resolved. The problem was much simpler. We had a quotation mark in an incorrect location in the mashup shortcode.

Was:

[mashup query="post_type=preserve" width="100%" zoom="7" maptypeid="preserves1"]

Should have been:

[mashup query=post_type="preserve" width="100%" zoom="7" maptypeid="preserves1”]

Working. Case closed 🙂

 

 

[Chris]

Hi,

I’m glad it’s working, but it’s strange – it looks to me like the first shortcode is actually the correct one.

[jaycollier]

I had put the quotation mark before the descriptor rather than the attribute.

This didn’t work: “post_type=preserve”

This did: post_type=”preserve”

-Jay

[Chris]

I did see that, but I think this is correct.  The attribute in the shortcode is ‘query’ so its value should be in double quotes:

query=”post_type=preserve”

I still can’t pan the map at the original URL.  Did you make the change there yet?
https://www.mcht.org/visit-a-preserve/

[jaycollier]

This ticket is old, but I wanted to provide an update for others who may find this ticket.

We discovered that the problem was a javascript minification for this one page by the Swift Performance plugin. Once we excepted this page from minification, it was working fine again.

I did not have time to explore what other script conflicted, but the problem was solved immediately, and we continue to be very happy with this plugin!

Thanks, Chris!

-Jay

[Author]

Posts