Changelog

0.12.4 Rent Fetch Sync February 10, 2026

Updating our hooks to match the new rent-fetch pattern as we split out our general settings page into multiple subpages.

0.32.7 Rent Fetch February 10, 2026

• Security: sanitize tracked search params and escape tracked search output in the admin UI to prevent stored XSS. (NOTE: This should close a vulnerability disclosed to us by WordFence, which could allow an attacker to store a payload in a transient.)
• Security: sanitize cached meta values before storing transients.
• Security: correct attribute escaping in search filters (baths/pets).
• Verification: confirmed tracked search counts increment and beds/baths filters render correctly.
• Splitting the General settings page into subpages, as our options there have nothing to do with each other and are getting lengthy.

0.12.3 Rent Fetch Sync February 10, 2026

• Security hardening: escaped Rent Manager settings output in wp-admin to prevent unsafe rendering of option values.
• Security hardening: sanitized Rent Manager properties data before storing it, including support for both list and single-object API response shapes.
• Security hardening: removed unsafe HTML concatenation in frontend form submission handling and switched to safe text-node rendering for success/error messages.
• Security hardening: escaped and validated Entrata availability data before rendering date/time UI in the browser.
• Security hardening: sanitized request metadata (`REMOTE_ADDR`, `HTTP_USER_AGENT`) before storing form entry meta.
• Security hardening: added write-time sanitization for externally sourced unit/property/image meta in Yardi/Entrata/Rent Manager sync flows.
• Minor hardening: escaped sync metabox label text output in wp-admin.

0.32.6 Rent Fetch February 6, 2026

• Improved the loading of the RentFetch property map and RentFetch single property map to eliminate a console warning about the maps JavaScript library loading the wrong way.
• Added a console notice explaining Google’s deprecated map markers warning and why we cannot switch to the new implementation without requiring per-site Map ID updates.
• Reduced console noise by removing unnecessary debug output and cleaning up minor warnings.
• SEO Press updates: added new variables (including pricing), improved existing ones, and updated floorplan bed labels to output “Studio” instead of “0”. Hat tip to Ryan for spotting the issues.
• Feature: Adding Google Analytics integration (documentation here)

0.32.6 Rent Fetch January 23, 2026

This is a minor release. We fixed a number of issues and had a number of minor technical improvements.

New functionality

Added several new variables and improved existing ones in our SEO Press integration. Hat tip to Ryan for noticing these issues.

• Adding parameter for pricing.
• Updating the parameters for floor plans so that we’re not outputting things like “0” in the title element but are rather outputting “studio”.

Minor bugfixes

• Improved the loading of the RentFetch property map and RentFetch single property map to eliminate a console warning about the maps JavaScript library loading the wrong way.
• Google deprecated its map markers functionality almost two years ago. There’s a warning that always shows up in the console to this effect, and I attempted to move away from that implementation. Unfortunately, the new implementation requires a unique map ID that would happen on an API basis, meaning that every single site that’s launched already that has a different API key (which is probably almost each of them individually) would need to update their API setup in order for the new version to be functional. That doesn’t seem feasible or worthwhile to do. I’ve added a console warning explaining this breaking change and the reason for Google’s console warning.
• We fixed a number of other console notifications. A lot of this cleanup is because we’ve been doing some debugging in the console for forthcoming additions to Rent Fetch, and I wanted to clean up our notifications for things that we don’t need to be debugging to the console at all times. We also had a number of minor things happening that could be slightly improved to avoid outputting a warning to the console, and that’s just fine. Please note that most websites, particularly interactive ones, will have a large number of notifications and output to the console. This isn’t necessarily an indicator that anything’s wrong, but we want to clean up after ourselves a little bit.

0.12.2 Rent Fetch Sync January 23, 2026

Bugfix release to remove some debugging information we were sending to the console.

0.32.5 Rent Fetch January 15, 2026

This is a relatively minor release with one bug fix/augmentation for clicks on shortcodes visually showing that they’ve been copied, and one new feature.

New feature: SEOPress dynamic variables

In SEOPress, you can now use Rent Fetch variables for properties and for plans to highlight attributes of those within your title element, meta keywords or meta description element, and other places within the plugin, including schema.

Here’s what that looks like in practice (more documentation for our SEOPress meta available here):

Bug fix: Shortcode copy/paste animation

Click event on shortcode display has been fixed.

0.32.4 Rent Fetch January 7, 2026

