404 page not found

Hi Shirster,

I have a few questions regarding the nodes that this is applied to the node this operation would be performed on:

1) Is this content you created (its been written such that you are not allowed to flag your own content)?
2) Does your user have the required permissions to be able to flag content (in the access control)?
3) Is the content type allowed to be flagged?

Basically, any more information you can provide to help me narrow down the problem would be great :)

-BTM

I've run into this as well. I finally realized that it was happening when I tried to report on nodes that I created (I was testing a site). I'm not sure that this is really a bug since the use-case might not be valid. Perhaps rather than giving a 404 error it can give a better message?

Thanks,
pgmillion

Hi,
I also ran into this bug, and got around it by stopping the "Report as offensive" link from appearing on nodes or comments that the user owns. I've attached a patch, although I'm not sure if this is the best solution to the problem.

Rohan

I'll take a look through the code to see where the check goes faulty (its not supposed to be showing the link to the user's own content) and devise a patch for it (thanks for your preliminary patch, Azzor - I'm assuming this also breaks for anonymous user created content - something I had not thought about).

I'll change the flow to send the user back to the page with the content with a message that they cannot report on their own content.

I've updated the module with the patch - should be available with the next release. Please notify if there are still problems.

The error still continues with or without the patch applied. So far what i did was create a test user account and then flagged one of the admin comments. after the flag i was sent to a 404 page not found.

Looks like an issue with it doing drupal_goto($object->link), when link is the result of a l() call. The 404'ed URL includes a url-encoded "path), I think. Debugging now, see if I can figure out a patch....

Patch to switch ->path for ->link, works on our site, YMMV.

Thanks for your patch, Mike. I incorporated a few other things with your patch as well as the issue seemed to be stemming from the comment flagging. Should be out with the next release.