Skip to content

v8.13.4

Choose a tag to compare

@ccmrik ccmrik released this 01 Oct 04:26
· 16 commits to main since this release
9277f6e

The v8 line. This is a large step up from v7.44.1 — the plugin has been rebuilt rather than patched.

Highlights since v7.44.1

Administrator only. The gate used to be the manage_options capability, which sounds like "is an administrator" and is not — shop manager roles, client roles from membership plugins and page builders' "site manager" roles are routinely given it. Given this plugin rewrites wp-config.php and .htaccess and can permanently delete rows, that was the wrong thing to trust. Multisite super admins still pass, because they often hold no role on a given subsite.

Anyone non-administrator who uses CCM Tools today will lose access on update.

Every admin page rebuilt on one component set, with a dark theme, a floating save bar, and run panels that show work happening instead of rendering progress into a box further down the page. Both themes meet WCAG AA and nothing overflows on a phone.

Site Health replaced the old AI page. Twelve checks across caching, front end, database and platform, each linking straight to the control that changes it. Google PageSpeed is one input among them rather than the whole page, and it reports only — it never applies changes.

Premium and the AI optimiser are gone. Everything formerly behind the paywall, including the Redis and Cloudflare features, is now standard.

Fixes that mattered

  • A Redis password containing a dollar sign followed by a digit could write a broken wp-config.php, taking the front end and wp-admin down together.
  • Two output filters could blank the page for every visitor on a large page — invisibly, because they are skipped for administrators.
  • The .htaccess page could pre-tick "Block REST API" off the back of directives another plugin had written, and one click then broke the block editor and most front-end AJAX.
  • "Delete trashed posts" was graded Safe and ticked by default while orphaning attachments, revisions and WooCommerce order tables. It now goes through the proper API, batched.
  • The updater installed packages it could not verify. It now refuses them at the boundary.
  • The transient count on the Database page always read zero, because the query it ran was rejected by the database.

Housekeeping

Around 226 KB and 5,100 lines of internal commentary removed from the shipped files, along with 259 CSS declarations a later rule had already overridden — about 14% off the installed size, with no functional change.

Installing

ccm-tools.zip is the package. It unpacks to a ccm-tools/ folder.