Posted 1 year ago #
I don't know that much about iFrames but the fact that I can't use the most recent YouTube player emebed codes and that Facebook / javascript plugins (meaning embed codes generated from those service's sites) act goofy a lot as does google adsense...
I know it is not WordPress's job as a piece of software to handle this but It would be totally awesome if it did it better and take a lot out of the white-knuckle and cringing out of my life.
Thank you for your time.
You don't need to use YouTube's embed code.
Paste the URL into your post (literally just paste the URL, no code) and it will automatically put the video in. If you want to adjust size and width, wrap it in the [embed] short code.
Posted 1 year ago #
@Ipstenu
That is great to know, thank you!
The other Javascript on the site is all conflict-y, I guess maybe I need some professional guidance on that...
(I mean stuff like this is happening to us http://www.google.com/support/forum/p/AdSense/thread?tid=18890327279dad00&hl=en )
I use the Google Analytics plugin and don't have any issues. Are you using the 'new' (as of like... last year?) code from Google?
Posted 1 year ago #
@Ipstenu
Thank you for talking me through this! Yes I am using the new code and am impressed by how easy and slick it is.
I'd like to clarify my issue here:
I found that the Javascript that wasn't working most recently on my site, the AdSense, was due to the fact that it was in the post loop , and was registering it's Javascript and messing up the other ads, despite being excluded from the homepage via the theme and some Custom CSS. Tweaking the PHP so that the ads were single-post page exclusive fixed that up nicely.
It now looks like everything on the page is working, despite the fact that it throws JavaScript / JSon errors like a rapper in a strip club. (I got over most of these by forcing the Facebook Javascript to load in the header asychronously with some custom (non-plugin) code but they still showing up in the background in Chrome, etc.).
I guess this was a dumb thread to start because I'm just complaining at this point, being OCD about the errors while simultaneously not understanding JavaScript enough to understand why Chrome / Safari gets so angry at them has taken its toll ...lol.
This topic has been closed to new replies.
