Awhile back I noticed that the Amazon Machine Tags plugin I use on various sites stopped working and wasn’t sure why since it had not been updated in quite awhile. When initially investigating I was hoping that there was an update I had missed that would resolve the issue with Amazon Machine Tags however that was not the case. Luckily the fix was easy and is documented below.amazon, Amazon Machine Tags, amtap, api, cache, links, plugin, verification key, WordPress, WP Super Cache, wp-content
Posts Tagged “WP Super Cache”
Feb 13 2011
Jan 08 2011
Late last night I realized that the traffic for Question-Defense.com was way down for the day and thought it was related to some recent updates I had performed on the site. I spent probably an hour or so last night verifying that nothing was out of the ordinary with the site and wasn’t able to find any issues. Upon waking up this morning the traffic again was extremely low for this time of the day even on a Saturday so we started to investigate. One of the referrers that traffic had dramatically decreased for was Google so we went to Google and performed a search that we knew would return a link to Question-Defense.com. Sure enough upon clicking on the link to Google we hit the question-defense.com URL and then we were immediately redirected to finditnow.osa.pl. Below we describe the issue in more detail, provide specifics about how our site was hacked, and provide the information needed to locate and resolve the problem.0day, 5.2.X, 5.3.X, advanced-cache.php, bing, CentOS, finditnow.osa.pl, google, hack, hijack, Linux, PHP, php 0day, redirect, search engines, search results, URL, WordPress, WP Super Cache, wp-cache-config.php, Yahoo, yum
Sep 29 2009
I recently noticed that the redirect from question-defense.com to www.question-defense.com was no longer working. Recently I updated WordPress and many of the plugins I have installed. The issue with this was some of the pages served from question-defense.com versus www.question-defense.com were serving different cached pages. After some investigating I thought the issue was related to caching however when caching appeared to b e turned off the issue still existed.directory, plugins, super cache, supercache, WordPress, WP Super Cache, www
Aug 11 2009
If you are using the Amazon Machine Tags plugin for WordPress then you are aware that Amazon recently changed their policy for the Amazon Product Advertising API and now will require that all requests are authenticated. Initially with the AMT (Amazon Machine Tags) plugin you wethe re only required to have the Amazon Access Key ID configured and not the Amazon Secret Access Key. Most people probably already had the Secret Access Key configured however if you did not have your “Secret Access Key” configured then after upgrading the AMT plugin will no longer work. If this is the case then your Amazon Machine Tags will display like the below in your WordPress posts instead of displaying the product properly.
Example AMT WordPress Post Tag: “[ amtap book:isbn=0596510489 ]”access key id, Admin, Amazon Machine Tags, AMT, AWS, plugin, products, secret access key, WordPress, WP Super Cache
Jul 16 2009
I struggled with getting WP Super Cache in full caching mode to work with a mobile device plugin such as WordPress PDA & iPhone for a long time. Awhile back I actually had given up because everything I was doing appeared that it should work but it wasn’t working properly. Needless to say I recently moved the site to a new server and decided to give it another shot. This time I was able to get WP Super Cache working with WordPress PDA and iPhone with ease.
Please realize that this method makes it so all of the mobile browsers do not cache pages but they also do not retrieve pages from the cache. To configure the below properly you have to realize that there are two different things happening which are the fact that mobile browsers should not cache files and they should not read from the cache. Basically if they didn’t cache files but read from the cache they would be reading the cache of the default template that you see in IE. If mobile browsers cached files then they would be caching the mobile template so when typical browsers such as Internet Explorer or Firefox visited the same pages they would be viewing the mobile cache instead of the default template you have configure..htaccess, blackberry, HTTP_USER_AGENT, iPhone, mobile browser, opera mini, rewrite rule, ReWriteCond, Templates, user agent, WordPress, WordPress PDA and iPhone, WP Super Cache