Jetpack Clash

  • Resolved Kyle_Irving

    (@kyle_irving)


    10 years, 6 months ago

    Hello,

    First up your plugin is great thanks.

    Recently we noticed that there is a problem with Anitspam Bee and Jetpack Comments.
    When you have both running at the same time users are not able to leave comments as they receive a notification “Invalid Key”. This notification goes when you deactivate Antispam Bee.

    Any ideas?

    Thanks

    https://www.ads-software.com/plugins/antispam-bee/

Viewing 6 replies - 1 through 6 (of 6 total)
  • Anonymous User 7658014

    (@anonymized_7658014)

    Not 100% sure, but I think the plugin might just not provide support for Jetpack. Do you have a test site running where that message shows up in the front-end?

    Thread Starter Kyle_Irving

    (@kyle_irving)

    Thanks Caspar – i just noticed in the description that Jetpack is unsupported, that answers that then.

    Anonymous User 7658014

    (@anonymized_7658014)

    Ok, sorry this wasn’t very helpful. Would you still consider marking the topic as resolved?

    Thanks!

    Thread Starter Kyle_Irving

    (@kyle_irving)

    sure – happy to mark as resolved – do you know if the devs have any intention of adding Jetpack support?

    Anonymous User 7658014

    (@anonymized_7658014)

    As far as I know he doesn’t (source in DE). Jetpack used to do this:

    $( '#commentform' )
  .attr( 'action', "https://jetpack.wordpress.com/jetpack-comment/" )
  .attr( 'target', '' );

    which used to create a potential conflict with German law as it was unclear if and to what extent data was being tracked on wordpress.com servers without the user’s knowledge.

    However, I’m definitely not up to speed with Jetpack development. Things might have changed since the article cited above was posted.

    Thread Starter Kyle_Irving

    (@kyle_irving)

    Thanks for the link and the insight.

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Jetpack Clash’ is closed to new replies.