From Jeremy:

I just tested again, and I'm still getting the error. Indeed, marking a user as spam a second time does indeed mark his as spam. After that 'mark as spam' and 'mark as not spam' work as expected, though I see the error each time. I'm using the latest version of the spam module code checked out from CVS (cvs update -dP). The only thing I've not (yet) tried is dropping my database and using a fresh installation, but I'm not aware of any relevant database updates.

Screenshot attached.

The steps I used to get here:
1) as uid 1 I went to admin/user/user/create and created a test user
2) I clicked on the new user to view its profile
3) I click 'mark as spam' on the user's profile

I repeated these steps to create a new user, and saw the same error.

CommentFileSizeAuthor
#2 notices.patch6.37 KBkilles@www.drop.org
spam_error.png28.92 KBgnassar

Comments

gnassar’s picture

gnassar commented

Hey, Jeremy --

followed those exact steps, and still not seeing the problem.

Any particular roles selected for the user? I left all non-required fields blank.

Beyond this, I'm not sure why we'd be getting this. I'm thinking maybe, dump the value of $string in _bayesian_tokenize (after line 149) and see what it's pulling as content?

killes@www.drop.org’s picture

killes@www.drop.org commented
Status: Active » Needs review
StatusFileSize
new notices.patch6.37 KB

Here's a patch that addresses this and other similar errors.

jeremy’s picture

jeremy commented
Status: Needs review » Reviewed & tested by the community

Looks good, thanks Gerhard!

killes@www.drop.org’s picture

killes@www.drop.org commented
Status: Reviewed & tested by the community » Fixed

committed

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.