JavaScript Errors with the Share This Widget

Hi

I think I have cracked it.

I did a compare with other browsers and it was only Chrome that was throwing up these blocked errors. FireFox was fine, even though that is the browser I have with all the plugins.

I went through all the few plugins I do have on Chrome, thinking it would be something like KB SSL Enforcer or some “force” HTTPS security plugin (even though I disable them for my own sites).

However I found it was the MaskMe (https://chrome.google.com/webstore/detail/maskme/dpkiidbpeijnaaacjlfnijncdlkicejg) plugin that was causing the issues.

When I turned it off the only common JS error between Chrome/FF was this, which always appeared first in the console.

TypeError: document.body is null in
http://widgets.digg.com/buttons.js (don’t know if this is related to your plugin) but I only use Jetpack for the social media icons now whereas I used to use Share This.

I thought MaskMe was only supposed to protect my passwords and emails. I didn’t realise it was doing anything to block site to site access, or anything related to protocol security, but it seems to be doing so for some reason.

I cannot find anything in the settings to set it to allow http to https frame display. Or anything related to “allowing” this site etc but it seems to be causing the problem.

Anyway turning this plugin off made all the errors apart from that digg.com one go away.

Why it is doing this I do not know but I thought I would let you know.

Thanks

Rob Reid

Hi Richard,

I have checked all my plugins and yours is the only “social media” one I am using that outputs buttons on the page (below my content).

Also the reason I thought it may have been your code is that in the source, I can see an inline script in the header. It is this script which is causing the error. Also directly below the code is a reference to your CSS file e.g

<script type="text/javascript">
	document.documentElement.className = 'js';
</script>

<!-- This site is optimized with the Yoast WordPress SEO plugin v1.4.15 - http://yoast.com/wordpress/seo/ -->
<meta name="robots" content="noodp,noydir"/>
<!-- lots more META tags -->
<!-- / Yoast WordPress SEO plugin. -->

<script type="text/javascript">
(function() {
	var s = document.createElement('SCRIPT'), s1 = document.getElementsByTagName('SCRIPT')[0];
	s.type = 'text/javascript';
	s.async = true;
	s.src = '<strong>http://widgets.digg.com/buttons.js</strong>';
	s1.parentNode.insertBefore(s, s1);
})();
</script>
<meta content="UkTipster v.3.5" name="generator"/><link rel='stylesheet' id='jetpack_likes-css'  href='http://www.mysite.com/wp-content/plugins/jetpack/modules/likes/style.css?ver=2.4.2' type='text/css' media='all' />

However when I look in the source of the theme the PHP code is just this.

<script type="text/javascript">
	document.documentElement.className = 'js';
</script>
<?php if ( is_singular() ) wp_enqueue_script( 'comment-reply' ); ?>
<?php wp_head(); ?>
</head>

As you can see there is no hardcoded JS between the code that does document.documentElement.className = ‘js’; and the offending script, just PHP.

Therefore it must be a plugin outputting the JavaScript and I guess the problem is being caused by the JS running too quickly BEFORE the actual DIGG buttons in the share button option has had time to load into the source.

If I could find the offending plugin (if it’s not yours 🙂 ) then at least I could wrap it in a document.ready or move it to the bottom of the page. Even run a looped test for the element it is trying to apply the style on before loading etc.

Are you sure that your own JavaScript that loads up all the other social media code doesn’t include code for Digg?

I cannot find any other widgets that could be to blame and there are no comments being outputted to help diagnose the offending code.

Thanks for your help anyway!

Hi Richard

The website is http://www.ukhorseracingtipster.com

You can see an example of the source I am talking about here

UK Horse Racing Tipster News

Notice the inline SCRIPT just after the YOAST SEO comments?

I did have a combination of WP Super Cache and WP Minify working together which was beating the hell out of another site with W3 Total Cache behind Cloudflare. However for some reason WP Minify has stopped working and I cannot use W3 Total Cache (to minify the HTML/CSS/JS) as it caches too well!

I auto post a lot of content by feed OR email and need to check the HTML source before posting to prevent duplicate content but I get cached pages back which prevent it from working – AAH!.

It was working so well WP Minify & WP Super Cache, I’ve contacted the plugin author (WP Minify) but have not heard back from him.

I have de-activated all plugins, re-actived, deleted, all combos, but no errors and no help. I really hated debugging other peoples plugins which is the whole reason I started making my own. I really don’t want to have to make my own minify plugin!

Anyway sorry to get off topic. I just felt a need for a Sunday morning rant 🙂

Any help you can give would be much appreciate – I can code so if you need me to do anything let me know.

Thanks

Rob

I am not sure what you are looking at if you cannot see the comments or digg.js.

View the source of this file (in Chrome) > http://www.ukhorseracingtipster.com/2013/09/frances-vorda-to-be-ridden-by-olivier-peslier-in-cheveley-park-raid/

I get from lines 42 – 55 (not logged in as u user)

<meta name="twitter:creator" content="@ukhorseracetips"/>
<!-- / Yoast WordPress SEO plugin. -->

<script type="text/javascript">
(function() {
	var s = document.createElement('SCRIPT'), s1 = document.getElementsByTagName('SCRIPT')[0];
	s.type = 'text/javascript';
	s.async = true;
	s.src = 'http://widgets.digg.com/buttons.js';
	s1.parentNode.insertBefore(s, s1);
})();
</script>
<meta content="UkTipster v.3.5" name="generator"/><link rel='stylesheet' id='jetpack_likes-css'  href='http://www.ukhorseracingtipster.com/wp-content/plugins/jetpack/modules/likes/style.css?ver=2.4.2' type='tex t/css' media='all' />

I’ve also updated to v2.5 of JetPack.

As for the two jQuery loads I am not sure which plugin isloading the old version, it is certainly not hardcoded in the source of the header or footer.

Can you tell me the difference between de-avtivsting a plugin and deleting it? Will any source code, options, timer etc remain in the system or will they all go when de-activated?

At the moment my full list of “activated” plugins sre:

Akismet
Audio player
Cookies for Comments
Fuzzy SEO Queries
Jetpack by WordPress.com
Limit Login Attempts
LinkWithin (client side, related posts, low load nice pictures of related srticles)
Postie (a custom version I built to correct errors within it)
Quick Page/Post Redirect Plugin
s2Member® Framework
Sidebar Login
SimplePie Core
Strictly Auto Tags (my own custom latest version as I wrote it)
Strictly Google Sitemap (same as above)
Strictly System Check (same as above)
Strictly TweetBot (same as above)

— all my plugins dont make use of JS client side scrpts

WordPress SEO
WP-DBManager
WP-o-Matic (a very custom version I made of it – no JS)
WP Autoresponder
WP Autoresponder to s2member Integration Plugin
WP Minify
WP Show IDs
WP Super Cache
WPtouch
WP Widget Cache (just caches sidebars, tag clouds etc)

Server is 2GB RAM Debian, running APC and MySQL ISAM. Tuned with 3+ MySQL tuners reguarly.

I am on holiday from work for a week+ now. So I might not repy for a while.

Thanks for any help.

Yep definitley Jetpack, I put it back on and now the script is back. It must be included when you drag options for sharing into the “share” box. It says “Services dragged here will be hidden behind a share button.” so I reckon if you throw digg behind there it would add that code.

That’s ok!

Do I get to be a “happiness engineer” now? 🙂

Gutted, I know you work from home, around the world, but it seems like your side of the pond gets all the benefits.
I don’t know if I could work alone constantly and would probably miss an office environment.
All good to think about though!