Closed (won't fix)
Project:
Drupal core
Version:
6.8
Component:
comment.module
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
19 Aug 2008 at 19:40 UTC
Updated:
13 Feb 2012 at 08:34 UTC
After upgrade to 6.x.1.x-dev after update to D6 i get Internal Server Error when trying to post/edit comment.
Comments
Comment #1
gregglesCan you look in your apache and/or php error logs and see what messages it shows?
Comment #2
lomz commentedHow do I do that?
Comment #3
gregglesIf you are unsure, contact your hosting company.
If this is in MAMP or XAMPP or something, look in the logs directory or search the documentation.
Comment #4
lomz commentedSorry, no access to the logs
Comment #5
gregglesThen there's almost nothing I can do, unfortunately.
What operating system and version of PHP and what database are you using? If you don't know, contact your host.
Comment #6
lomz commentedMy ISP told me that the error showed:
Comment #7
gregglesWell, I just committed 2 small changes to comment_notify.module 6.x branch that removes a newline at the end of the file which can sometimes cause this problem and also changing to a more Drupalish style of returning the page content instead of printing the theme() function.
So, I'm somewhat hopeful that those will fix it. Otherwise, I could really use your help on this:
1) what is the operating system and version of PHP that you use?
2) If you can, try commenting out different parts of the "comment_notify_comment" function and see if the problem goes away. That will help pinpoint which bit of code is causing the problem and I can then review that area more closely.
Comment #8
lomz commented1.:
MySQL: 5.0.45
PHP: 5
OS: Think is Ubuntu 8.04 or 7.10 or similar.
2.: I will test it as soon as I see it as downloadable.
Comment #9
gregglesWhich specific PHP5.?
I've used the module on Ubuntu 7.10 and 8.04 with the version of PHP5 that comes with Ubuntu and it works fine.
Comment #10
lomz commentedhow do i find the version number?
Comment #11
gregglesAsk your host. Or go to http://example.com/admin/reports/status/php
Comment #12
lomz commented5.2.3-1ubuntu6.4
Comment #13
lomz commentedI tried commenting out each of the separate "underfunctions" but still the same error, then I tried to comment out the whole function but still same error.
Comment #14
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.
Comment #15
lomz commentedSorry, not fixed, I didnt get any response on my last comment, and I tried with the latest version, still same error.
Comment #16
gregglesOk. Can you try commenting out more and more parts of the module file and see if the problem goes away? I still don't have an idea about what causes this.
Comment #17
gregglesComment #18
lomz commentedUninstalled the module completely, that fixed it, but kind of anoying to have to remove all the information.
Comment #19
gregglesWithout any feedback or consistent set of steps to repeat the issue I don't see the benefit to keeping it open. If the issue remains even after commenting out the whole file then it is not caused solely by this module...
Comment #20
kenorb commentedI've got the same problem when replying the comment, but I'm not using comment_notify module;/
Comment #21
greggles@kenorb - that's just further proof that this issue is not related to comment_notify. I suggest you open a new bug in the core queue. You will likely have to debug it yourself since it is clearly not very common.
Comment #22
kenorb commentedIt easy to say, but it happen on production environment, where I can't debug it.
Comment #23
asimmonds commented@kenorb - greggles asked you to open a NEW bug in the core queue, not reopen/reassign this bug.
Comment #24
kenorb commentedBut I think it can be the same issue, so for what for? To duplicate the problem?
Comment #25
dpearcefl commentedClosing this issue because of a lack of activity.