https://buy-zithromax.online buy kamagra usa https://antibiotics.top buy stromectol online https://deutschland-doxycycline.com https://ivermectin-apotheke.com kaufen cialis https://2-pharmaceuticals.com buy antibiotics online Online Pharmacy vermectin apotheke buy stromectol europe buy zithromax online https://kaufen-cialis.com levitra usa https://stromectol-apotheke.com buy doxycycline online https://buy-ivermectin.online https://stromectol-europe.com stromectol apotheke https://buyamoxil24x7.online deutschland doxycycline https://buy-stromectol.online https://doxycycline365.online https://levitra-usa.com buy ivermectin online buy amoxil online https://buykamagrausa.net

Just what I need — coding problems, too …

So taking Hythian’s suggestion, I did some research and found the Google Referrer program for Firefox that he mentioned. You need to be a Google AdSense affiliate (I am), and…

So taking Hythian’s suggestion, I did some research and found the Google Referrer program for Firefox that he mentioned. You need to be a Google AdSense affiliate (I am), and you simply get some additional code to paste into your site.

All well and good, but I couldn’t get it to work. Some of the referrer stuff would display, some wouldn’t, and it seemed to interact together badly.

Finally thought to view in IE. Hmmm. Works there. Front page looks like crap, but the referrals work.

But …

Hmmm …

Looked at an individual archive page. Multiple AdSense stuff working perfectly there, FF and IE … and the page looks good in both, too.

So … something screwy between the two templates?

Both have the same doctype at the top

<!DOCTYPE HTML PUBLIC “-//W3C//DTD HTML 4.01 Transitional//EN” “http://www.w3.org/TR/html4/loose.dtd”>

Interesting … different charsets in the metas. The main index uses UTF-8, the archive page uses ISO-8859-1. I wouldn’t think that would make a difference, and MT should be publishing the page as UTF-8 anyway … Make the correction for the archive page template, no difference.

Hmmm. Requires more looking. The basic page framework divs are the same for both, which makes me wonder if I have a div problem on the main index page (outside the basic framework) — except I don’t understand how that would screw up the page in IE (but not in FF) and I *really* don’t understand why it would screw up the AdSense Java scripts.

Must ponder further.

43 view(s)  

3 thoughts on “Just what I need — coding problems, too …”

  1. Okay, here’s the (or at least “a”) really weird thing — what’s being pulled in for the AdSense buttons between the main index and the archive page is different — even though it’s running off the same MT module code.

    Hmmmm …

  2. Thought it might be that the main index was doing a server side include, while the archive was using an MTInclude command, but that didn’t resolve it.

    Static vs. Dynamic? I’d expect the dynamic (archive) page to be broken, in that case.

    Code between them is exactly alike, but the displayed results are different. Very weird.

  3. Aaaaand … some sort of weird caching problem. Because when I opened a new instance of the main index page, everything looked right.

    Doesn’t explain the weirdness with the difference in display of the front page in IE vs. FF, but at least the AdSense stuff is working (and I’ve earned two whole dollars this month! Whee!).

Leave a Reply

Your email address will not be published. Required fields are marked *