Rentiva v5.0.0 — First Public WordPress.org Release
· 2 min read
MHM Rentiva's first release on WordPress.org: the complete rental core with no artificial limits, no third-party requests, and full WordPress.org coding-standards compliance.
Every screen works exactly as before — this release changes how the plugin is packaged and loaded, not what it does.
What's in it
- First public release on WordPress.org. Fleet management, availability, bookings, customers, WooCommerce payments, email notifications and the customer account pages — with no vehicle, booking or listing caps, no feature timers and no locked screens.
- No third-party requests at all. The webfont is bundled and served from your own site; there are no geolocation, analytics or CDN calls.
- 16 shortcodes, 16 Gutenberg blocks and 17 Elementor widgets share a single renderer (Render Parity), so all three produce identical output. Ships with a full Turkish translation.
Under the hood
- Assets load through the WordPress asset system. Every admin and front-end script and style now goes through
wp_enqueue/wp_add_inline_*instead of inline<script>/<style>blocks — with no change to how any screen looks or behaves. Self-contained documents (email templates, the downloadable test report, the meta-keys reference) keep their inline styles by design, since an external stylesheet would not be available when those are opened on their own. - Licence gating hardened. Pro-only surfaces are now gated on a valid licence rather than only hidden, closing several paths where the separate paid add-on's features could run without one.
- WordPress 7.0 ready, including a contrast fix for dashicons inside primary buttons (WP 7.0 colours them with the admin theme colour, which made them invisible on a primary button's matching background).
Quality gates
| Gate | Result |
|---|---|
| PHPUnit | 868 tests / 2,823 assertions, 0 failures |
| WordPress Coding Standards | 0 errors |
| Plugin Check (distributed ZIP) | 0 errors |
| Independent audits | Two architecture/security reviews, plus browser verification across every affected admin and front-end screen |
Upgrading
First WordPress.org release — if you are upgrading from a pre-release build, no action is required.
Requirements: WordPress 6.7+, PHP 8.1+. WooCommerce is required for frontend booking payments.