I just purchased your plugin last night and have spent several hours trying to configure it with no luck. I have gone through every piece of information I could find in your forums and your FAQs (well written and helpful, by the way). I have carefully copied and pasted my AWS access key and private key into the configuration as well as my Amazon affiliate ID. I have tried both cURL and fileGetContents (after configuring the PHP configuration for my website to enable it).

I see nothing displayed in my article, either from the embedded code {amazonWS:itemId=0945053622,0945053657,0945053746} or through configuring the metadata for the article with a comma delimited list of three tags.

If I disable the plugin, I see the embedded code displayed in the article output. Enabling the plugin makes the code disappear once more.

One thing I noticed is that my invoice with the download link specifies version 3.0 to support Joomla! 2.5 and 3.0, whereas the version I downloaded from the link was 2.5. Could this be related to the difficulty? I am running Joomla! 3.0.2 on my site. I would sincerely appreciate any suggestions.

Never mind... I found another way to embed my Amazon affiliate links without this plugin. I will continue to test this and look for a way to get it to work, but I am disappointed at this point.

Hello, the Joomla 2.5 version is designed to work in both 2.5 and 3.0, that should not be a problem.

There are a few things to check, firstly check that the ISBNs 0945053622,0945053657,0945053746 actually correspond to products on the country site you are searching, often they will be available for one country but not another.

If you are searching using metatags it is much better to use one rather than three, 3 tags usually lead to a search that is way too specific, Amazon will only return results that match all search words.

I suggest trying embedding code with a very general search term, eg

{amazonWS:keywords=Food}

that will definitely match something, if you do not see anything it is not a problem with the embedding code.

In that case it is a good idea to turn on the options to show error messages, and see it there is one.

Also it is a good idea to check that you have copied the keys correctly, the secret key in particular can contain characters that look like they are punctuation, eg a full stop at the end which can confuse people.

If this does not solve your problem let me know and we will certainly investigate further.

I have the same lack of results even using the code {amazonWS:keywords=Food}.

I was very careful to copy every character of each code required for AWS.

I tried 2 metatags. Incidentally, the three tags I used were exact terms that return at least 12 results when used as search terms on Amazon.com. I verified several times that the ISBNs were correct for the books I embedded.

I had turned on the error reporting options when I first installed but do not receive any error messages.

I'm sorry but I simply cannot dedicate any more time to this at the moment. My next steps will be to install this plugin on a pristine site to see if it works there, on the suspicion that this is due to a conflict with another plugin.

The search terms you use on Amazon.com would not lead to the same results as the Amazon advertising API, they use a broad match on the website whereas with the API they only return exact matches.

That said, it sounds as if you have been fairly thorough with this, if you wish I will be happy to take a look myself if you would like to send me an admin login for your site. Don't post it here but send by email to the address from which you received the order confirmation.

It does sound more like a problem with your credentials than with the embedding code. One thing is that Amazon do require nowadays that you have their permission to use your associates id on each specific site, if it is a new site perhaps you have not the appropriate permission yet? That may be worth checking.

In particular if you do that I can check it will my own Amazon credentials which I know do my work.

I did do a quick check of the plugin code and cannot see anything which is likely to be problematic, Amazon do occasionally change things that might make a request stop working properly, but nothing obvious brought itself to my attention.