Skip to main content

Rentiva 6.1.5 — The database cleanup no longer deletes what is not its own

· 4 min read
MaxHandMade
MaxHandMade
Maintainer

If you run MHM Currency Switcher next to Rentiva, one click in Rentiva's database cleanup could wipe your products' fixed prices. 6.1.5 closes that, makes the cleanup refuse to delete anything it could not back up first, and fixes a Bookings filter that never finished loading. It is published on WordPress.org, so WordPress offers it to you as an ordinary update — nothing to re-save afterwards.

The cleanup only removes what belongs to Rentiva​

Under MHM Rentiva > Settings > Database Cleanup, the invalid-meta cleanup treated every data key starting with _mhm as Rentiva's own. MHM Currency Switcher's keys start the same way, so the cleanup removed each product's fixed prices and, on stores whose orders are stored as posts, the currency, exchange rate and base currency recorded on each order.

Keys under _mhmcs_ — Currency Switcher's — are now left alone. A key that only resembles the prefix is still cleaned.

No backup, no deletion​

Three cleanups copy what they are about to remove into a backup table first: invalid meta, orphaned meta and old logs. None of them ever checked that the copy had actually been made. If the backup table could not be created, or could not be filled, the rows were deleted anyway — and the result screen still named a backup that did not hold them.

Each of the three now deletes nothing unless both steps of its backup succeeded. It tells you why it stopped, and removes a backup table it created but could not fill. The old-log cleanup decides table by table, so the other tables are still cleaned.

Two smaller faults in the same place are gone too: two cleanups started in the same second no longer share a backup table, and a long custom table prefix no longer breaks the backup table's name. A cancelled cleanup shows its own reason instead of "[object Object]".

The Database Cleanup page in these docs now describes the tools with the labels you see on screen, including where the invalid-meta cleanup lives.

The Pending filter opens again​

On the Bookings list, clicking the Pending chip could leave the page loading forever. The filter was built as a database query that grew with every detail stored on a booking; on a test site with real booking data the database was still working on it after 77 seconds. Every status chip now finds its bookings in one step, using the same rule the number on the chip uses — so the list and the number still agree. Filtering by licence plate now narrows a chip's list instead of replacing it. This had been there since 6.1.0.

Smaller things you will notice in the admin​

  • Notices stay put. A notice such as the licence warning used to slide in under the page title a moment after most admin screens appeared, pushing the page down. It is now in place when the screen first shows. On Settings > Notification Templates it no longer appears twice, and on Settings it no longer turns into a pop-up that disappears after four seconds.
  • The menu sits directly above WooCommerce, instead of below WooCommerce's Products, Payments and Analytics menus, so Rentiva's long list of screens stays in view. It is still below WordPress's own Posts, Media, Pages and Comments.
  • Vehicle Settings > Display & Preview shows your first vehicle that has a featured image — its photo, name and daily price — instead of a grey placeholder and a sample car.

Also in this release​

The search filter's "No vehicles found" message is now escaped on its AJAX path too, the vehicle edit screen no longer raises a PHP warning when the vehicle-details setting is empty, and unused e-mail screen JavaScript that called four admin actions that do not exist was removed.

Where to get it. 6.1.5 is on WordPress.org and on GitHub as v6.1.5; both carry the same files. WordPress.org holds new versions for a few hours before sites are offered the update. Using Rentiva Pro? Pro 6.2.0 requires this version — update Rentiva first. The full changelog in both languages ships with the plugin.