I own a GhostScripter Amazon Store. Have for several years. I need to authenticate the calls to Amazon. Is there anyone out there who owns this script that has successfully updated it to comply with the new authenticated method? If so, can you assist me with the code and file to update. Everyone has until August 15, 2009, to get this done. The schedule outage that occurred today was bad. My site went down from 11 am to 1 pm PDT. It failed the test, so I need to get this resolved. Thanks in advance.
I don't have a copy of Amazon Store. However if you have some knownledge of PHP I may be able to help talk you though adding the signature to your Amazon request. If you have not done so I suggest reading through the following thread. http://forums.digitalpoint.com/showthread.php?t=1366791 From what I have found when updating several other scripts it is easiest to add the signature code just before the API request is made by the parser. Much like I did with "ASM2" in the above thread or "Accessories Me" in the thread below. http://forums.digitalpoint.com/showthread.php?t=1432308 Find the php file located within the Amazon Store script which contains the parser. Echo the Amazon request URL just before the parser. If the echoed URL contains all the proper Amazon request "Parameters"? Most likely you can add the Amazon API signature code at this point. The code in the above Accessories Me thread includes my lastest updates and should work fine. Please note that you will need to rename the variable "$escUrl" to whatever is used by Amazon Store.
Thanks myhart. I read the two threads and it gave me enough confidence to get started. I spent several hours yesterday on this. I actually thought I had the issue resolved, but I did not. I did make progress with understanding the GhostScripter Amazon Shop code and scheme. For example, I believe the file I eventually need to edit is called /includes/functions/func.global.php. I think I've even narrowed it down to where within the code. But when I check the xml file that are returned from Amazon, they do not include a Signature. These were checked in the cache folder. I used the final code from the first thread as I couldn't determine what $escUrl should be for Amazaon Shop. Thank for the assistance. I will update the thread with any success. If someone has already solved this who owns Amazon Shop, please post here. There are a lot of Amazon Shops out there. There are several DP members who own some of them. They are all going to stop working soon if we don't solve this. Personally, I like this script very much. I have already contacted support at GhostScripter, but have not received a reply. GhostScripter is going to need to address this also as their product will no longer work. If you know the owner of GhostScripter, tell him about this thread. Over the years, I have updated the script myself to keep it working with the changes at Amazon, but my coding skills are weak and it gives me a headache and I dread doing it. I like the site running this script and it consistently makes income. So I will work through this and report back. Almost forgot, rep for myhart. Thanks again.
it may also be worth posting in the amazon Product Advertising API forum see if anyone there using theat script has a solution already ? http://developer.amazonwebservices.com/connect/forum.jspa?forumID=9
I'm back up and running. myhart informed me that GhostScripter updated their script. To be fair to GhostScripter, they replied to my email on August 14, 2009, to state the same. So there was a delay, but they did reply to my email. They are running a $30 special on a new license. Licenses come with one year of free updates. So if you bought your license in the last year, you are entitled to an update free of charge. Since my license is much older than that, I bought a new license and started another site, then I studied the code to updated the site/license I already own. I have updated my site for about the last four year, and made many changes as Amazon has made several change over the years, especially how images are served. If one has not made many changes to the script, and hasn't adopted a custom mod rewrite or template. The transition may be very simple by studying the new update. But if one has customized the script heavily, I offer these tips. 1. Start with /includes/functions/func.global.php and add custom mod rewrite rules. 2. Do the same with the major php files in the index directory: public_html eg. info.php used.php, search.php, shop.php, etc. 3. Very Importance. This cost me the most time: My info.php call was info.php?aid= it needed to be updated to info.php?asin= . I had to make sure this variable was changed in all files. This effected the used.php function also. I need to search and replace this variable, aid to asin. Everything started to come together after I discovered this point. 4. Updated .htaccess file if needed. I needed to change the mod rewrite rule that handle aid= . This pulled in the individual listings for the script in my version, version 5.0. 5. If you have a custom template, make sure the mod rewrite rule matches your .htaccess file. For me I need to edit all of the info_xxxx.html files. Yes all of them, with search and replace. I needed to change used.php?aid= to used.php?asin=. So I'm back up and running. Hope you are too. Many sales to you.