Internal Server Error when trying to post/edit comment
lomz - August 19, 2008 - 19:40
| Project: | Drupal |
| Version: | 6.8 |
| Component: | comment.module |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | postponed (maintainer needs more info) |
Jump to:
Description
After upgrade to 6.x.1.x-dev after update to D6 i get Internal Server Error when trying to post/edit comment.

#1
Can you look in your apache and/or php error logs and see what messages it shows?
#2
How do I do that?
#3
If 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.
#4
Sorry, no access to the logs
#5
Then 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.
#6
My ISP told me that the error showed:
#7
Well, 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.
#8
1.:
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.
#9
Which 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.
#10
how do i find the version number?
#11
Ask your host. Or go to http://example.com/admin/reports/status/php
#12
5.2.3-1ubuntu6.4
#13
I 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.
#14
Automatically closed -- issue fixed for two weeks with no activity.
#15
Sorry, not fixed, I didnt get any response on my last comment, and I tried with the latest version, still same error.
#16
Ok. 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.
#17
#18
Uninstalled the module completely, that fixed it, but kind of anoying to have to remove all the information.
#19
Without 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...
#20
I've got the same problem when replying the comment, but I'm not using comment_notify module;/
#21
@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.
#22
It easy to say, but it happen on production environment, where I can't debug it.
#23
@kenorb - greggles asked you to open a NEW bug in the core queue, not reopen/reassign this bug.
#24
But I think it can be the same issue, so for what for? To duplicate the problem?