Vote link is executed by search engines

That is a great idea. I will add the attribute now. Brb.

Actually this will not work.

From Wikipedia

The nofollow attribute value is not meant for blocking access to content or preventing content to be indexed by search engines. The proper methods for blocking search engine spiders to access content on a website or for preventing them to include the content of a page in their index are the Robots Exclusion Standard (robots.txt) for blocking access and on page Meta Elements that are designed to specify on an individual page level what a search engine spider should or should not do with the content of the crawled page.

So what you have to do is edit the robots.txt file that comes with Drupal.

Add these lines:

Disallow: /plus1/vote/
Disallow: /?q=plus1/vote/

Report back on this, please. If that works, I will add it to the module's documentation.

This might be a long term check of course. Please try it and report back in 2-3 weeks. That would be awesome!

Not many people use anonymous voting.

Any progress on this, I have been having the same problem on http://blog.to.it now that I have enabled anonymous voting.

timmillwood, add the 2 lines to robots.txt. It really should fix the problem. And please report back if it does. I do not have a live site that uses plus 1. I cannot test this.

I have added those to the robot.txt but guess it will take a while to filter through.

Will that stop the listings on http://www.google.co.uk/search?q=site%3Ablog.to.it ?

Will that stop the listings on http://www.google.co.uk/search?q=site%3Ablog.to.it ?

Yes.

Robots.txt and nofollow isn't the right solutions - the right solution is to not violate the HTTP-specification of the GET-method and submit votes through POST-request instead. A GET is not allowed to have any impact on the state of the data and letting a GET have that not only makes search engine robots trigger but can also have weird results with caches and similar.

Any progress on this issue...?

I have coded in solutions to this in the themes for the sites I'm using Plus1 on - should be fairly easy to make a patch out of it when I get time.

If any one else has a solution - please don't let that stop you from presenting it though.

Here's a patch that changes the theme function as well as make it more customizable.

The change to the theme layer is that the link is now a button instead and the form POST:s the votes to the backend - which means that no search engines will index it and no cache will stop it from being processed.

This patch is dependent on #696500: Variable misused used to store state.

voxpelli this patch didn't work for me. I have this error

patching file README.txt
patching file jquery.plus1.js
patching file plus1.css
patching file plus1.module
Hunk #1 succeeded at 83 (offset 7 lines).
Hunk #2 succeeded at 259 (offset 5 lines).
Hunk #3 succeeded at 284 (offset 5 lines).
Hunk #4 FAILED at 288.
1 out of 4 hunks FAILED -- saving rejects to file plus1.module.rej

How i can fix this?

I 2nd #12 as I get the same error trying to apply the patch.

Opps, you have to apply the other patch first, as it says in the description.

I've applied the patch, but it breaks the current version of google chrome. The submit button is shown but not clickable. (had a caching issue)

Everything is working and tested

Coding standards: indentation, "elseif".

This also seems to fix the problem in #581032: Not working on IE8.

Do we need to reroll a patch for #16 or can we fix it once we commit?

It is fixed in my copy. Just waiting on commit access.

Committed to 6.x-2.x-dev.