Optimizing Database Tables is shown empty

Hi @lsbk,

Sorry to hear you’re having trouble with this. Several of us on our team have been testing the plugin today at the latest version (on PHP 8.0 and 8.2 and Core 6.4.3) and haven’t seen this issue.

In 5.2 we did a lot to tighten up security — do you have any custom user permissions set on your user, by any chance? I’m wondering if maybe something is conflicting there.

Could you please try creating a new Administrator account, logging in with that, and seeing if you encounter the same problem?

Appreciate any other info you might be able to provide, and we’ll continue to dig into this!

Thanks,

Andrew

Hi

I did it with another, new created Admin, no other result.
It seems, that deletions have been made, but the tables were not reorganized.

Hi @lsbk,

Thanks for following up, and for trying the new Admin account. We are now thinking the issue may be related to the one-click optimization button (in the menus).

If you go to Tools > Optimize Database, and then click the “Optimize (detail)” button, does that work as expected?

Thanks again,

Andrew

I always use this option.

My tables are not shown on the settings page nor in the optimization result.
Deletions are shown in the log, but nothing about tables and savings.

How to send you the screenshots?

Hi @lsbk,

Thanks for your patience. We just released 5.2.1 which fixes the one-click link in the admin bar — though it sounds like there’s more going on here than that.

You can use an image hosting service like https://postimages.org/ to upload your images, and then link them here via URL. Alternatively, if you’d like to email us directly, please send them to [email protected] (Add a note asking to send it to Andrew).

If you can include a screenshot of all your settings, and anything else that’s not working as expected, that would be super-helpful.

Thanks!

Hi @lsbk,

Thanks for sending those screenshots via email; it was very helpful!

We’ve released version 5.2.2 which should fully resolve the issues you were seeing. (For the record: It was due to a capital letter in the database name. 5.2.2 fixes the sanitization to accommodate for that scenario.)

I appreciate your patience as we figured that out!

Thanks again,

Andrew