Phil
(@probablynotphil)
The changelog is showing for me. However I think the confusion may be that it is in ascending order, rather than having the latest updates at the top of the list.
@olliejones, it might be worth changing that in the next update. So the newest update is listed at the top of the changelog. I notice someone recently asked about the “Do ANALYZE TABLE after each rekeying operation” entry from update 1.4.12, which suggests that person has probably perceived version 1.4.12 to be the latest update as it is at the top of the list.
Doh! (smacks forehead). @probablynotphil, you’re probably not wrong. I bet you get that a lot.
And thanks for the question, @swb1192. The changelog should say this. I’ll push a fixed readme.txt to the repo tomorrow with fresh eyes. I can do the readme.txt change without changing the current version and forcing everybody’s site to update.
Happy and prosperous 2024 to you.
= 1.4.15 =
(no changes to keys)
Add a Database Health section to the About tab showing some performance metrics.
Avoid doing EXPLAIN DESCRIBE when capturing monitors.
Clear the dashboard upgrade nag after doing wp index-mysql status.
Put backticks around table names in data definition language statements.
= 1.4.14 =
(no changes to keys)
Handle database version 55853 (no schema changes).
Deal with php 8.2 deprecations.
= 1.4.13 =
(no changes to keys)
Support MariaDB 11.x in version-detection code.
= 1.4.12 =
(no changes to keys)
Change max_statement_time session variable if necessary to avoid "Query execution was interrupted" errors.
Do ANALYZE TABLE after each rekeying operation.
Hello, it still appears in ascending order for me. Is anyone else experiencing this? Perhaps it can be resolved or included in the next update, as Ollie mentioned, to avoid mandatory updates solely for this change.
Thanks!
Reply edited because perhaps the changes haven’t been uploaded yet. Sorry!
Phil
(@probablynotphil)
Happy and prosperous 2024 to you.
Thanks Ollie, same to you! I am very grateful for the work you’re doing with this plugin.
I pushed a change to the readme.txt file to put the paragraphs of the change log in the correct order. I apologize for the error and the ensuing confusion.
Yep, top-down is the way to go, thanks for taking care 🔥
