Plugin Author
Steve
(@steveatty)
You can either truncate it using a db management tool or you can delete it from the wordbooker options screen (there is a button to delete the diagnostic logs) – but that second method might not work if its that big. It should auto trim when you visit the admin page but either that’s not working or you’ve not been visiting the admin page.
Hi
I tried clicking the ‘Clear Diagnostic Data’ button and there are no logs appearing on the Wordbooker Admin page. I do visit the Wordbooker admin page very regularly so its not that either. 🙁
I just went into PHP My Admin and ran the command DELETE FROM wp_wordbooker_errorlogs;
It seemed to do the trick.
Plugin Author
Steve
(@steveatty)
It still seems odd that its not clearing things down as you’d expect. Are there multiple users on your blog and which version of Wordbooker are you using?
Hi!
I have the same problem, I’m using the lastest version of wordbooker plugin. I need to keep cleaning the diagnostic data every few days as it get increasing really fast, 200-300 MB a week or so.
I use to visit my wordpress admin page everyday.
Any way to fix this?
Thanks!
Plugin Author
Steve
(@steveatty)
What is it filling up with? The cron job that refreshes the cache should clear old entries down.
It get cleaned just whe I click the button in wordbooker admin page “Clear diagnostic messages”.Or if I clear the table manually in phpmyadmin.
I don’t know what’s filling the table, diagnostics messages, I guess, mostly comment handling information.
FYI, from the last manual cleaning just a few hours ago the table has 11382 lines.
Thanks for your quick answer.
Plugin Author
Steve
(@steveatty)
Is this a multi-site install? What polling interval are you using?
No multi-site, comment handling every 30 minutes.
Plugin Author
Steve
(@steveatty)
OK – how comfortable do you feel about editing code?
in wordbooker_cron.php (in the wordbooker/includes directory)
Find
$result = $wpdb->query('DELETE FROM '.WORDBOOKER_ERRORLOGS.' WHERE timestamp < '.$trimtime.' and blog_id ='.$blog_id.' and post_id=-2');
and add after it:
$result = $wpdb->query('DELETE FROM '.WORDBOOKER_ERRORLOGS.' WHERE timestamp < '.$trimtime.' and blog_id ='.$blog_id.' and post_id=-3');
In my file it’s a bit different, like this:
$result = $wpdb->query(' DELETE FROM ' . WORDBOOKER_ERRORLOGS . ' WHERE blog_id ='.$blog_id.' and (user_ID='.$user_id.' or user_ID=0 ) and post_id<=1');
Should I have to add your line anyway?
Plugin Author
Steve
(@steveatty)
Braincramp on my part I meant wordbooker_comments.php … not wordbooker_cron.php
These are the first lines of support info from the plugin admin page:
Wordbooker: 2.1.32
Wordbooker Code Base: 2.1.32 R00 – When a Warm Wind Blows Through the Grass
Wordbooker ID: 254577506873
Wordbooker Schema: 5.6
WordPress: 3.5.1
Table prefix: wp_
PHP: 5.4.16
Plugin Author
Steve
(@steveatty)
OK so make the change to wordbooker_comments and not wordbooker_cron.
Its been a long week at work.
Hi, Sorry I didnt get notified of your reply till today.
My site isn’t a multi user site, just me. I have made those changes also as you recommended above.
