Skip to main content

Rentiva v5.2.4 — The menu moves down, and every link out of your site is now written down

· 3 min read
MaxHandMade
MaxHandMade
Maintainer

A small release with a simple theme: fitting into WordPress rather than competing with it.

The menu is lower now​

MHM Rentiva registered its top-level admin menu at position 58, which put it directly above Appearance — ahead of most of WordPress's own items. That is a prominent spot, and on a site running several plugins it is exactly how the admin sidebar turns into a scramble.

It now sits at 76: still top-level, but below Appearance, Plugins, Users and Tools, immediately above Settings. Nothing else changed — the same screens are underneath it in the same order.

If you navigate by muscle memory, this is the one thing you will notice.

The readme said the plugin uses no external services. That is true in the sense that matters — it makes no HTTP request to anyone, sends nothing about your site or your customers anywhere, and loads every asset including its webfont from your own server.

But the admin screens do contain ordinary hyperlinks, and a reader checking the claim would find them and reasonably wonder. So the "External services" section now lists them: the documentation site, the issue tracker, wpalemi.com with its terms and privacy pages, this plugin's WordPress.org support forum, the two SMTP plugin pages the setup wizard suggests, and a YouTube channel. They open only if you click them, and they send nothing when you do.

A sentence we had to take back​

The same section previously said that a check in our build "fails if a request to any third-party host is introduced."

That was not true, and the file it referred to says so itself, in a comment we wrote: "this gate cannot catch a NEW third-party host nobody has thought of. It is a regression fence, not a discovery tool." It is a list of sixteen specific hosts — the geolocation, CDN, analytics and Gravatar services earlier versions used — and it scans PHP only. We confirmed the gap by testing it: a request to one of those sixteen fails the build, a request to a host nobody listed passes.

So the readme now describes the check as what it is. The underlying claim — that the plugin makes no third-party request — still holds and was verified by sweeping the shipped code, not by trusting the gate.

We are writing this down publicly because it is the third time in two releases that a sentence of ours turned out to be an assumption rather than a measurement, and the pattern was identical each time: reading a thing's name instead of reading what it does.

Upgrading​

Nothing to do.