Ok, I made those changes to the file, I’ll keep an eye on the table to see if it keeps growing up, right now it’s 228.273 rows and 56.3 MB size.
I’ll let you now if it get fixed.
In the meantime, thanks for your time!!
Hi again,
right now (3 days later) the table has 606.046 rows and 148.5 MB it seems pretty big, right?
I’m not sure what size should be.
What do you think?
Plugin Author
Steve
(@steveatty)
Something is not clearing it down.
We need to know what the error codes are… that will tell us what is creating them and what isn’t clearing them down. You’ll need to look at the table directly to do that
Sorry for the delay, I’ve been pretty busy these days.
I’ve just exported the first 1000 rows of the table to a csv file, so you can take a look: http://sdrv.ms/14CJgl7
Let me know if I have to do something else.
Plugin Author
Steve
(@steveatty)
They’re all -3 errors which should be deleted by that extra line we put in the code which should remove ALL -3 posts that are more than 3 comment cycles old.
Is that a log file that you just grabbed?
Can you manually try running (assuming that wp_wordbooker_errorlogs is the right table name)
SELECT count(*) FROM wp_wordbooker_errorlogs WHERE timestamp < 1371292683 and blog_id =1 and post_id=-3
I’ve checked the code and its working fine here.
The file I linked is a csv export from the table wp_wordbooker_errorlogs.
How should I run that command? Should I have to create a php file with that code between php tags and run it from the root of my website or from any other folder inside it?
Here you can see my wordbooker_comments.php file edited as you suggested. I think it’s ok. http://sdrv.ms/17bYIbA
Plugin Author
Steve
(@steveatty)
I’ve got a recoded version in test at the moment. If that works I’ll zip up just the wordbooker_comments.php file for you.
You’d need to run that query from something like phpMyAdmin
As a SQL query? Sorry I’m not used to work with databases.
I ran that code as a SQL query and I got this:
count(*)
0
Plugin Author
Steve
(@steveatty)
Ok, just uploaded it to our website.
Let’s see how it works. I’ll keep an eye on the database and let you know.
I just had a look at my Error Log table and its petty large again also. I ran the SQL query and got the same result as taniko1.
I also updated my files to the version in the zip file above and I had a look at my error logs table but it has increased in size. I have uploaded a CSV of the table here. https://dl.dropboxusercontent.com/u/68217166/wp_wordbooker_errorlogs.csv
Plugin Author
Steve
(@steveatty)
The new version’s code will run the next time comment handling runs – watching it here with comment handling set at 10 minutes its always keeping the previous 3 runs in the diagnostic logs on the Wordbooker Admin page.
I think it’s now working for me, we’ve just published a post, so maybe you need to publish something to start the cleaning function.
My table now has only 1537 rows, it’s still 148.8 MB but 129 MB are trash to be cleaned with the next database optimization, so I’d say it works for me now.
I’ll update you in a few days, till then, thank you very much, Steve.
Plugin Author
Steve
(@steveatty)
Will – what is your comment handling window set to – Wordbooker is handling 140 blog posts in each comment cycle. 99.9% of those have probably vanished off the walls in Facebook
Plugin Author
Steve
(@steveatty)
It deletes comment processing log rows that are older than 3 times the comment polling period and it does that at the start of each comment run. So if you have it set to 12 hours then it will keep the previous 3 runs + the current run.
