Same thing. Hope this is not a up sell move after offering everyone this tool free.
@kronos1705: In the default situation, a MySQL OPTIMIZE command on an InnoDB table is detrimental. The latest release reflects this fact, and so won’t let you do this if all your tables are InnoDB: http://code.openark.org/blog/mysql/how-often-should-you-use-optimize-table-followup
For future releases we have been working on the research and code to make sure that the option is available in the situations in which it is advantageous, and not on others.
@voicetoons: Sigh.
Thank you, however it only stopped working overnight after updating yesterday and we have used it for months. Our tables dB has not changed. Explain please? :–)
Indeed, I enjoyed throughout the year – no problem was found, but – developers know better. Pritenzy can not be. Can I somehow revert to the previous version of the plug-in? To use the old functionality or you’ll soon all will test and return the option?
What’s interesting, is if you look on the Settings tab, you can choose to optimize database tables there.
