Elementor-built pages are found: "Book now" buttons open your booking page again. On Elementor sites the vehicle pages may move under your vehicle-details page (old addresses redirect).<\/p>","6.3.0":"
Unticked e-mail templates and the "Send Booking Notifications" switch now really stop sending, and cancelled bookings send the customer one e-mail. Check your e-mail settings and Settings > Payment after updating. Rentiva Pro users: update Pro to 6.4.0 after this.<\/p>","6.2.1":"
Privacy fix: Elementor pages with Rentiva widgets could expose the saving user's account data to site search. A background job cleans affected pages. Purge page caches and search indexes after updating.<\/p>","6.2.0":"
Contact attachments move to a private folder and the customer dashboard is retired. Ten hooks were removed: custom code using them stops working. Rentiva Pro 6.1.0 or older breaks on the vendor panel: update Rentiva Pro to 6.3.0.<\/p>","6.0.1":"
Cleanup and bug-fix release. No action required; an automatic one-time migration removes some internal database indexes. If you build pages with this plugin's blocks, this release repairs the favourite and compare buttons on them.<\/p>","6.0.0":"
Major release. Data migrates automatically, but 113 hooks and every post type name were renamed: custom code that hooks or queries them stops working silently. See the changelog before updating.<\/p>","5.1.0":"
Security hardening and WordPress.org compliance. No action required; your settings and data are unaffected.<\/p>","5.0.2":"
Compliance housekeeping and translation improvements. No action required; your settings and data are unaffected.<\/p>","5.0.1":"
Maintenance and translation update. No action required.<\/p>","5.0.0":"
First WordPress.org release.<\/p>"},"ratings":{"1":0,"2":0,"3":0,"4":0,"5":1},"assets_icons":{"icon-128x128.png":{"filename":"icon-128x128.png","revision":3661857,"resolution":"128x128","location":"assets","locale":"","width":128,"height":128},"icon-256x256.png":{"filename":"icon-256x256.png","revision":3661857,"resolution":"256x256","location":"assets","locale":"","width":256,"height":256}},"assets_banners":{"banner-1544x500.png":{"filename":"banner-1544x500.png","revision":3661857,"resolution":"1544x500","location":"assets","locale":"","width":1544,"height":500},"banner-772x250.png":{"filename":"banner-772x250.png","revision":3661857,"resolution":"772x250","location":"assets","locale":"","width":772,"height":250}},"assets_blueprints":{},"all_blocks":[],"tagged_versions":["6.0.7","6.1.0","6.1.3","6.1.4","6.1.5","6.2.0","6.2.1","6.3.0","6.3.1"],"block_files":[],"assets_screenshots":[],"screenshots":[]},"plugin_section":[],"plugin_tags":[269,13605,35555,722,262926],"plugin_category":[40],"plugin_contributors":[277101],"plugin_business_model":[],"class_list":["post-314275","plugin","type-plugin","status-publish","hentry","plugin_tags-booking","plugin_tags-car-rental","plugin_tags-rent-a-car","plugin_tags-reservation","plugin_tags-vehicle-rental","plugin_category-calendar-and-events","plugin_contributors-maxhandmade","plugin_committers-maxhandmade"],"banners":{"banner":"https:\/\/ps.w.org\/mhm-rentiva\/assets\/banner-772x250.png?rev=3661857","banner_2x":"https:\/\/ps.w.org\/mhm-rentiva\/assets\/banner-1544x500.png?rev=3661857","banner_rtl":false,"banner_2x_rtl":false},"icons":{"svg":false,"icon":"https:\/\/ps.w.org\/mhm-rentiva\/assets\/icon-128x128.png?rev=3661857","icon_2x":"https:\/\/ps.w.org\/mhm-rentiva\/assets\/icon-256x256.png?rev=3661857","generated":false},"screenshots":[],"raw_content":"\n
MHM Rentiva is a vehicle rental management plugin for car and motorcycle rental businesses. You manage your fleet, availability and bookings from the WordPress admin; frontend payments are handled by WooCommerce, and administrators can also create and manage bookings manually.<\/p>\n\n
Everything described below works in full. There are no vehicle, booking or listing caps, no feature timers, and no locked screens.<\/p>\n\n
Features:<\/strong><\/p>\n\n Documentation and support<\/strong><\/p>\n\n Requirements:<\/strong> WooCommerce. It is declared in the plugin header and checked on activation, so the plugin will not activate without it. WooCommerce provides the cart, checkout and payment gateways used for frontend bookings.<\/p>\n\n This plugin does not send your data anywhere. It makes no requests to any third-party service: no analytics, no geolocation lookups, no remotely-hosted fonts or scripts. Every asset it loads, including its webfont, is served from your own site. Nothing about your site, your bookings or your customers leaves your server.<\/p>\n\n For completeness, the plugin's admin screens do contain ordinary hyperlinks to pages outside your site, which open only if you click them and send nothing when you do:<\/p>\n\n These are links, not integrations: the plugin performs no HTTP request to any of them. A check in our build guards against reintroducing the specific third-party services earlier versions used \u2014 geolocation lookups, CDN-hosted fonts and scripts, analytics and Gravatar \u2014 by failing if any of those hosts reappears in the PHP we ship.<\/p>\n\n MHM Rentiva stores its booking and customer records (such as names, e-mail addresses and phone numbers) locally in your WordPress database and does not transmit them anywhere.<\/p>\n\n Four other things it keeps are worth naming; three of them record an IP address, which in most jurisdictions counts as personal data in its own right.<\/p>\n\n If you publish the plugin's contact form<\/strong>, each submission is saved as a private record holding the sender's name, e-mail address, telephone number, company, the message itself, any file they attached, and the IP address<\/strong> and browser user-agent<\/strong> it was sent from. The record also keeps the rest of what the form submitted: which vehicle the enquiry was about, a preferred date, a priority, a rating, and which variant of the form was used. These records have no retention setting and are never removed automatically; you read and delete them yourself under MHM Rentiva \u2192 Contact Messages. Files attached to a contact message are stored in a plugin-owned folder inside your uploads directory ( If you publish the plugin's rating form<\/strong>, each review is stored as an ordinary WordPress comment, so WordPress itself records the reviewer's IP address and browser user-agent alongside it, exactly as it does for any comment \u2014 and for a review left by someone who is not logged in, the name and e-mail address they typed. Those guest reviews are reachable through Tools \u2192 Export\/Erase Personal Data, which matches comments by e-mail address. From version 6.0.1, a review left by a logged-in customer is saved the same way WordPress saves any comment from a signed-in visitor: against their user ID, and with the display name, e-mail address and website address from their profile written onto the comment. Those reviews are matched by the same Export\/Erase tools, on the account's e-mail address. Reviews that logged-in customers left in earlier versions carry no name and no e-mail address on the comment, and updating does not fill them in, so the Export\/Erase tools \u2014 which look comments up by e-mail address \u2014 do not return those older ones; remove them from the Comments screen instead.<\/p>\n\n The activity log<\/strong> records, for each entry, the IP address and browser user-agent of the request that produced it, along with the WordPress user ID where there is one. Unlike contact messages, log entries are deleted automatically after a retention period you set in the plugin's settings (30 days by default).<\/p>\n\n The e-mail log<\/strong> records, for each message sent through the plugin's notification system, the recipient address, the subject, whether delivery succeeded, and the booking details the message was built from \u2014 which for a booking e-mail means the customer's name, contact details and rental dates. The assembled message body itself is not stored. This log has its own retention setting on the same terms (also 30 days by default).<\/p>\n\n Booking records themselves do not store an IP address: no code path in this version writes one, whether the booking comes through WooCommerce checkout or an administrator enters it by hand. Records created by older versions may still carry an IP address and user-agent; where they exist they have no expiry and go only when the booking is permanently deleted.<\/p>\n\n If you keep a privacy policy, these are the parts of the plugin it should describe.<\/p>\n\n The plugin registers no personal-data exporter or eraser. Contact-form submissions are not covered by Tools \u2192 Export\/Erase Personal Data: search for them by e-mail address under MHM Rentiva \u2192 Contact Messages and delete them there.<\/p>\n\n A separate paid Rentiva plugin adds a multi-vendor marketplace, VIP transfers with location-based routes, customer messaging, advanced reports and vendor payouts. It is a separate add-on plugin. Nothing described on this page is withheld or limited to promote it, and this plugin never advertises it to you in the admin.<\/p>\n\n Most of this plugin is plain, human-readable PHP with no build step.<\/p>\n\n Five admin screens (Dashboard, Customers, Contact Messages, About and Shortcode Pages) are built in React. Their compiled bundles ship in The build tooling itself ( https:\/\/github.com\/MaxHandMade\/mhm-rentiva<\/a><\/p>\n\n To rebuild the admin bundles from source, clone or download that repository and run the following from the repository root:<\/p>\n\n The build uses @wordpress\/scripts<\/a> (webpack). Run Three bundled JavaScript libraries and one webfont ship with the plugin -- two of the libraries on the front end, one in the admin dashboard only -- all permissively licensed and with public upstream source.<\/p>\n\n Two are pre-built (minified) under One is compiled into the admin dashboard bundle ( One webfont is bundled under \n
mhm-rentiva\/v1<\/code> for availability checks, customer records and admin dashboard data.<\/li>\n\n
External services<\/h4>\n\n
\n
Privacy<\/h4>\n\n
wp-content\/uploads\/mhm-rentiva-private\/contact\/<\/code>) under a random name with no file extension. They are not encrypted<\/strong>. On Apache the folder ships with an .htaccess<\/code> that denies direct access; on nginx you must add a location ^~ \/wp-content\/uploads\/mhm-rentiva-private\/ { deny all; }<\/code> rule yourself, otherwise the only protection is the unguessable name and the folder's empty index page. If you use a plugin that copies every upload to external storage (a CDN or cloud offload plugin), exclude the mhm-rentiva-private<\/code> folder in its settings, or it may copy these files as well \u2014 or, if it moves files away from your server, contact attachments may fail to upload. The file is deleted when the message is permanently deleted, and when the plugin is deleted with its \"Wipe all data on uninstall\" setting turned on. On a multisite network that wipe covers the main site only: delete the other sites' mhm-rentiva-private\/contact\/<\/code> folders by hand. A copy is also sent as an attachment of the notification e-mail, which this plugin does not control once sent. Attachments saved by earlier versions were public files in the normal uploads folder; updating moves those it can positively identify into the private folder and lists the rest in an admin notice.<\/p>\n\nA paid version exists<\/h4>\n\n
Source code<\/h3>\n\n
build\/admin\/<\/code>. They are generated from un-minified React sources that are NOT part of this ZIP: those live in the public GitHub repository linked below, under src-react\/<\/code>, next to the build tooling. What does ship under src-react\/<\/code> is plain CSS: the five screens' stylesheets and the shared admin stylesheet (src-react\/shared\/admin.css<\/code>) that the vehicle, booking and add-on list screens load directly. No obfuscated code is bundled.<\/p>\n\npackage.json<\/code>, webpack.config.js<\/code>) is not included in this plugin's ZIP -- it lives only in the public GitHub repository, alongside the same src-react\/<\/code> sources:<\/p>\n\nnpm install\nnpm run build\n<\/code><\/pre>\n\nnpm start<\/code> instead of npm run build<\/code> for a watched development build.<\/p>\n\nBundled third-party libraries<\/h4>\n\n
assets\/vendor\/<\/code>:<\/p>\n\n\n
build\/admin\/dashboard.js<\/code>) by the build described above, and is declared as a dependency in package.json<\/code>:<\/p>\n\n\n
assets\/vendor\/fonts\/<\/code>, served from your own site rather than from a font CDN:<\/p>\n\n