Title: Cannot edit comments, internal server error 500
Last modified: August 19, 2016

---

# Cannot edit comments, internal server error 500

 *  [stopkatie](https://wordpress.org/support/users/stopkatie/)
 * (@stopkatie)
 * [16 years, 11 months ago](https://wordpress.org/support/topic/cannot-edit-comments-internal-server-error-500/)
 * Hi All,
    I just upgraded to WordPress 2.8 with hopes I could mass edit the 410,000
   + unapproved spam comments on my website (yes, I know). I went to edit the comments
   and everything was going fine. Then I saw I could have it show up to 999 comments
   at a time so I entered 999 and save and then the internal server error 500 showed
   up. Now every time I go to the comments page I have this problem.
 * So two questions:
    -How do I fix this?
 * -Is there a plugin out there that will allow me to delete hundreds of unapproved
   spam comments at a time??

Viewing 3 replies - 1 through 3 (of 3 total)

 *  Thread Starter [stopkatie](https://wordpress.org/support/users/stopkatie/)
 * (@stopkatie)
 * [16 years, 11 months ago](https://wordpress.org/support/topic/cannot-edit-comments-internal-server-error-500/#post-1127751)
 * Any help anyone? Even pointing me to a topic with a resolution to the same problem
   will help. Thanks.
 *  Thread Starter [stopkatie](https://wordpress.org/support/users/stopkatie/)
 * (@stopkatie)
 * [16 years, 9 months ago](https://wordpress.org/support/topic/cannot-edit-comments-internal-server-error-500/#post-1127955)
 * Hello, I’m still having this problem. I cannot access my comments and I can’t
   find any info relating to it. ANY HELP PLEASE?
 *  [jon](https://wordpress.org/support/users/adiant/)
 * (@adiant)
 * [16 years, 9 months ago](https://wordpress.org/support/topic/cannot-edit-comments-internal-server-error-500/#post-1127956)
 * This is very likely a problem with your web host. My former host runs a Resource
   Manager that gets “very aggressive” whenever the workload on the server (i.e.–
   other customers using the same physical computer as a web server that you are)
   gets heavy. It would then start canceling any process that used even a moderate
   amount of processor time. Like your 999 comments to be displayed.
 * Admittedly, my problems were with phpBB Version 2, but the same would hold true
   for WordPress as my issue was processor-intensive MySQL queries that caused me
   to have hundreds of 500 errors (to myself and hundreds of site visitors).
 * Best way to figure it out is to file a Trouble Ticket with your web host giving
   exact date and time (tell them what time zone you are in, so they can translate)
   of a 500 error you are getting for this 999 comments thing, and ask them for 
   all log information they can find.
 * And don’t delay. Finding log info after 24 hours can be a lot tougher for some
   web hosts than incidents that occurred the same day.
 * In my case, the results were quite telling, as I tracked it down to a very complex
   MySQL query to build the information for a feature that almost no one used!
 * Good luck with it!
 * 500 errors can be very frustrating because they can be either WordPress configuration
   or other problems. Or they can be caused by a web host that goes around automatically
   cancelling legitimate Processes that you are running.

Viewing 3 replies - 1 through 3 (of 3 total)

The topic ‘Cannot edit comments, internal server error 500’ is closed to new replies.

## Tags

 * [Comments](https://wordpress.org/support/topic-tag/comments/)
 * [internal](https://wordpress.org/support/topic-tag/internal/)
 * [server](https://wordpress.org/support/topic-tag/server/)

 * In: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/)
 * 3 replies
 * 2 participants
 * Last reply from: [jon](https://wordpress.org/support/users/adiant/)
 * Last activity: [16 years, 9 months ago](https://wordpress.org/support/topic/cannot-edit-comments-internal-server-error-500/#post-1127956)
 * Status: not resolved

## Topics

### Topics with no replies

### Non-support topics

### Resolved topics

### Unresolved topics

### All topics
