WordPress.org

Ready to get started?Download WordPress

Forums

Basic Google Maps Placemarks
[resolved] Incompatibility Between BGMP 1.9.3-rc1 and JetPack 2.0.4 (6 posts)

  1. Gillian
    Member
    Posted 1 year ago #

    Hi Ian

    First and foremost, Happy New Year :-)

    The maps on both my sites suddenly stopped loading - the "loading" graphic didn't even appear. I changed themes to three different WordPress default themes but it didn't make any difference.

    I then followed the usual troubleshooting technique of deactivating all plug-ins except BGMP (which made the maps load again), and then reactivating them one by one until I found the culprit.

    I found it was a new component of JetPack that was introduced with the latest version (2.0.4), namely, Publicize. Deactivating Publicize results in the maps loading again.

    I tested further and found that BGMP 1.8 works fine with Publicize activated, which is why I have concluded the problem lies in an interaction between BGMP 1.9.3-rc1 and the Publicize component of JetPack 2.0.4.

    Hoping this helps someone.

    http://wordpress.org/extend/plugins/basic-google-maps-placemarks/

  2. Ian Dunn
    Member
    Plugin Author

    Posted 1 year ago #

    Thanks for the detailed report Gillian, and happy New Year :)

    I was able to reproduce that. It looks like maybe Jetpack is stripping the [bgmp-map] shortcode out of the content when the page is generated. I had to disabled both Publicize and Sharing in order for BGMP to work.

    It looks like Jetpack is causing problems with a lot of plugins. (1, 2, 3, etc).

    I've spent about 2 hours this morning digging into it, but haven't found the specific source of the problem yet. I'll keep working on it, but don't have any more time today.

  3. Ian Dunn
    Member
    Plugin Author

    Posted 1 year ago #

    Ok, I discovered that this is caused by a bug in Jetpack. See Timperator's post in this thread for a workaround until Automattic fixes it.

    The reason it affects 1.9.x and not 1.8 is because 1.8 accesses $post->content directly, instead of using the_content(), so the filters that hook to the_content aren't being applied. Accessing $post directly is a bad practice, though, which is why I changed it in 1.9.x. But unfortunately that makes it susceptible to the Jetpack bug.

  4. Ian Dunn
    Member
    Plugin Author

    Posted 1 year ago #

    Er, nevermind, it turns out this is a bug with BGMP and not Jetpack. I'll fix it for 1.9.3-RC2.

  5. Gillian
    Member
    Posted 1 year ago #

    At least I'm glad I didn't waste your time, and it really was a bug :-)

    Sorry I didn't realise that the Sharing component of JetPack also needed to be disabled (because I already had it disabled on my sites).

  6. Ian Dunn
    Member
    Plugin Author

    Posted 1 year ago #

    1.9.3-rc2 is now available, which should fix this.

Topic Closed

This topic has been closed to new replies.

About this Plugin

About this Topic