• kamakurasurfer

    (@kamakurasurfer)


    Hello, first I’d like to say that I’m very impressed with your dedication to support of this plugin. Secondly I’d like to share something I discovered recently after installing Subscribe2 10.19.0.

    I had the exact same problem as described in this topic. (the first and last posts, which were never fully addressed.)

    After considerable process of elimination (deactivating every plugin and re-activating one at a time, isolating Jetpack, and then deactivating every default Jetpack setting and re-activating one at a time) I finally narrowed it down to a problem with Jetpack settings “Enhanced Distribution” and “WordPress.com Stats.” If these are deactivated then Subscribe2 works exactly as it should.

    I use some default Jetpack settings, but not the above 2, so this was an acceptable workaround for me. Sorry if I missed this fix somewhere in the support posts. I searched but did not see it.

    Cheers,
    KS

    https://ww.wp.xz.cn/plugins/subscribe2/

Viewing 2 replies - 1 through 2 (of 2 total)
  • @kamakurasurfer

    Jetpack seems to be an issue quite frequently so I don’t use it at all. I’ll take a look at these modules if / when I get time. Subscribe2 already disables some of it’s own features or those of Jetpack to maintain some level of compatibility – it seems that may need reviewing.

    Thread Starter kamakurasurfer

    (@kamakurasurfer)

    Thanks for the response. I wasn’t necessarily looking for a fix. I had already seen your conflict warning about Jetpack in the support site, so I suspected it was the problem. I just wanted to let others know some more detail about the conflict. I don’t like Jetpack either, but right now it’s the lesser of two evils for my site.

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

The topic ‘Conflict with WP Jetpack’ is closed to new replies.