| 1:24 pm on Jul 27, 2011 (gmt 0)|
<!-- Place this tag where you want the +1 button to render -->
<!-- Place this tag after the last plusone tag -->
po.src = 'https://apis.google.com/js/plusone.js';
var s = document.getElementsByTagName('script'); s.parentNode.insertBefore(po, s);
I don't understand what they mean by the instruction I bolded above. Does it mean to put it right after the <g:plusone></g:plusone> line or where else? Maybe it's just too early in the day for my brain to think.
| 1:32 pm on Jul 27, 2011 (gmt 0)|
Ice, yes that is what it means.
| 4:23 pm on Jul 27, 2011 (gmt 0)|
@icedowl, Put it just before your closing </body> tag.
| 4:28 pm on Jul 27, 2011 (gmt 0)|
The new asynchronous code is indeed faster but there are still two major issues for me:
1. To increment the +1 count, the visitor must have a Google account, must be logged in to their Google account and must have a public profile. I've estimated that approximately 20 percent of my site visitors have a Google account but I have no way of knowing the number that are actually logged in and have set up a public profile.
2. The +1 code does not validate as W3C HTML 4.01 Transitional. The basic code when put into a DIV with class="g-plusone" does validate but the other parameters such as data-count="false" and data-size="standard" do not validate.
| 5:13 pm on Jul 27, 2011 (gmt 0)|
Warmglow thats the problem with google +1 its never validates but does this create any problem?
| 5:53 pm on Jul 27, 2011 (gmt 0)|
I removed it when I saw how slow it was.
Google did not live up to their name on this one. After all that PR about page load speed, they send us a code that is not even polished and release an update 2 month later..
This +1 button should not have been release until it is ready !
That kind of mistake is what will kill this project...
They have too much going on, nothing is good, lots of things are ok, but none are good enough to make a real difference..
very sad coming from Google
Good news for us :) Google might not be as capable as we all thought !
| 6:27 pm on Jul 27, 2011 (gmt 0)|
|Warmglow thats the problem with google +1 its never validates but does this create any problem? |
Yes, it is a problem for me. I validate every edited page and when validation fails, I am slowed down while I check to see which lines of code did not validate. This, coupled with the fact that only a small percentage of my site visitors can actually increment the +1 count make it a "no go" for me, for now.
| 6:56 pm on Jul 27, 2011 (gmt 0)|
I'm still removing it when I get around to working on the site where I've added it. So far only one click and that came from the serps not from my site...
so far the + one is not awesome
And I don't like the name either.
| 7:15 pm on Jul 27, 2011 (gmt 0)|
Same boat, it slows down the website and when we did testing, no one clicked on it. Plus 1 can not compete with the facebook button.
| 7:39 pm on Jul 27, 2011 (gmt 0)|
1. To increment the +1 count, the visitor must have a Google account, must be logged in to their Google account and must have a public profile.
Isn't the same true of the Facebook and Tweet buttons as well? That is, in order to Facebook Like something, you must be signed in to Facebook, and in order to Tweet something, you must have a Twitter account. The button doesn't make any sense otherwise, because then you could just +1 your own page a million times.
| 7:52 pm on Jul 27, 2011 (gmt 0)|
I realize G's scheme is new, and iffy, but multiple +1 pages with 0 counts look as sad as multiple blog entries with 0 comments. Might as well hang a sign saying, "Not worth reading."
Speaking of counts... Maybe the no-count button styles would render more quickly. (If nothing else, their locations would look less unpopular.)
| 8:01 pm on Jul 27, 2011 (gmt 0)|
I took the count off the plus one button; it looked silly with 3 plus ones next to almost 4000 Facebook likes.
It's good that they released a faster version; I can't help but wonder why they didn't just wait to announce it till they had the asynchronous version ready to go, though.
(The validation issue is a PITA, but the FB OGP stuff doesn't validate without jumping through hoops either)
Normal people aren't using +1 because they don't know what it is. But people on Google+ are using it all over the place. So maybe Google is hoping that as more and more people get into Google+, they'll get acclimated to the +1 button there, and start using it elsewhere.
Hey, I know it's convoluted and ridiculous. But it's a theory.
| 2:18 am on Jul 28, 2011 (gmt 0)|
How do you ditch the count on tall buttons? It's the only one where the blue +1 image is the right size for my site but apparently the only one I can't remove the count from.
|The +1 button code requires a script from Google's servers. You can include this script using either http:// or https://, like this: |
If your web page uses https://, some browsers and verification tools will show an error when any assets on the page are called via [....] If your site serves pages via https://, make sure that the +1 button code on those pages also uses https://. (In fact, it's fine to use https:// in the button code for all pages, even if they are only served via [.)...]
| 9:43 am on Jul 28, 2011 (gmt 0)|
Wow, that sounded harsh when I re-read it, which isn't the sentiment I was wanting to convey so...
| 2:09 pm on Jul 28, 2011 (gmt 0)|
does this mean if we set +1 button up a few weeks ago with the header code, that all that can now be discarded with?
| 11:51 pm on Aug 1, 2011 (gmt 0)|
I pretty sure also that apple mobile clients wont cache anything over 25kb although im not sure about that.
" - " 1