Skip to main content

Rentiva v5.1.1 / Pro v5.1.1 — Compliance hygiene, no behaviour change

· 2 min read
MaxHandMade
MaxHandMade
Maintainer

A small follow-up to v5.1.0, continuing the pass ahead of the WordPress.org listing. Nothing about how the plugin behaves changes here — this is the kind of release that is worth publishing precisely because it is uneventful.

Written before 6.0.0

This post is the record of a release that shipped before 6.0.0, which renamed the plugin's post types, taxonomies, options, meta keys and hooks. The identifiers below are the names those versions actually used, and they are kept that way on purpose. For the current names — and a conversion table — see the 6.0.7 release post.

What changed​

  • Action names carry the full prefix. The REST API-key and deposit-management AJAX actions now use the complete mhm_rentiva_ prefix. A duplicate registration of the API-key handlers was also removed, so each action is handled exactly once instead of twice.
  • Dead references removed. A leftover reference to a settings class that is not part of the free plugin, an unreachable deposit-calculation path, and developer debug logging left behind in the block-editor and search scripts.
  • No non-functional buttons. The customer privacy controls render only when their handlers are actually available — those ship with the paid add-on — so the free plugin no longer shows controls that cannot do anything. Add-on-only scripts were removed from the free plugin at the same time.
  • Docs: the readme describes the bundled shared UI library in neutral wording.

Pro v5.1.1​

The add-on now bundles the frontend scripts it owns, rather than expecting the free plugin to ship them on its behalf. This is the other half of the neutral-hooks separation that landed in v5.1.0.

Upgrading​

No action required; your settings and data are unaffected.