Skip to main content

Rentiva 6.2.0 — Contact messages get their own screen, the customer dashboard retires, and ignored block and Elementor settings now apply

· 6 min read
MaxHandMade
MaxHandMade
Maintainer

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.

Contact messages get their own screen​

MHM Rentiva > Contact Messages is a new screen: statistics, New / Read / Replied tabs, a month filter, search, bulk actions, and a detail view with the sender's card and their other messages. You can reply by e-mail, mark a message as replied, and the menu shows how many are unread. Links to the old list and edit screens open the new one, and existing messages are marked as read once, on update.

Attachments move to a private folder​

Contact-form attachments are now stored in a private folder, uploads/mhm-rentiva-private/contact/, under random names. They can only be downloaded through the administrator's Download button, and deleting a message deletes its file. On update, existing attachments are moved there and their old public addresses stop working; any file that cannot be moved is listed once in an admin notice. Attachments are capped at 5 MB.

  • On nginx, add the deny rule from the privacy section of the plugin's readme: location ^~ /wp-content/uploads/mhm-rentiva-private/ { deny all; }. On Apache the folder ships with an .htaccess that denies direct access.
  • Using a media offload plugin? Exclude the folder from it.

The customer dashboard is retired​

[rentiva_user_dashboard], its block and its Elementor widget no longer render a dashboard. A logged-in customer sees one line and a link to My Account; visitors see nothing; administrators also see a notice asking them to remove it from the page. The block and the widget are hidden from the editors, and Shortcode Pages no longer offers to create the page. Customers find their bookings, favorites and payments on My Account. See Master account dashboard (retired).

Block and Elementor settings that were ignored now apply​

  • Saved settings reach the page. Among them: the contact form's type, phone, company, vehicle, priority and attachment fields, theme and auto-reply (every form used to render as "general"); the vehicles list's Columns; the vehicle details "Ratings & Reviews" section, which now follows "Show Reviews"; the availability calendar's height. The defaults keep the old look, so a page only changes where one of these settings had been changed.
  • Elementor style controls for vehicle cards, lists, grids, featured vehicles and the booking button now style the page — most of them matched nothing before. Colours or spacing you saved earlier but never saw may now appear.
  • Block settings stick. A setting changed in the block editor and saved is no longer overwritten on every render.
  • Settings that never did anything were removed from blocks, widgets and shortcodes. A saved value is simply ignored and the page renders as before. The shortcode pages in these docs no longer list them.
  • Two shortcode attributes were renamed in practice: Featured Vehicles no longer reads show_book_button — use show_booking_button="0" — and Unified Search no longer reads layout — use search_layout="vertical". Search Results has a single Default Sort Order (default_sort) instead of Sort By and Sort Order.

Smaller things you will notice​

  • Vehicle cards show a 3:2 image and the vehicle's real rating; a vehicle without ratings shows none, and the placeholder "★ 4.8 (120 reviews)" is gone. The booking button reads "Unavailable" when the vehicle is out of service, and otherwise follows the widget's text, then your global "Book Now Button" text. The booking form takes the same look and matches the vehicle details layout.
  • Customers screen: Total Spent, Active, VIP and Avg. Spend count only completed or confirmed bookings, customers who checked out through WooCommerce show their phone and address, and a customer with two phone records no longer appears twice.
  • My Account lists: Payment History page 2 can be reached again, and My Bookings and Payment History filter before paging, so a filtered page is full.
  • Testimonials' "Load More" keeps the order, filters and display options.
  • The front end no longer turns dark because the visitor's operating system is in dark mode; your theme and the plugin's own Dark Mode setting decide.

Security and privacy​

  • A vehicle's gallery and featured image accept only images the editing user uploaded or may use, and never a sensitive document. Gallery entries stored earlier are shown only when their origin is trusted. Attaching an image to a vehicle requires permission to edit that vehicle.
  • A contact form's custom recipient (email_to) is used only while that address is still set on the page that holds the form; otherwise the message goes to the global recipient.
  • The visitor's IP address is no longer included in the admin e-mail, and the contact form's type and priority are checked against the allowed values.
  • The database cleanup no longer deletes Rentiva Pro's message-thread, commission-hold and vendor IBAN records.

For developers​

Ten hooks and the customer dashboard classes were removed, including the mhmrentiva_dashboard_* filters and three mhmrentiva_availability_calendar_* filters; render_shortcode() and output_shortcode() remain as deprecated shims — use render_canonical(). New hooks include mhmrentiva_contact_recipient_fallback, mhmrentiva_gallery_attachment_allowed and mhmrentiva_retired_dashboard_notice, plus REST routes under mhm-rentiva/v1/contact-messages (administrators only). Three database steps run once on update: contact statuses, contact attachments and Elementor style ids.

Where to get it. 6.2.0 is on WordPress.org and on GitHub as v6.2.0; both carry the same files. WordPress.org holds new versions for a few hours before sites are offered the update. Using Rentiva Pro? Update Rentiva first, then Pro to 6.3.0 — Pro 6.1.0 or older stops with an error on the vendor panel beside this release. The full changelog in both languages ships with the plugin.