Harvify Database Cleaner

1.0.26

• Readme: step-by-step setup and usage instructions, a frequently asked questions
  section, and a plainer description of what the free and Pro tiers include.

1.0.24

• Fixed: the “Keep last N revisions per post” control now appears on the
  Cleanup screen in the free tier. 1.0.23 made the setting free and the cleaner
  honoured it without a licence, but the box to change it was still drawn only for
  licensed sites, so a free user had no way to set it. It now shows after a scan in
  every licence state.
• Changed: the External services section now describes the Freemius opt-in screen
  shown on activation. Until you answer it a fresh install makes no outbound
  request, and choosing Skip keeps the free tier fully usable and sends nothing.

1.0.23

• “Keep last N revisions per post” is now free. The setting existed and the
  cleaner that honours it shipped in every download; only a licence check stopped
  it working, so a free user could not keep a single revision. Set it to 0 to
  delete them all, as before.
• Changed: the twelve Pro cleaner categories — orphaned and duplicate metadata,
  orphaned term relationships, oEmbed caches, pending comments, the WooCommerce
  categories and Action Scheduler cleanup — are supplied by the separately
  distributed Pro plugin rather than being present-but-inactive in this download.
  This download scans and cleans the eight categories it owns.
• Changed: daily scheduling is likewise supplied by the Pro plugin. Weekly and
  monthly scheduling are unchanged and remain free.
• Changed: every identifier this plugin owns has been renamed off its old
  three-character hdc_ prefix, which is shorter than WordPress.org accepts.
  Functions, options and the plugin’s own actions and filters are now
  harvify_dbclean_*; global constants are HARVIFY_DBCLEAN_*; classes are
  Harvify_DBClean_*.
• Developers: the REST namespace is now harvify-dbclean/v1. The old hdc/v1
  namespace is GONE and there is no compatibility alias — any code calling it
  will 404 until updated. The admin script and style handle hdc-admin is now
  harvify-dbclean-admin, and the localized JavaScript object hdcSettings is
  now harvifyDbcleanSettings.
• Fixed (Pro): “Duplicate post meta” and “Duplicate user meta” no longer delete
  legitimate values. A duplicate now means the same key AND the same value. The
  cleaner previously removed every additional value stored under one key — for
  example all but one of the previous-slug records WordPress keeps so old links
  still redirect.
• Fixed (Pro): “WooCommerce orphaned order items” no longer matches real
  orders. On stores using WooCommerce’s high-performance order storage it
  counted — and would have deleted — the line items of every order, and on older
  storage it also matched refund and subscription line items. An item is now only
  treated as orphaned when its order no longer exists anywhere.
• Fixed: asking for a cleanup frequency this installation cannot run is now
  refused with a clear message naming the frequencies that are available. It
  used to answer “saved” and quietly store weekly instead.
• Fixed: the Schedule screen now shows your saved schedule on every site.
  Weekly and monthly scheduling are free, but the screen only read the saved
  schedule when Pro was active, so a free site always showed it as unset.
• Fixed: when the server refuses a request, the screen now shows the reason.
  Every refusal used to be treated as a success, so a refused save said
  “Schedule saved.” and a refused cleanup reported “Cleaned undefined rows”.
• Fixed: when the frequencies a site can run change, the scheduled cleanup is
  rescheduled to match on the next admin visit or cron run. Your saved
  frequency is not changed.
• Fixed (Pro): when the Pro licence is not active, the Pro plugin stops
  running Pro features — its twelve cleaner categories, daily scheduling,
  pre-cleanup snapshots, cleanup history and email reports. Nothing you saved
  is removed: the twelve categories stay listed and are still counted by a
  scan, a daily schedule keeps running weekly, and re-activating the licence
  restores everything. Asking to clean one of those categories now says why it
  cannot run instead of reporting zero rows.
• Fixed (Pro): a scheduled cleanup is recorded once in the cleanup history. It
  used to appear twice, once labelled as a manual cleanup.
• Fixed: Table Optimization reads the free space of the table it names. A
  table name was matched as a pattern, so a table with nothing to reclaim could
  be offered because a similarly named table had free space. The size shown for
  a leftover table uses the same exact match.
• Changed: the plugin’s loader no longer creates an unprefixed global variable.
• Fixed: the Schedule screen lists frequencies in order: Daily, Weekly, Monthly.
• Fixed: the upgrade card no longer lists “keep last N revisions” as a Pro
  feature, and the Plan screen lists it under the free tier, where it is.
• Fixed: the Action Scheduler cleanup (Pro) is described accurately. It removes
  completed, failed and cancelled actions older than 30 days, with their log
  rows; it never empties the tables.
• Your settings, your schedule and your scheduled cleanup are migrated onto the
  new names on the first page load after updating. Your cleanup history and
  snapshot tables are untouched — those names never changed.

1.0.17

• Added: a single Support entry in the Harvify menu, so you can reach us from
  inside WordPress. Until now no plugin offered a contact route at all. One entry for
  the whole suite rather than one per plugin.
• No behaviour changes.

1.0.16

• Added: an External services section to this readme, naming every third-party
  service the plugin can contact, exactly what is sent, when, and each provider’s terms
  and privacy policy. Required for WordPress.org submission.
• Changed: the Contributors field now names the correct WordPress.org account.
• No behaviour changes.

1.0.15

• Fixed: deactivating or deleting the plugin now cancels the scheduled cleanup.
  The cleanup is queued through Action Scheduler, but the cancellation used the
  WordPress cron function, which reads an entirely different store — so it
  reported success and removed nothing.