[wp-hackers] CVS: wordpress/wp-includes comment-functions.php,
1.17, 1.18 functions-formatting.php, 1.61, 1.62 vars.php, 1.44, 1.45
Christoph Rummel
bronski at bronski.net
Sat Jan 22 15:34:21 GMT 2005
- Previous message: [wp-hackers] CVS: wordpress/wp-includes comment-functions.php,
1.17, 1.18 functions-formatting.php, 1.61, 1.62 vars.php, 1.44, 1.45
- Next message: [wp-hackers] CVS: wordpress/wp-includes comment-functions.php,
1.17, 1.18 functions-formatting.php, 1.61, 1.62 vars.php, 1.44, 1.45
- Messages sorted by:
[ date ]
[ thread ]
[ subject ]
[ author ]
On 22.01.2005, at 15:48, Owen Winkler wrote:
>> It's not that simple...
>>
> Agreed. Having a look at the intended code, the
> nofollow stuff needs to be more isolated in order
> to work. It's included directly in kses for one. You
> can't turn it off in there without disabling all of the
> other useful things kses does.
>
> I don't have a problem with spreading nofollow all
> over commenter-added links as a default. It will protect
> novice bloggers from poisoning the well. But more
> advanced hooks for plugin authors to augment the
> nofollow routines would be well appreciated. As it
> stands, you'd have to filter the comments after the
> nofollows were inserted to remove the ones you
> didn't want. Ugly.
That is what I did - just str_replace all occurrences of
nofollow out of comment_text and get_comment_author_link.
http://bronski.net/data/nonofollow/
Very rudimentary, simple, but if you don't want to do
rel="nofollow" it does just that.
Chris
- Previous message: [wp-hackers] CVS: wordpress/wp-includes comment-functions.php,
1.17, 1.18 functions-formatting.php, 1.61, 1.62 vars.php, 1.44, 1.45
- Next message: [wp-hackers] CVS: wordpress/wp-includes comment-functions.php,
1.17, 1.18 functions-formatting.php, 1.61, 1.62 vars.php, 1.44, 1.45
- Messages sorted by:
[ date ]
[ thread ]
[ subject ]
[ author ]
More information about the hackers
mailing list