- Although info fields in an info set are changed, they are still displayed as they were before!
There may be two reasons for that: either the cache is not refreshed, or a webservice is used to overwrite the actual info set content. Note that the standard setting is to use an overwrite if a webservice identifier (for example an Amazon ASIN) is given. This can be switched off, for example for the first info field, by setting the parameter info1overwrite to 'none'
- The Amazon webservice does not work at all
Make sure that you entered to correct values for the Amazon webservice access key and also the secret access key. If you don't have any of these keys, the webservice will not work! To get these keys, sign up at Amazon and follow the instructions to use the Product Advertising API (this requires another sign up).
- What does "permanent overwrite" means? What is overwrite anyway?
The term "overwrite" denotes the process of fetching information from a webservice (such as Amazon or Google books) and then fill in the item information according to the fetched data (i.e. filling in title, image, author and publisher). This overwrites the information that was entered by the user before (if any). Again, to prevent overwrite in an individual info field, set the respective overwrite parameter (for example "overwriteinfo1") to "none". This can be done in individual info sets or in the global configuration, which then affects all items and all info sets. The task "permanent overwrite" simply uses the fetched data, fills in the info sets and stores them into the database. That way the information is saved locally.
