Cannot post replies

[Greymantle]

getting a general error about word matches

[Laureana]

You are not alone... http://mboards.eqtraders.com/phpBB2/viewtopic.php?t=2495

[Ngreth Thergn]

I have turned on Debug mode.

Please post a full error as soon as you get the error (I want to turn debug mode off again asap)

[Greymantle]

well apparently the replies were being posted. I just got an error message so i thought they were not going through. This resulted in 5 replies t oone post in the fletching forum.
I did go back and edit them, but could not delete them.

[Ngreth Thergn]

Link please and I will clean them

[Greymantle]

here ya go thanks.

http://mboards.eqtraders.com/phpBB2/...pic.php?t=2641

[Ngreth Thergn]

someone cleaned it

[Dunthor Warsmith]

<center><b>General Error</b>Could not insert new word matches</center>
whimper. Was a long post too

[Kehvrynne]

I sort of officially hijacked http//mboards.eqtraders.com/phpBB2/viewtopic.php?t=2495this topic</a> in Primal Screams for troubleshooting information.

[Verdandi]

I haven't had this problem yet, and it's not for lack of replies....

*knocks vigorously on her wooden desk*

[Greymantle]

error merssage

This is what i get when posting a reply. It does howerver attach the reply to the thread intact.



General Error

Could not insert new word matches

[KyrosKrane]

Two thoughts on the matter; I'm sure you've already considered these, but I'll post anyway.

How do the boards handle the search function? Does it try to identify key words in the post and log them to some kind of index in the database? That would speed up searches, and I believe it's a common way to implement searches on bulletin boards. That's the first thing that popped into my mind when I saw the "cannot insert new word matches" error.

Next, about the Line 119 error: here's how I'm reading it. Line 119 is trying to save (or update) some information to the database. I'm guessing, based on my experiences, that this line tries to update the "last post date" information for the thread. For whatever reason, this fails, and the line generates an error message and sends this out to the browser immediately.

Normally, all the output is cached and sent out to the browser in one shot after all the processing is complete. This allows the page to change headers or even wipe the output and prepare new output later in that same page. This is what's happening in lines 449-451. The page is trying to update the HTTP headers for the page.

However, the error in line 119 forced the output to be sent to the browser, which also sends the HTTP headers. Since the headers must be sent before any page data, lines 449-451 fail and generate the three additional errors.

Hope this helps, or at least gives you some ideas on where to search for the cause.