70 posts tagged with "rentiva"

6.3.0 protects what vendors hand over: IBANs, identity documents and vehicle documents are encrypted and kept out of the media library. Messages are rebuilt as conversations, and Vendor Management gets a vendor detail page and one home for every vendor setting. Update MHM Rentiva (Lite) to 6.2.0 first, then Pro. Rentiva Pro 6.1.0 or older stops with an error on the vendor panel beside Rentiva 6.2.0, so do the two updates back to back.

6.2.0 gathers four weeks of work. Contact messages move to a screen of their own and their attachments to a private folder, the separate customer dashboard is retired in favour of My Account, and block and Elementor settings that were saved but never reached the page now take effect. It is published on WordPress.org, so WordPress offers it to you as an ordinary update. Using Rentiva Pro? Pro 6.1.0 or older stops with an error on the vendor panel beside this release — update Pro to 6.3.0 right after.

Vendors get a panel of their own, and the money behind it is put on one footing: one currency in the ledger, and refunds that take back exactly the commission that was credited. Update MHM Rentiva to 6.1.5 first, then Pro. If Pro finds an older Rentiva it switches itself off with a notice and creates nothing.

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.

This release is mostly about one question: what happens when an account is deleted. The answer, in 6.0.0, was worse than it should have been in three separate places — and one of them destroyed a customer's messages on sites that had never bought the compliance feature at all. Update MHM Rentiva to 6.1.4 first, then Pro. There is no data migration and no hook renames this time.

If a guest booked with you first and created an account afterwards, the Customers screen could not see that booking. The customer's row read 0 bookings, their money never reached the summary cards at the top, and "View Bookings" showed an empty list. 6.1.4 fixes that, and it asks nothing of you: no database change, no re-saving of settings.

This is a major release, and the first Pro build published since 5.2.3 at the end of July. Two sentences cover most site owners: update MHM Rentiva to 6.1.3 first, then Pro, and your data moves itself the next time you open the admin. Everyone else — anyone with custom code hooked into Pro — has a short list to read first, because 70 hook names changed and nothing warns you when one stops firing.

If your vehicle detail fields were configured before 6.1.2, adding gallery images and pressing Update could wipe the gallery you had just added. 6.1.3 stops that, and it asks nothing of you: no database change, no re-saving of settings. Installing it is enough.

If a customer paid and then cancelled, Rentiva marked the booking as awaiting a refund and stopped there. No money moved. Somebody had to notice and refund it by hand. From 6.1.0 the cancellation carries the refund through to your payment gateway itself.

MHM Rentiva is now published on the WordPress.org plugin directory. You install it the way you install anything else — search for it, click install — and WordPress keeps it updated from there on.