TOPIC: 500 Internal Server Error after deleting comments

Please try to disable the captcha system and post the long comment again. If you get the problem again - then please contact the server support.
If you don't get this error I will need super admin account to test it and then at the end we will perhaps also end with contacting the server support.

has this problem ever been solved? I have a similar one. I just tried to post a reply to a comment. I sent the comment and everything seemed to be fine. But now I cannot go to 'manage comments', I just get the 'internal server error.'

It seems that my comment was longer than the allowed limit. But I got no warning message that it was too long. Now Joomlacomments is unusable at this point.

What to do to fix this?
thanks,
Andre

Well, I can not remember if I got feedback from the user. It doesn't matter for joomlacomment how long the post is. The whole comment will be stored in the database, but only the limited one will be shown.
Do you have any error messages in the error log?

yes, tons, but I don't know what it all means. Could you possibly have a look? I'll attach it.
Thanks very much.

Can you write a letter to your support and ask them about this error message:

[Sat Apr 11 13:54:47 2009] [error] [client 93.41.189.77] Premature end of script headers: php5.cgi, referer: www.israelcatholic.com/administrator/ind...&task=settingssimple

I'm not running php5 in cgi mode, so I would like to know the answer of the support. It could point me in the right direction. Thank you!

thanks Daniel, I have sent an email to the server support and will let you know as soon as I get an answer.
Andre

The answer I got from support was the following:

Basically the 500 error is a HTTP server (Web
server) error message that is sent to the browser when the server cannot continue to execute the code in a script. It can occur for a variety of reasons, including a bug in the code, an undefined variable or lack of permission to a certain resource. Lack of permission to a certain resource can mean that you are going over shared memory limits but I checked this earlier and doesn't seem to be the case.

Please let me know any ideas you may have Daniel. Joomlacomment remains in the same situation - impossible to reaccess 'manage comments'.

That was absolutely not a helpful response

However I have one idea. Please chmod all the files and folders in administrator/components/com_comment to 777 and check if it is working. (if it works, then start to reduce the permissions to see when it brakes down)

Please, can you also look in your error log for a file missing or something like that?

In my error log I had a message sayin that fiel could not be found.

[Thu Jan 22 16:49:22 2009] [error] [client 127.0.0.1] File does not exist: D:/xampp/htdocs/liberator/administrator/components/com_comment/joscomment, referer: http://localhost/liberator/administrator/index.php?option=com_comment&task=settingsedit

Because xdebug is not working on my vista machine, I installed windowsXP in virtual machine, apache server, mysql and netbeans. Took around 1h to setup.
Then I started with debugging. After 1h I found where the error message was coming from. The configuration in backend was creating the config object and there we had a parameter for live site that was pointing to the administrator directory, instead to frontend.
We were using JURI::base() instead of JURI::root() .

Please go to components/com_comment/joscomment/utils.php
at line 150 in the boardInitialization function findand change it to
I don't know if this is going to solve your 500 error message, but if you make this, then this means that no error messages are generated in backend. (no bug in the code anymore )
Please make the change and tell me if it help you.

thanks for all your efforts to try to solve this Daniel, I really appreciate it.

I looked into /components/com_comment/joscomment/utils.php and could not find any line with the code you mentioned.

By the way, I am running Joomla 1.0.15 in case that makes a difference.

Regarding your previous message, what is chmod and how do I do this? Please forgive my ignorance, i am not a pro at this and usually need to have things spelled out. However I will work with you as much as I can in order to find the trouble. In the meantime joomla comment is unfortunately still not usable.

Andre

Hm. No this code I'm reffering to is only in joomlacomment alpha3.
We or better to say I am not supporting joomla 1.0 anymore. Are you able to upgrade to joomla 1.5? I know this is difficult, but joomla 1.5 is the future. You will not be able to update to 1.6 from 1.0 and also joomla 1.0 is not anymore supported or am I wrong?
about chmod here en.wikipedia.org/wiki/Chmod . You can also use filezilla to change file permissions. Right click on the file you want to change and permissions. There you set the permissions you want.

