Error Log Huge

I had it set to twice daily but I have it now disabled because not many people comment anyway.

Thanks for your help Steve!

Hi!

Just to let you know that it’s working perfectly now, the table has 33K rows and 9MB.

Thank you very much, Steve.

That’s still pretty big…. I wonder if you’ve got a lot of orphaned records in there.

Hi,

I missed your answer, how can I check that records?

It would really take some looking at the table and working out what sort of records are in there….

Here you have a full CSV export of that table:

https://www.dropbox.com/s/hfnje4d6gfoox53/wp_wordbooker_errorlogs.csv

It’s like 30K rows.

Thanks.

I’d look at how long you keep posts open for comments for because you’re processing 1280 posts for comments and that is a stupid amount of posts to be checking for comments – its taking 20 minutes to process them all and you’re checking every 30 minutes ..

So no orphaned rows – just a lot of diagnostic messages.

That’s the same thing as emptying the table from phpmyadmin? Sorry but I’m not used to work with databases.

Yes it is – but see my updated post… there are no orphaned rows, its because you are checking 1280 posts for comments every 30 minutes.

You really need to set WordPress to autoclose comments after a fixed number of days or tell Wordbooker to ignore posts over a certain age.

Oh!

Stupid me, I didn’t see that line in the wordbooker options panel, I’ve just changed it to 15 days.

Thank you very much again.

OK – so hopefully as the comment handling cycles and purges the old rows the total number should drop. If not let me know and I’ll investigate further.

You might want to consider setting the Comment Auto close on the main WordPress Settings–>Discussions tab

Hi, it’s now 700 KB, so I’d now say it’s fixed.

I’ll leave wordbooker comment management cut off at 15 days and close comments in wordpress for much older posts.

Thank you very much again, fantastic support.