Has Denensio's API 2.0 broken the plugin?

[Neil Darlow]

Hi All,

I've recently installed Habari-0.8 and am currently trying to
configure the Defensio-0.4 plugin.

I have a Defensio API key and when I attempt to configure the plugin I
get the following error:

Sorry, the Defensio API key ... is invalid. Please check to make sure
the key is entered correctly and is registered for this site
(http://...). Defensio said: "Unable to connect to api.defensio.com"

The API key is present at defensio.com but the Unable to connect to
api.defensio.com suggests that some change in the API may have broken
the plugin.

Regards,
Neil Darlow

[Colin]

It's quite possible. I don't use Defensio - tried once but didn't think much of it. I'll check it out later today or tomorrow if I get a chance or if someone else doesn't before then.

> --
> To post to this group, send email to habari...@googlegroups.com
> To unsubscribe from this group, send email to habari-users...@googlegroups.com
> For more options, visit this group at http://groups.google.com/group/habari-users

[Colin]

I've done some quick testing and this seems to be working for me.

It's worth pointing out that the plugin still uses the 1.2 API.

I suspect the issue may be a communication issue between your Habari instance and the outside world, rather than a problem with the plugin being incompatible with the Defensio API.

HTH

Colin

Note: I've tested using the latest revision of the plugin from https://github.com/habari-extras/defensio

--
Colin Seymour
Blog: http://colinseymour.co.uk
Tech Stuff: http://lildude.co.uk
Barefoot Running: http://barefootrunner.co.uk
IRC: lildude #habari

[Neil Darlow]

Hi Colin,

On Thursday 26 Apr 2012 12:52:25 Colin wrote:
> I've done some quick testing and this seems to be working for me.
>
> It's worth pointing out that the plugin still uses the 1.2 API.

Yes. although the newer 2.0 API is being promoted it appears the 1.2 API is
still supported.

> I suspect the issue may be a communication issue between your Habari
> instance and the outside world, rather than a problem with the plugin being
> incompatible with the Defensio API.

Maybe I was unlucky at the time I installed the defensio plugin. I'll give it
another shot and see what happens.

Thanks for taking the time to investigate the issue.

Regards,
Neil Darlow

[Matt Read]

Defensio had server issues by being overloaded. the 1.0 series API is
synchronous and so if the defensio server fails to respond it dies. The
lastest plugin has a "retry mechanism" and it will keep retrying every
few seconds until defensio servers respond.

Defensio upgraded their API to 2.0 and made it "Asynchronous", where you
submit your comment for testing, then the defensio server responds to a
set entry point on your server at a later time with the result. This
solved their servers not responding from being overloaded.

I never got to updating the plugin to use 2.0, but someone should do
that :)

Just make sure you use the latest plugin from github to be sure it's
using the retry thingy and it should work.