My key and secret key register properly in other plug-ins. I get an error in this plug-in saying that my secret-key is wrong.
[Plugin: I am reading] Doesn't accept Amazon secret key (19 posts)
-
gerrymcg
Posted 2 years ago # -
cedarwaxwing
Posted 2 years ago #I'm having this problem as well, but have never used my amazon api key before. I'm pretty sure I'm doing it correctly, but the error message says my secret key is incorrect.
-
nicht-lesen
Posted 2 years ago #We are currently receiving reports about this problem from other people as well. We haven't been able to resolve the problem yet.
Since this started so suddenly, it might be that the problem is caused by changes of the Amazon API.We'll try to analyze and find the "bug", as our keys are workin' correctly and we've tried a bunch of keys from different people. It could be that there's a problem using the Amazon API with a different error message, which isn't handled correctly by the plugin - but I'm not sure and have to check this out during the next days.
Please wait, we'll be wokin' on it ;)
Regards,
Dominik -
CybrRob
Posted 2 years ago #I'm having this same problem as well.
-
Posted 2 years ago #nicht-lesen Are you still working on this or ??
-
Posted 2 years ago #Hi CybrRob,
I've been ill for a while now and didn't have much time, but I checked different parts of the code. The only thing I found out is that there might be this (in that case wrong) error message when file_get_contents() isn't allowed and there's no curl on your server / webhosting package.
The best way to find the bug would be to get in touch with someone who has this problem and check all details. (AWS Access Key ID + Secret Key + Server / Webhosting Config).
Regards,
Dominik -
caldwell
Posted 2 years ago #Feel free to contact me if it would help hasten the fixing of this problem. I can provide you with the details on my setup and config, etc. which are not working. Have tried installing this plugin twice to no avail. I've no choice but to discard it if I can't locate a fix.
-
Posted 1 year ago #Is this plugin dead at this point?
It doesn't work on a stock installation. The author doesn't respond. Is anyone picking up development on this?
-
Posted 1 year ago #I tried to find a new developer some time ago and the plugin died, so I did an almost complete rewrite of the plugin which works fine on thousands of installations right now.
I've no idea what's the problem with the Amazon API. It seems as if only some people from the US and UK are having trouble with authentication and I would do my best - if there would be free time.
If anyone is interested in doing (really) good work - please feel free to contact me at support@i-am-reading.info.
Right now - there's no chance for me to get this bug fixed - as I don't know what it is and I've no free time. My life is going on and I had a few changes regarding my job - so please be patient.
I'll try to get some people who will work on this plugin again.
Kind regards
Dominik -
Posted 1 year ago #OK. Thanks for the reply. It sounds like we're stuck for now. If you need a non-working example, let me know when you have time.
-
Keonyn
Posted 1 year ago #Yes, sadly I am also having this problem. I've gone through a dozen different keys and every one has given me the same problem.
-
ridjay
Posted 1 year ago #Any ideas when the plugin problem will probably be fixed?
Btw: I'm from germany, using the german amazon api and the plugin doesn't work (wordpress 3.0, most recent plugin version).
Edit: Reinstalled the plugin and it works flawless. Dunno why but it does.
-
Posted 1 year ago #Hi folks,
good news now - as I found a new developer who will work on the plugin from now on. I hope the bug with not working Amazon Keys will be fixed soon so that all of you can use the plugin as expected.
Regards from Germany
Dominik -
Posted 1 year ago #Great news! Thank you. Feel free to PM me when you have a new/test version.
-
Posted 1 year ago #UPDATE: Thought I'd upgrade to WP 3.0. Deleted the plugin and reinstalled. Didn't work still. Revisited Amazon and deleted keys created a few months back. Recreated a new key pair. Installed those. Configuration saved and plugin works.
So apparently something has changed in the keypair/API in the past few months with Amazon which this plugin doesn't like?
Hope this helps someone else.
-
Posted 1 year ago #FEATURE THOUGHT: Would be cool to have an "I have read..." link where people can see an archive of books read.
-
csigncsign
Posted 1 year ago #I use WordPress 3.0 with multi-blog function.
The plugin does not work, because it does not accept the secret key, which is definitely right :-(
-
Posted 1 year ago #@ caldwell
I deleted the keys, too, and made new ones, but the plugin still does not accept the secret key!
-
Posted 1 year ago #Alright, well I did what caldwell said. I disabled the plugin and I then removed it and FTP'd in to the server to make sure it was gone. I also went to Amazon and wiped my Access Keys.
I redownloaded and reinstalled the plugin and then created a new access key on Amazon. I entered the new key and at first it said it was an invalid access key. I believe there's just a delay since I entered it right after creating it. When I tried the second time it worked and accepted the key and the plugin is back up and running again. So thank Caldwell.
Something I did notice on the reinstall is that the file count is different from what I had on the server previously, even though I had the latest version on there. I'd always done the automatic upgrade from the plugin menu, could this be why? The menu also looks slightly different now as well as it fits in a nice little box on the API config screen, but before the reinstall it did not. Both versions are 0.9.9, but there are minor differences in file count and menu appearance between them in spite of being the same version. Only difference is that this one is a fresh reinstall, while the one prior was auto-upgraded through the plugin menu in WordPress.
I can't explain this difference, but I do recommend anyone having problems do what caldwell suggests and what I did as it seems to have done the trick for me.
Topic Closed
This topic has been closed to new replies.
