Viewing 8 replies - 1 through 8 (of 8 total)
  • Plugin Author Matthew Denton

    (@mdbitz)

    Hi, I’ve done some initial review and the issue does not appear to be related to the API. As i see the same version of the plugin working across multiple sites but not on some. Upon review it appears that in most cases the issue is that the server time is off causing the request to error out with RequestExpired exception from Amazon. I am working on a fix to check for this error and resubmit the request based on lookup of gmt time from a time server which is working but I need to do some follow up to make sure there is not going to be excessive calls to the Time Servers which would cause a denial of service to future requests for the time from your host and would end you back in the same situation currently being faced.

    If you have access to your server I would suggest verifying the gmtdate time returns the current time correctly. I noticed on my web host it is off by 20 minutes.

    Hopefully further updates soon,

    Matthew

    Thread Starter Mike Stop Continues

    (@mike-stop-continues)

    Hi Matt,

    Unfortunately, gmdate(); indicates the correct time. Is there anything else I can try?

    Thanks for your help!

    Plugin Author Matthew Denton

    (@mdbitz)

    Mike,

    I’m going to add additional error display to the validation screen in the upcoming version so we can see the exact reason your validation is failing.

    Working on support for locales and looking to have it available by end of week.

    Thread Starter Mike Stop Continues

    (@mike-stop-continues)

    Thanks Matt! That’s excellent news.

    Plugin Author Matthew Denton

    (@mdbitz)

    Mike Version 1.8.0 has been released. After updating let me know the detailed error you are receiving so that we can resolve it.

    Thread Starter Mike Stop Continues

    (@mike-stop-continues)

    Matt, I updated to the new version.

    I distinctly remember getting an InValid message (on account of the capitals) when I was working with the plugin last month, but when I tried after updating, a js-error prevented getting any validation notification at all. So I tried on a test site, and my keys validate. I can only assume that they’re also validating on my regular sites now too.

    Would any of the changes you made account for my (presumably) solved problem? In any case, thank you. Here’s the JS error:

    admin.php:700
    Uncaught TypeError: Cannot read property '0' of undefined
    jQuery.ajax.success
    admin.php:700
    f.Callbacks.n
    load-scripts.php:3
    f.Callbacks.o.fireWith
    load-scripts.php:3
    w
    load-scripts.php:5
    f.support.ajax.f.ajaxTransport.send.d
    load-scripts.php:5
    Plugin Author Matthew Denton

    (@mdbitz)

    Mike, what is your website? I can take a quick look and see if i can identify why you are getting the js error. if you don’t want to post it here email it to me at [email protected]

    Plugin Author Matthew Denton

    (@mdbitz)

    Marking thread as resolved as keys are now validating.

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘[Plugin: WordPress-Amazon-Associate] Keys InValid since amazon API update’ is closed to new replies.