Hi SK. Quick question before I dive in: the google api javascripts that stopped functioning, was that in the wp-admin part (as were the quicktags), or in the blog front-end as well?
And did you happen to check with firebug (or a similar javascript tool) to check what errors were thrown, or can you re-enable for a second and check (because I can’t reproduce)?
Thread Starter
S.K
(@kichu)
Thanks, Futtta for your response.
Yes, the problem is both on the front end and the admin part. I tried re-enabling and checking with firebug. It shows a big chunk of errors which turns me dizzy.
I’ll try it with another site of mine to find out if it conflicts with another plugin.
S.K
ideally you would be able to reproduce this an a non-production site (or one which can be broken for a couple of hours) which would allow me to go bug-hunting there myself? 🙂
but feel free to copy/paste that big chunk of errors here or into a mail to futtta-at-gmail-dot-com
just a silly idea: do you have DoNotTrack (the “bonus feature”) disabling 3rd party tracking? if so, can you try without that option to see if that solves the problem? I would still be very interested in the errors you got though (I’m working a new plugin that’ll do nothing but DoNotTrack)
Thread Starter
S.K
(@kichu)
Futtta, you are dead on!
I disabled DoNoTrack and everything is hunky dory!
But I need the do-not-track thingy too. Any non-conflicting version of it?
Thanks and regards
S.K
ok, now we’re getting somewhere. to solve this, i’m afraid i’m really going to need the javascript-errors generated by donottrack-min.js, either by being able to see them for myself in firebug on a site of yours, or by having a copy/paste dump from your firebug or javasript error console. what do you think?
Thread Starter
S.K
(@kichu)
Please see the blank space under the heading “Search site” on the side bar of http://aimwa.in/ and the content area of http://aimwa.in/search-results (under “loading”).
Hope this helps.
S.K
Weird, can’t see any trace of donottrack-related errors in the firebug-output, the only output I see is related to the google custom search implementation:
“NetworkError: 404 Not Found – http://www.google.com/uds/api/search/1.0/b30fd838d9675ca5b151bcc19ff5c9c8/default+en.i.js”
default+en.i.js
google.search.CustomSearchControl is not a constructor
http://aimwa.in/?s=india&submit=Search
Line 301
Which seems to imply that the js-loader did not succesfully load the search javascript-file because the wrong hash (?) was used. The question is; where does that hash (b30fd838d9675ca5b151bcc19ff5c9c8) come from? and in what way could donottrack interfere?
Can you disable donottrack, I’d like to see if that URL (the hash inside it) is different. maybe that way I’ll start to understand what is going on here …
Well, I digged some more, the hash (and full URL) are defined by Google in a response right after initiating the search.
This is what’s happening:
* jsapi (javasript loader) is loaded successfully
* search starts initiating (the google.load line)
* http://www.google.com/uds/?file=search&v=1&hl=en is called successfully
* that file contains a URL (including hash) for a javascript file which (a.o.) defines google.search.CustomSearchControl
* that javascript file cannot be loaded (gives a 404)
* because google.search.CustomSearchControl isn’t know, a javascript error is thrown
questions remaining:
* how can DoNotTrack cause this (I’m really stumped up until now to be honest)?
* can you disable DoNotTrack so I can see what is different in that case?
Thread Starter
S.K
(@kichu)
//can you disable DoNotTrack so I can see what is different in that case?//
Yes. I have done it. Please have a look.
S.K
OK, I think I found the problem (a stupid mistake on my part which results in a document.write’s not being executed).
can you replace your version of donottrack-min.js with the one on http://blog.futtta.be/wp-content/plugins/wp-youtube-lyte/external/donottrack-min.js? this should solve the problem.
if it does, i’ll push out wp-youtube-lyte (with some other fixed) later today, if not i’ll just have to keep on poking around 😉
I was kind of impatient and pushed wp youtube lyte v0.9.3 out, i’m pretty confident it solves the issues you encountered 🙂
Thread Starter
S.K
(@kichu)
Thanks. It (donottrack) almost fixes everything except the Google custom search code which still plays truant. I haven’t looked at the analytics thing yet.
S.K
arghhhhhhh … really thought I had cracked it. do you use a plugin for google custom search? which one?
and is (was) there an analytics problem as well? what’s going wrong there?
Thread Starter
S.K
(@kichu)
I inserted the Google CSE code myself and added a search form widget on the sidebar. I have just now added the Google analytics. So I’ll have wait for a day to check if it has started tracking.
You can see the custom search still “loading” on http://aimwa.in/ (sidebar) with DoNotTrack on.
Regards
S.K
