Hi all,
Just a quick update on the Amazon stuff. (And kind of a thread hijack... sorry)
Garvin, I have a rewrite of the Amazon Media Button plugin close to finished. Things to do are:
- Polish css/html. (Right now all the tags are just div and spans without classes or id.)
- Separate the Amazon functions into a included file so that we can reuse it fairly easily.
- Document setup/changes in a format users can easily see.
The new features are:
- Fully templated
- Dynamic refresh of data
- Enables inclusion of fields previously excluded because of Terms issues (price/availability)
- Two levels of caching (one for plugin output, one for xml response that can be used across plugins)
- Uses REST, eliminating the requirement of nuSoup library
Single biggest disadvantage:
Because of Amazons requirements to sign all requests with a private "key", and because Amazon has linked the private "key" with billable services, I can no longer ship the plugin with a developer key. Users will need to create a developer account themselves to run the plugin.
As I have rewritten the plugin, I kept in mind the idea that I can port the Amazon functions to other plugins, specifically the Recommendations plugin (though I really want to write a wrapper plugin for Wish Lists, too) and I think porting my functions will be pretty simple. Hopefully I will have a polished Media Button version to send to Garvin next week for review, and I will take a look a updating the Recommendations plugin to be more useful.
Zvenson, let me know if you would like to test the updated Recommendations plugin when I get to it. I'd be happy to have someone test out my code before it goes in spartacus. (this goes for the Media Button plugin, too
)
Hope everyone is doing well!
- i would be very thankfull! 
)! 
