Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.Khalid - this looks like a great module!
Reading from the google web accelerator help for webmasters, it appears that using the post method (e.g. making it a button instead of a link) would reduce the impact of crawlers. Also, using rel="nofollow" might help. In the end there will always be some crawlers that will follow content, but the impact of nice ones can be reduced.
http://webaccelerator.google.com/webmasterhelp.html#prefetch3
| Comment | File | Size | Author |
|---|---|---|---|
| #13 | flag_content_add_confirm_0.patch | 4.25 KB | neclimdul |
| #10 | flag_content_add_confirm.patch | 4.65 KB | neclimdul |
| #6 | nofollow_0.diff | 1.31 KB | greggles |
| #5 | nofollow.diff | 947 bytes | greggles |
Comments
Comment #1
moshe weitzman commentedi think the most consistent and bestest way is to add a confirm page. this gives users a point to reconsider their actions. maybe even restate the site policies on the confirm page.
Comment #2
kbahey commentedI don't want the "flag this" link to be a button (if I can help it).
Would the confirm_form() system.module be the best way to do this?
This way the link stays as a link, and the button is displayed in the confirm dialog only.
Comment #3
gregglesThat sounds reasonable to me to have the button on a confirmation page.
How about nofollow on the link? It's mostly famous for SEO reasons, but also has the intended impact of telling crawlers not to follow the link (for those that respect it).
Comment #4
moshe weitzman commentedthe flag link can remain a link. the button is for the confirm form ... the no_follow attribute is a good idea, but not a requirement. drupal is not so caring about this in general.
Comment #5
greggleswell, here's the nofollow part of it, at least. this was against 4.7 but I imagine it would work against HEAD as well.
Comment #6
gregglesactually, that should be on all three of those links, I think.
Comment #7
kbahey commentedMoshe and Greg,
You now have CVS access to this module.
Feel free to commit whatever patches that make sense.
Comment #8
j9 commentedWould there be any way to create a patch file or a new release w/ this fix? This code addition really helps a site do community moderation w/out bots flagging all nodes.
Or, perhaps, would anyone know the diff command to use to create the patch file from within the module directory?
Thanks - this is a really nice submission.
Comment #9
kbahey commentedI rather have a proper solution for this, a confirmation button.
In other news, I am in discussion with a client who wants a form for the flagging, where they can enter more info (why it was flagged, comments, ...etc.)
If this materializes, then this issue will be fixed by implication.
Comment #10
neclimdulOk, this adds the confirm form and rel='nofollow' to the 5 branch and also has the nofollow hints as optional through a setting as suggested by kbahey.
Comment #11
kbahey commentedCommitted to 5.x and HEAD.
Thanks man.
Comment #12
neclimdulAnd because I'm such a nice guy, here's a port to 4.7
Comment #13
neclimdulpatch...
Comment #14
kbahey commentedCommitted.
Comment #15
(not verified) commented