This is a minor update, where we’re just fixing minor issues that have come up and making small improvements to existing features.

• Adding styles to harden our fees tables (we’re seeing some theme defaults override things they shouldn’t, in particular line breaks are happening in odd places on mobile).
• BUGFIX: Removing duplicate fees notes (accidentally added this twice in contexts where the site is a single-property site).
• Minor cleanup of styles in regards to property fees

0.32.3 Rent Fetch January 7, 2026

Two features have been added in 0.32.3.

Customizable fees description text

Much more information documented here. Basically, there’s now a mechanism to customize the highlighted text below:

Long notes for fees

In this version, we’re adding a new ‘longnotes’ column in the property fees csv file which will trigger an info box that’s hoverable, intended for long-form content to keep the fees compact and readable.

0.32.2 Rent Fetch December 19, 2025

We’ve added validation to fees .csv uploads and more consistent handling for whether csvs that are “sort of” valid are used (generally, they should be used more often).

The problem reported was that .csv files with extra columns or blank columns, or which were missing one or more optional columns, were failing validation and weren’t being used as a result. Those should now work, and our new validation should show what’s missing and what’s present at a glance.

0.32.1 Rent Fetch December 10, 2025

This release includes substantial changes to our property fees structure, simplifying the settings and adding capabilities to use .csv files loaded from Google Sheets (here’s how to do that), letting you manage your property fees in a friendly, extensible format.

Here’s a quick rundown of the new capabilities:

0.12.1 Rent Fetch Sync December 7, 2025

Implementing a proxy for all API calls to RentManager to centralize the source of all of our API requests. Moving forward, user sites will query the RentFetch API, which will in turn query RentManager, so that we’re always calling it from the same IP address.

0.12 Rent Fetch Sync December 3, 2025

In this release, we add a capability for our native forms to send into the Yardi API. Please note that this requires that the client be using Rent Fetch Sync and has all of their data plugged in on the backend (because we use those credentials to send the data).

0.31.3 Rent Fetch December 1, 2025

We’re currently capturing URL parameters for our properties and floorplans searches to make searches bookmarkable. This only functions after the page has already loaded and the search has submitted (this is secondary to the page loading). It has the side effect, after the search has completed, of stripping extraneous parameters from the page.

We’ve had a concern brought up as to whether this affects Google Analytics tracking. The short answer is no, this happens after the page has fully loaded, so it doesn’t impact GA tracking regardless – but this release will preserve any UTM parameters passed onto a page with a floor plan or property search, to avoid the appearance that we’re removing tracking from those.

0.31.2 Rent Fetch November 25, 2025

This is a minor release, changing how some of the functionality works for the new rentfetch_property_info shortcodes.

• Removing the icon/styles from the shortcode version of the property data buttons
• Fixing style bug for the office hours in some situations.

