Fatal errors, fatal errors everywhere!
| Comment | File | Size | Author |
|---|---|---|---|
| #10 | forum.patch | 2.53 KB | mfb |
| #1 | 613278-forum-borked-D7.patch | 1.11 KB | dave reid |
Fatal errors, fatal errors everywhere!
| Comment | File | Size | Author |
|---|---|---|---|
| #10 | forum.patch | 2.53 KB | mfb |
| #1 | 613278-forum-borked-D7.patch | 1.11 KB | dave reid |
Comments
Comment #1
dave reidComment #4
chrishaslam commentedPrior to this patch upon replying to a forum post I was getting the following error
After applying the patch the error is gone and I can successfully reply to a forum post. Did this error occur elsewhere and is further testing needed?
Comment #5
heather commentedTested.
Me too. Before I applied the patch, I got same error as chrisred when trying to reply with a comment on a forum topic.
Applied the patch and it works! Well done Dave Reid :)
Comment #6
jim0203 commentedThis gets a pass from me too. Fixes a misconstructed db_query_range() call. RTBC.
Comment #7
damien tournoud commentedSorry for the error, that was me...
Let's extend the code coverage a little bit.
Comment #8
pwolanin commentedDo you have a suggestion for the added test coverage? Adding a comment with forum module enabled might be enough. If not, let's just fix this critical error asap and come back to it.
Comment #9
jim0203 commentedAgree with @pwolanin - I'm sure I've seen Dries commit a few crucial patches to HEAD and then mark the issue as "Needs Tests".
Comment #10
mfbAdded one additional bugfix and tests for 1) adding comment to forum topic and 2) editing forum topic that has a comment.
Comment #11
dries commentedConfirmed that this is a bug, and that the patch solves it. Committed.