My Add-to-Any is broken :(
When I press on any of the Standalone Service buttons, it takes me to this page:
The error at the top of that page says "Service not found"
This is from my blog: DanLikesThis
In addition, I am not getting the three main Standalone Services of Google+, Facebook and Twitter on the posts after the 1st post.
http://wordpress.org/extend/plugins/add-to-any/
I've just updated to 1.0.1 and updated WP to 3.3.2 and I've lost my Standalone Service buttons altogether (they're activited in my Settings, but not appearing at all on my site).
My site is http://www.reviewedmusic.com
Any ideas/alternative services that I could use while this gets fixed?
1.0.1 seems to be stable. Most problems with a stable plugin release will be host issues with an upgrade or a conflict with another plugin or theme. Best way to troubleshoot first is by temporarily switching themes and/or disabling other plugins.
@dcpdad can you reenable so we can help troubleshoot in this space?
@nilshay your site has a larger issue that's causing this one. If you view the source of your site you'll see some duplicated code in your <head> section. The duplicate code is partly mangled which is preventing the plugin's main resource from loading. Another plugin is most likely causing this.
@micropat - thanks for looking into it - it is reenabled at DanLikesThis
Any updates on what the problem is? Please.....
@dcpdad after a quick look I have a hunch that it's a conflict with your Twitter "Follow" button. Can you try temporarily disabling either the Twitter "Tweet" button or your Twitter "Follow" button to see if that resolves?
@micropat - thanks for your feedback. It IS the Twitter "Follow" button. Now - how do you suggest we get both? The code behind the Twitter button (which came FROM Twitter) is:
Follow @DanLikesThis
<script>!function(d,s,id){var js,fjs=d.getElementsByTagName(s)[0];if(!d.getElementById(id)){js=d.createElement(s);js.id=id;js.src="//platform.twitter.com/widgets.js";fjs.parentNode.insertBefore(js,fjs);}}(document,"script","twitter-wjs");</script>
@dcpdad will see this week if this scenario is something we can workaround from our end.
@dcpdad should be fixed now.