| Project: | Node Comments |
| Version: | 6.x-2.0-beta6 |
| Component: | Code |
| Category: | support request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Issue Summary
We have a forum on our site that uses nodecomments (and advanced forum). Generally speaking it works perfectly. However we've noticed three or four times over the past few months since we launched the site that once in a while a reply to a post will wind up as a regular drupal comment, not a nodecomment. As a result, it winds up in a kind of limbo where it's not displayed on the site. If the user re-posts, that new version of the same post works every time.
I can't find anything in the logs that might give me a clue as to how this is happening. Does anyone have a suggestion for where I should begin trying to track this down? It's so infrequent that we have very little data from users, but in every case I've contacted the end user and it doesn't sound like they're doing anything unusual to get into a state where something is different on the user facing side.
I'm completely baffled.
Comments
#1
Did you make sure the (core) comment module is disabled?
As stated on the NC project page:
To use this module you need to first disable comment.module. The two are, and will remain, completely incompatible. If you don't disable comment module before enabling Node comments module, the module should do this for you.
edit: Above applies only to version 1.x and since you're using 2.x (which I overlooked initially) it doesn't apply to your setup.
#2
Correct - that doesn't apply.
And we're actually using regular comments in some places (in some content types, we don't need the benefits of node-based comments). so, disabling the core comment module isn't an option.
#3
So here's an update - It seems that the end users who are posting these comments that wind up as regular comments are getting a different form. I suspect this because I've noticed that some of the comments have subjects. custom subjects are disabled for our forums (which should be using nodecomments exclusively), so if they're typing something in (or not, and getting the default "(No Subject)") then they must be getting the wrong form in the first place, no?
We are using Panels to display the pages that have forms, if that has any bearing on this...
#4
What version of Node Comments are you running ?
Are you sure you have comments and nodecomments for the same (commented) content type ?
#5
Yes - definitely regular comments for a handful of seemingly random replies to our forums. We have hundreds of posts, and they're all node comments except for a few that slip through. this does not just happen on our forums though - it has also happened on other content types.
If I look at the list of Drupal Comments, I can see the ones that should have been nodecomments, so they're definitely there, just the wrong kind.
We are planning to upgrade to Beta 3 soon (we're in the process of preparing a fairly big set of upgrades to the site right now, so it should go live in a month or so). Right now we're on Beta 1.
#6
Ok. Please try latest release or dev.snapshot and come back.
#7
no answer
#8
I have also encountered this problem! At first, it was just with spammers so I assumed they were using standard URLs in their bots to post Drupal comments. But lately, it's started to happen with normal users. If only I could sit next to them while they replied on my forum, to really see what they are doing to get to the old form!
Anyway, attached is a patch that denies access to normal "comment/reply/%node" page for node types that are using nodecomment. I also considered overriding the page callback and doing drupal_goto() to the node add form. But this seemed simpler. What do you think?
Regards,
David.
#9
Denying access is not a solution. User will get access denied page and still won't be able to comment, and the goal is to allow them to do that, instead of just blocking. I advise to research why and how do you get wrong comment forms in the first place.
#10
You are right! It was just the easiest thing to code up.
Attached is a new patch that isn't intended for inclusion, but for helping people track down the problem. Instead of denying access, it redirects the user to the correct URL and puts a message in the log. All log messages include the "Referrer" which will hopefully point to the culprit.
Thanks for your advice!
Best regards,
David.
#11
I think you could get this because of the poor logics inside nodecomment form panels pane. I've fixed it in 3.x
#12
2.x has many bugs like this one, because of hacks and inconsistency. 3.x will be much better.
#13
Automatically closed -- issue fixed for 2 weeks with no activity.
#14
Using my patch #10, I finally found out how to recreate this dependably!
My site uses notifications, which sends links to the site that look like: http://mysite/comment/reply/5529
If a user goes to that URL while logged out (ie. as anonymous user), they get access denied. When they login (ie. via the login blog), it will be submitted to this link:
http://mysite/user/login?destination=comment%2Freply%2F5529%23comment-form
Which redirects them to this URL on successful submit of the form:
http://mysite/node/add/forum-reply/5529#comment-form
I'm not sure why the normal comment/reply/!node redirect doesn't kick in, but at least I can recreate this problem 100% of the time now.
When I get a chance I'll dig into the code.
#15
2.x is not supported by me anymore. If you really want to help, try 3.x and see if it has same problems.