1 weevil Mar 08, 2005 18:30
3 weevil Mar 08, 2005 19:17
So as far as the future posts go, we're just not checking to see if it's a valid post ID before we enter the comment against it. This should be relatively easy to fix.
As far as a crap shoot post, I guess it won't be easy to trap those. If it hits a valid post ID, the application won't know any better than to let the thing in.
If I ever get any spare time I might take a look at this and see if I can plug the future/draft hole, anyway.
Thanks for the info...
4 village_idiot Mar 08, 2005 19:25
Weevil wrote:
So as far as the future posts go, we're just not checking to see if it's a valid post ID before we enter the comment against it. This should be relatively easy to fix.
youre welcome, and yes, thats correct.. i beleive the same hold true for comments and trackbacks,
not only can you get a trackback to a draft post, you can get a trackback to a post in the future .. it, the latter, is already documented on this forum. Its an unresolved issue as far I know. It was also an issue in WP, but they have resolved it, if i reme correctly. Im bored so i will hunt around for their fix, and maybe a similar one can be adopted for b2evo.
edit: I did find the WP fix, Ill see what I can do about making that implementable in b2evo.. trouble is it will be largely untestable unless I want to build a form to remotely submit comments/trackbacks.
If anyone else is interested in doing this, the corresponding fix for WP is here> http://www.tamba2.org.uk/wordpress/spam/#seven
Once again, thats a WP fix, do NOT attempt to fix a b2evo blog using that, it wont work, and youll fsck your blog looking for the code.