Re: [Tikiwiki-devel] blog posts trackbacks

[<gun...@nv...>]

Thanks for the update. I was the one who reported the issue. As a =20
temporary fix against sping (spam pings) I had disabled trackbacks =20
inside the code. (return false;)

Den 20. jun. 2006 kl. 21.55 skrev bertrand Gugger:


> The trackback pings for blog posts are now considered as comments.
> So they are allowed only if :
> - the feature blog is enabled
> - the feature blog posts comments is enabled
> - the blog allows comments
> - anonymous have the permission to post comments (is this one too =20
> strict ?)

That works for our users, if comments and trackbacks can be deleted =20
by the blog owner. (I'll update soon.)


> However, some users could like to have only one between comments and
> pings allowed.
> It could be advisable to separate the perms for those 2 features.
>
> That could be done without changing the data scheme:
> * for the allowance on the per blog basis, by extending the blog's =20
> allow
> comments which is now y/n in y/c/t/n where y=3Dboth, c=3Dcomments only =
,
> t=3Dtrackback only , n=3Dnone (that is backward compat)

This sounds good, and is the solution that I would go for. That way, =20
we can have, on the same site, this use case:

Anonymous comments is off (global setting).
Blog A allows only comments from registered users, not trackbacks.
Blog B allows comments from registered users and pingbacks from anybody.

> * for the general permission by adding a tiki_p_blog_pings or =20
> certainly
> better as it applies only for anonymous a $feature_blogposts_pings

The problem is that the permission system kind of breaks down since =20
trackbacks_from are only added by users if the blog is on the same =20
site. Most blogs like to have trackbacks by other sites. A site-wide =20
or per-blog system of whitelists, black lists, and other filtering of =20=

trackbacks would be needed to tackle this, and that would be a re-=20
design for HEAD, not a fix for BRANCH-1.9, I think.

--
Regards , Vennlig hilsen
Gunnar Ren=E9 =D8ie, MSc. IDI/NTNU
PGP public key available