Basically, these should be buttons with icons by default on a corporate site (multiple properties) on the properties template, but should just be text links when output by the shortcode (these can obviously still be styled by a theme, and the svg icons are still there, just hidden, so they should be easy to turn back into buttons.

Here’s a video walking through it:

0.31.1 Rent Fetch November 20, 2025

This is a major release, with large performance imrovements, along with some incremental improvements.

Performance improvements

• Moving the entire search (for both properties and floorplans) to use REST instead of admin-ajax.
• Adding transient-based cache setting for preloading
• Adding UI to show recent uncached searches.
• Adding UI to clear the transient cache
• Adding database indexing and associated UI

Icon set update

• New icons for single-properties buttons
• New single-properties button to show office hours, if synced.
• Updating shortcodes with new button and icons

Bugfixes re: copying/pasting shortcodes

• Restoring capability to click on shortcodes on the site backend to copy them to the clipboard.
• Fixing link to the floorplan shortcodes page that wasn’t going to the specific shortcodes page of the floorplan settings.

0.11.11 Rent Fetch Sync November 12, 2025

Capability for Yardi to sync office hours on the property level into our meta information for properties

0.30 Rent Fetch November 12, 2025

• Add new metabox for properties to show office hours.
• Add office hours functionality to the property functions, with an appropriate function to get the markup, one to echo the markup, and an appropriate filter.
• Add office hours to the shortcodes capability
• Add detection for whether we’re syncing this to disable these fields on the backend if these are synced values.
• This functionality depends on Rentfetch Sync 0.11.11 for the actual syncing capabilities; these updates make manual entry possible, however.

0.29.5 Rent Fetch November 6, 2025

RF 0.29.5 is pushing live now with a speculative hotfix for the nonce notice you’re seeing on some sites (seems to be either caused or exacerbated by changes in caching on some of these sites, as this is a new issue that I don’t believe any of our recent changes should affect). We’re basically adding a few things to try to bypass the cache for a particular ajax request to get the nonce for purposes of the nonce being generated, which should result in us not seeing this issue anymore.

Please note that after the update, on affected sites, they won’t be “fixed” until the current site cache is cleared, so you’ll need to do that after installing the update (or wait the 10 hours or whatever it is until the cache refreshes).

0.11.10 Rent Fetch Sync November 5, 2025

• Entrata handling for units when there are zero units being returned by the API across a whole property
• Entrata handling for removing floorplans that no longer appear in the API.
• Both these changes are incremental improvements that became obviously needed with our new heirarchy view in the RF admin.

0.29.4 Rent Fetch November 5, 2025

Minor improvements across the board to the new backend heirarchy view. Apologies; I know I’ve been focused on this, but moving forward this is probably our front-line troubleshooting for issues with the various syncs, so it needs to be rock solid and as easy to use as possible.

• Heirarchy view: allowing for CMD/CTRL+click to open in a new tab.
• Heirarchy view: adding the unit IDs into the unit information
• Heirarchy view: more consistent styles and more obvious highlighting for where we are in the heirarchy.
• Heirarchy view: general style updates, simplifying the structure of this for consistency
• Heirarchy view: tooltips line-break and sizing when showing dates for multiple APIs (e.g. both Yardi and Entrata properties, since we call two APIs for each of these)

0.11.9 Rent Fetch Sync November 4, 2025

• This release adds new functionality to account for Yardi potentially sending 304 responses. We haven’t seen this in the wild yet, but we’re simulating a 304 response and handling that properly. We’re going to maintain the current data in all situations where there’s a 304 response, but we’re going to log those 304 responses on the site backend. A successful response will clear any recent 304s. This gives maximum visibility to you as to what’s happening if Yardi enables this functionality.
• We’re updating the UI of the manual sync slightly because it’s annoying that it asks each time if you want to refresh afterward (the answer is always going to be yes).
• Updating the RentManager sync to remove unit types that were removed from the API (our highlighting functionality made this problem visible; we hadn’t encountered it before).

0.29.3 Rent Fetch November 4, 2025

Adds support on the site backend to show the 304 logging

0.11.8 Rent Fetch Sync October 31, 2025

This is a minor release that does two things:

• Adds the sync highlighting and API debug information that was applied to Yardi earlier this week to RentManager properties/floorplans/units
• With that highlighting in place, it became clear that some units had moved between floorplans or been removed on one of our example properties. Added a minor update to change how we process units slightly to better remove units no longer in the API.

0.29.2 Rent Fetch October 31, 2025

Fixes a bug where, when some APIs (mainly the Yardi one where we see this happening) was sending through data with unescaped single quotes, our processing was accidentally converting those to double quotes (like don’t was becoming don”t).

0.8.18 Rent Fetch Sync August 15, 2025

• Add cookie-based lead source persistence: the frontend now stores the captured `lead_source` parameter in a sitewide cookie named `rentfetch_lead_source` for 30 days.
• JavaScript now uses the cookie as a fallback when session storage doesn’t contain the tracking parameter, ensuring outgoing external links still receive the lead source parameter.
• Shortcode update: `rentfetch_output_form()` now prefers an explicit `?lead_source` URL parameter, otherwise will fall back to the `rentfetch_lead_source` cookie (which overrides the shortcode `lead_source` attribute if present). This ensures cookie-based values do not overwrite explicit URL parameters.

0.22.5 Rent Fetch August 8, 2025

• We’ve now validated that phone numbers DO sync from Entrata if the client actually enters them. We’re reverting the change from 0.22.4 to disable manual editing of the phone number on entrata-synced properties, since those come from the API.
• More efficient queries for the main floorplans loop (for property searches and floorplan searches), as we’re seeing some examples of sites with 10k+ floorplans that were struggling. This should be a 1-to-1 change to the query, and should make the query component of the load time dramatically faster.
• Adding the backend column for ‘amenities’ to units for easier visibility into which units have amenities attached.
• Fixing the columns display on the admin for unit-level amenities.
• Fixing several sql duplicate joins that were throwing an error when searching the units for a particular unit, etc.