oh, that's bad news. Yes I know about Joomla 1.5 but I expect some kind of worst case scenario if I try to migrate, and that it will give me a month of nightmares. I tried uninstalling and reinstalling the joomlacomment component but the problem is still there - no way to manage comments. I'm puzzled though, shouldn't joomlacomment 3.26 work with Joomla 1.0? Is my only other alternative to uninstall Joomlacomment and look for some other comment extension?

If you look in our faq section all of the videos are made with joomla 1.0. Joomlacomment 3.26 works on joomla1.0, but the problems you have are configuration specific.

There is another user that reported problems in cgi mode with joomla comment compojoom.com/forum.html?func=view&catid=8&id=3695&limit=10 . And I will try to find out the problem, because he uses joomla1.5

I don't like to say it, but I don't have the possibility to work on both joomla installations. First because joomla1.0 is past and second, because I don't know the framework and third, because I will have even less time for myself.

Another alternative is to forget about the backend and edit the comments directly in the database through phpmyadmin for example.

Please understand that I want to help you, but this is connected with too much work and it is not something that will help the other users, because all future versions will work only with joomla1.5 .

Thank you for not giving up on compojoom!

yeah I understand that you don't want to spend time on a Joomla 1.0 problem, though it's kind of frustrating to see that it worked at first and then just stopped working, without me doing anything special.

In case you have some flash of genius as to what my problem might be, this is my configuration below. Otherwise I'm not crazy about dealing with the database directly... unfortunately it looks like I'll have to find another comment component. If you would like to have a quick look anyway I could PM you access to my site.

PHP built On: Linux hillhurst 2.4.32-grsec-opteron-peon-1.1.1 #1 SMP Fri Dec 21 15:45:17 PST 2007 i686
Database Version: 5.0.67-log
PHP Version: 5.2.6
Web Server: Apache/2.0.63 (Unix) PHP/4.4.7 mod_ssl/2.0.63 OpenSSL/0.9.7e mod_fastcgi/2.4.2 DAV/2 SVN/1.4.2
WebServer to PHP interface: cgi-fcgi
Joomla! Version: Joomla! 1.0.15 Stable [ Daytime ] 22 February 2008 23:00 UTC
User Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0. Gecko/2009032609 Firefox/3.0.8
Relevant PHP Settings:
Joomla! Register Globals Emulation: ON

I will try to help the user with 1.5 - he also uses cgi. If I find it for him, perhaps it will be the same for you. Right now 4.0 and 3.26 are not so much different.

Wait till the end of the week and let me see if I can fix this.

anything new Daniel? I am getting some new comments posted that I can't manage. I will have to change comment system if there is no solution to this. Or would you like to have a quick look into my backend?

Hey there andre!

For the other users it was all database problems. One of them had MySQL 4.1 - you need 5.0 (that is not the case for you).

For the other one it was corrupted table.

Can you make the following test.

Use phpmyadmin and go to your site database.
First make a backup of the jos_comment table. (this is the most important step here!!!!)

After that open the table and delete all comments in it. Check to see if the backend is working. If yes - then the database is corrupted.

I will need you backup then to check what exactly is wrong there.

P.S. I really suppose it is the database, because you got this problem after deleting a comment.

ok, I exported the table and here it is. Didn't delete anything yet, am a little nervous about that. jos_comment.txt

Daniel:

breakthrough!

I deleted a few comments, one by one, and the backend started working properly after I deleted comment id number 14 by user 'Ariel'. Iif you could tell me what the problem was, it may help avoid it in the future.

Thanks for the help! I'm glad we got this sorted out.

Hm, interesting!
I imported you dump and it is not creating any blank screen for me.

Would you import all the comments again and look if you get the same error again?