It is possible to exceed MySQL or PHP execution time limits and when you do you can get a similar result and don’t always get a notice or warning about it. I’d talk to my web host and try to get more details about exactly what is going on, and I’d think about paginating those comments.
Thread Starter
sdamy
(@sdamy)
I use the standard built in limit comment per page but the problem is the same…
Have you talked to your web host? I still think it sounds like a timeout issue.
Do you have the same problem if you set the comments per page limit to a very small value, like two or three?
Also, if this started with an upgrade, make very sure that all of your files actually got uploaded. FTP can hang and files end up missing or corrupt.
Thread Starter
sdamy
(@sdamy)
The blog work on dedicated server, this is the setting about time php:
max_execution_time: 330 (phpinfo)
With wordpress < 2.65 non problem.
Yes, I’ve the same problem if I set the comments two or three per page.
The data about the records are OK… I’ve done many test with sql statement on number of comments about a post, I’ve split the 117.00 comments in plus posts (es.UPDATE wp_4comments SET comment_post_ID=11517 WHERE comment_post_ID=11502 and comment_date > ‘2008-10-01’), there are the result:
– with 117.000 comments in a single post wordpress 2.84 crash
– with 49.027 comments in a single post wordpress 2.84 crash
– with 35.240 comments in a single post wordpress 2.84 run but it don’t numbering correctly the totale number of posts, it say “no responses to”
– with 9.721 comments in a single post wordpress 2.84 run and numbering correctly the comments
For me there are bug on wp 2.84
What can I do?