Until recently, the Amazon Quick Linker code (type="amzn") worked just fine on my site funboardgames.org. Today I realized that it's not working in Firefox and Internet Explorer. Instead of the hand pointer, I see the I-beam cursor when hovering over such links. I'm not sure when this started, but it might have been when I upgraded to WP 3.0.5. The code still works in Chrome and Safari. I'm trying to pinpoint the source of the problem and have sent a similar question to Amazon. Could it be something in 3.0.5 that is causing the problem? If so, what can be done to fix it?
[resolved] amzn Quick Linker fails in FF and IE - 3.0.5 problem? (10 posts)
-
glsonn
Posted 1 year ago # -
sprux
Posted 1 year ago #From what I can tell, this isn't an issue with the new 3.0.5 release. I have not yet updated to 3.0.5 and am experiencing the exact same issue. The Amazon widget JS resource throws the error "document.body is null" in firefox, but like you said it works fine in webkit (safari/chrome). Based on the resource address of the amazon quick linker widget, it seems like the widget code has not changed since 2008.
I am wondering if there was perhaps a change to one of the WP plugins that loads a JS resource after the Amazon widget script is loaded, which then causes the issue in FF and IE. Which plugins do you use? And what is the URL of your blog, perhaps I can have a look at your <head> area and see if we use any of the same plugins that load JS resources after the Amazon <Script> tag? Sure would like to get to the bottom of this, especially since Amazon support was no help whatsoever.
-
Posted 1 year ago #Plugins I'm using at FunBoardGames.org -
Akismet
All in one SEO pack
Google XML sitemaps
Pretty link (lite version)
TinyMCE advanced
TweetMeme retweet button
W3 total cache
WP-statsIf you visit the site, you'll see that most links are working, but only because they no longer use the short "amzn" code. Here's one page I haven't updated yet...
http://funboardgames.org/all-ages/teenagers/
Thanks for looking. Hope you can find the solution.
-
Posted 1 year ago #Well, it looks like the issue has been resolved somehow. Links on the page you linked to seem to work, and I'm getting positive results on my blogs now. I am guessing this was an issue on Amazon's side and they have fixed the problem for us. :)
-
Posted 1 year ago #Oh, sorry, scratch that. It's been a long day and I was testing with Chrome. Still broken, will let you know if I find any clues to this mystery...
-
Posted 1 year ago #Ok, good...sorta. I was going to say it was really getting weird if it was fixed for you but not me.
-
Posted 1 year ago #Well I found a solution, though it's more of a hack than a true fix for the issue.
For some reason (not entirely sure why, I'm not much of a JS guru), Firefox and IE don't seem to recognize the
document.bodyelement before the<body>tag has finished loading, even though I am pretty sure it's supposed to wait until the whole page has loaded before running the amzn quicklinker code.Anyway, to fix the issue, at least temporarily, move the
<script>tag for the QuickLinker widget from the<head>section of your template to just after the first<body>tag. I just did this and it is all back in working order!Hope that helps!
-
Posted 1 year ago #Thanks. Now I just have to figure out where that is amongst all the php.
-
Posted 1 year ago #Wasn't as hard as I thought. The body tag was just a few lines down in the "header" file.
-
123milliseconds
Posted 1 year ago #Please mark thread as resolved so that
- others with similar problem can see it as resolved and will read this thread for help if they have similar problem
- people providing help see it as resolved and will not waste time reading this post.
Topic Closed
This topic has been closed to new replies.
