Spam module don't work on comments using the project issue tracking.module

you delete comment spam by click on the delete link as User 1

you delete node spam by editing the node itself and deleteting or going to adminsiter -> content

if you have the spam module installed and enabled, something tells me you don't have it set up properly otherwise your spam should be detected and unpublished.

I also don't understand why you are submitting this issue against the project module. your spam has nothing to do with the project issue module.

as such I am closing this issue.

actually it may be best to move this to the spam module issue query as a support request

you have a problem with the spam.module not the project issue tracking.module. The two modules have nothing to do with each other.
Again, I don't believe you've found a bug, I don't believe you have the spam.module correctly set up.

I don't have any idea why you believe the search is broke ?

without more information on all your settings for the spam.module it is difficult to help.

To help stax get his point across.

The spam.module does not seem to work with project issue tracking.module. Stax is getting spam comments on his issue query on his site.

He's never stated what version of the spam.module is in use and I moved this here from the project issue tracking module query.

@ Stax please adjust the version to reflect the correct version of the spam.module in use.

adjust title to better reflect the problem stax is having.

Then realistically they are seperate issues and probably should have been filed as such.

1) The spam.module would be repsonsible for the spam and have to handle spam in the issue query I believe. even though the issue query is a custom type comment.

2) with regards to searching the issue query, here on drupal.org you have a seperate search to search issues. see: http://drupal.org/project/issues/search/ this is part of the project.module and you should be able to do this on your site too. what do you have at yoursite.com/project/issues/search ?

also of note: your search is for the word lesbian and the search result is finding the correct comment attached to the correct node. That being said, I'm not real clear on what the problem you see with search is ?

3) with adminsitrator privledges comments on issues can be deleted. Are you sure the the link isn't just mising from the theme in use ? have you checked in a default theme ?

I can delete comments here on drupal.org's issue query, so this part doesn't make much sense as to why you can't using the project.module ? do you not have a reply and edit link at the bottom of each comment ?

the delete link should be sitting right next to the edit link and reply link at the bottom of each comment.

I'd really like to help you out in this situation. It'd difficult when you are balling up 4 issues into one. Consider filing seperate issues or start a forum thread and close this issue. When issues are all balled together it leads to confusion.

That unfortunately means my visitors will be confronted with dirty porn spam until the new version is available.

That being the case, you can remove them from the DB manually.

Feel free to move this back to the project issue tracking query if you like then.

Actually I'll do it for you.

Right. the 5.x-1.* series and all previous versions of project_issue use a weird, custom pseudo comment system for issue "followups". one of the primary efforts of the 5.x-2.* series was to convert those to real drupal core comments (http://drupal.org/node/18920). one of the many reasons for this was so that you could more easily edit/delete inappropriate followups, and use other modules that operate on comments directly (like comment_upload, etc).

this isn't technically a bug, since everything is working as designed. the problem is just the weird decision years and years ago (long before my time) to split off issue replies into their own special "followups" instead of using real comments.

anyway, we will not be fixing this particular issue in 5.x-1.*. however, we might take this whole issue as a good reason to consider a feature freeze on project_issue 5.x-2.*, now that followups are real comments, and do the heavy lifting for views support in a new 5.x-3.* series.

cheers,
-derek

Yes, it's risky, especially if you don't know SQL. Sorry.

5.x is not broken and doesn't really need to be fixed. As dww pointed out in #14 above, if you use the project issue 5.x-2.x branch, project issue followups are real Drupal comments. There's even an official project issue 5.x-2.0 release.

@stax: I am clearly dreaming: http://drupal.org/node/216121

Just below the downloads table there is a link to "View all releases". If you click on that, you get all releases.

In this particular case project issue 2.0 is not the "recommended" version to use. As far as I know it is functional and stable, and it is the version running on drupal.org itself. I believe the reason that it is not technically the recommended version to use yet is that it was released as part of a security fix in project issue, and we weren't quite ready to actually create the 2.0 branch at the time. Hopefully by the end of the week we'll be able to put together a project issue 2.1 release and that will probably become the recommended version, and therefore it will appear on the release download table.