Rentiva 6.2.1 — Elementor widgets no longer write the saving user's account data into a page's stored text
6.2.1 is a privacy fix for sites that build pages with Elementor. Rentiva's Elementor widgets could leave the account data of the person who saved a page inside that page's stored text, where the site search could find it. This release stops that and cleans up the pages already affected. It is published on WordPress.org, so WordPress offers it to you as an ordinary update. If you use Elementor, update now and do the two steps under "After updating".
What was wrong
When a page, post or template holding a Rentiva Elementor widget was saved, Elementor also stored a plain-text copy of it in the post content. The Rentiva widgets wrote into that copy what the person saving it saw: their bookings, payment history, favourites, e-mail address and security tokens. The site search reads that copy, so on a published page anyone could find this data.
What changes
- Rentiva widgets write nothing into the plain-text copy Elementor stores when a page is saved.
- They also leave Elementor's markdown copy empty and are never stored in Elementor's shared element cache, even when a widget's Cache Settings is set to Active.
- Visitors see no change. The page itself still shows each visitor their own data.
Affected pages are cleaned up for you
After the update, a one-time background job rebuilds the stored plain text of every Elementor page, post and template that holds a Rentiva widget, drafts included, and drops its cached markdown copy. It runs through WP-Cron in batches of 50, retries pages that fail and waits longer between tries while it cannot make progress. It does not change a page's modified date or create a revision, so your pages keep their dates and history.
After updating
- Purge your page cache, so cached copies of an affected page are replaced.
- Using a search plugin? Rebuild its index, so it forgets the old text.
- Optionally, clear Elementor's own cache under Elementor > Tools > Clear Files & Data.
Older revisions of an affected page still contain the old text. Only users who can edit that page can see them.
Where to get it. 6.2.1 is on WordPress.org and on GitHub as v6.2.1; both carry the same files. WordPress.org holds new versions for a few hours before sites are offered the update. The full changelog in both languages ships with the plugin.
