Plugin Contributor
cageehv
(@cageehv)
ok, checked: I don’t touch the wp-terms table… and also not wp_term_taxonomy…
Plugin Contributor
cageehv
(@cageehv)
(only in the OPTIMIZE TABLE statements, not for deleting records)
Plugin Contributor
cageehv
(@cageehv)
what happens when you select all tables and run an ‘optimize table’ statement in PHPMyAdmin? will that fuck it up too? (because that is basically what I’m doing…)
Rolf, none of these check boxes are ticked. I don’t run the scheduler either. I delete all revisions, so that option is set to ‘0’.
Plugin Contributor
cageehv
(@cageehv)
reading all of this, to me it sounds like you have a corrupted database problem… my plugin is just indicating that… (not sure, of course ;-))
Plugin Contributor
cageehv
(@cageehv)
next question: did you try to disable all plugins for a second and run it?
Yes, you are correct. PHPMyAdmin produces the same error for the table when “Optimize table” is selected.
Many thanks. The question is, why is that triggered by optimization? There are no errors logged otherwise.
Plugin Contributor
cageehv
(@cageehv)
(I mean, only my plugin activated, the rest deactivated and then running it)
Plugin Contributor
cageehv
(@cageehv)
I repeat: sounds like you have a problem with your database…
Plugin Contributor
cageehv
(@cageehv)
my plugin touches all the tables (for optimizing them) so then the problem shows up…
Alright, I will give it some more thorough testing and will update. Thanks for your suggestions.
Plugin Contributor
cageehv
(@cageehv)
bedtime here, so tomorrow evening I’ll be available again for thinking with you and solving this problem 🙂 ciao!
Plugin Contributor
cageehv
(@cageehv)
In the mean time, I’m sure my plugin is not ‘causing’ the problem but just signalling it…
Plugin Contributor
cageehv
(@cageehv)
tables are already corrupted (by another plugin?) and my plugin says: “Hey, that table has a problem!” (in the log file)
Yes, I can see that after I manually optimized via phpMyAdmin. Thanks!
