Changelog

0.37 Rent Fetch July 6, 2026

Rent Fetch 0.37 adds more control over how property information is displayed across your site.

Property fee toggle

You can now choose whether to show property fees globally. When fees are turned off, Rent Fetch will hide fee details and display pricing as if no fees are attached to the property, floor plan, or unit.

Unit-level square footage

This release also improves unit information by adding support for unit-level square footage display, making it easier for visitors to compare available units with more complete details.

0.36.5 Rent Fetch June 17, 2026

• Updated styling for password fields in the RF admin so the Yardi API key field displays consistently with the rest of the settings screen.
• Added a new Apply Online URL field for properties. When populated, this displays as an Apply Online button on the single property page.
• Added date controls for property specials, allowing a special to be shown during a specific date range, after a start date, or until an end date.
• Improved the single property specials display for cases where only a specials headline is entered without body text.
• Updated the default caching behavior for new Rent Fetch installs so query caching is off by default. This only applies to fresh installs; existing sites and copied sites will keep their saved caching setting.

0.15.6 Rent Fetch Sync June 11, 2026

• Improved sync safety checks so cleanup only runs when the API response is considered valid for deletion decisions.
• Fixed an Entrata sync issue where available units could be removed during cleanup even though they were still present in the Entrata API response.
• Improved Entrata unit syncing so units are matched and retained using Entrata’s actual unit IDs instead of response list positions.
• Added cleanup support for Entrata-synced properties, floor plans, and units that are no longer part of the site’s configured Entrata property list.

0.36.4 Rent Fetch June 4, 2026

Search/cache reliability fixes:

• Empty property/floorplan search results are no longer stored in search/query transients.
• Existing empty cache entries are treated as misses.
• All-unavailable floorplan aggregates and rendered results are not cached when no result has positive availability.

RentFetch admin bar improvements:

• Cache controls always show, even on sites with five or fewer properties.
• Dropdown spacing, singular labels, and sync status display were refined.
• Healthy sync summaries are shown as non-clickable text.
• Inactive sync status rows no longer take up space.

Sync settings fix:

• Saving sync settings now clears cached Rent Fetch Sync API bootstrap error state, including stale refresh locks.

Documentation:

• Admin documentation menu link now points to the Rent Fetch getting started docs.

0.15.3 Rent Fetch Sync June 4, 2026

Making a number of changes around a significant, intermittent bug that was introduced in 0.14.2 of the Rentfetch Sync plugin. Notably, this bug could cause floorplans to be repeatedly deleted and re-synced with a site, with the primary long-term consequence being loss of custom-input data on those floorplans specifically.

In detail: recent Sync scheduling/bootstrap changes made sites resolve credentials and Yardi bearer tokens at runtime, while a cache regression allowed a non-array/error value in the rentfetch_api_info transient to be treated as valid bootstrap data; when that happened, rfs_get_yardi_bearer_token() returned null, the Yardi floorplans request produced no usable authoritative floorplan list, and the old orphan cleanup interpreted that empty/missing data as “all floorplans are gone” and deleted the synced floorplans and related units. We hardened this in two layers: first, the central API bootstrap cache now only accepts validated array responses with required token fields, stores errors separately, deletes legacy poisoned transient values, and falls back to the last known good bootstrap response; second, Yardi floorplan orphan deletion now only runs when the floorplans API response is explicitly authoritative, preserving legitimate floorplans: [] cleanup while refusing to delete anything on blank, malformed, missing-key, request-error, or non-200 responses.

The combination of these two bugs would only rarely have negative consequences. Typically, the failure state would begin when an upstream request failed, such as a request to the Yardi API or RentFetch API, or when cached/bootstrap data entered an invalid state and was reused. However, across many thousands of syncs, rare states happen frequently enough to matter, and a handful of sites appear to have been impacted.

Please note that this bug was introduced on May 28th. If any floor plan data is missing from a site, restoring to a database backup from the 27th or before would restore the floor plan and unit custom meta that might otherwise be lost.

0.15.1 Rent Fetch Sync June 1, 2026

This release focuses on making full-site syncs faster, safer, and easier to monitor from inside WordPress.

Faster full sync controls

Rent Fetch Sync now includes an accelerated “Run full sync now” option. Instead of waiting for the normal scheduled sync cycle to work through each configured property, admins can manually start a full sync when they need fresh data right away.

The accelerated sync uses a controlled worker queue with up to five concurrent sync workers. That means it can move through configured Yardi, Entrata, and Rent Manager sync targets more quickly while still avoiding an uncontrolled burst of requests.

The “Run full sync now” control is available from the Sync settings screen and also from the Rent Fetch admin bar tools when those are available.

Safer sync start behavior

Starting a full sync now automatically enables Data Sync before the run begins. This makes it easier to recover from a paused sync state without having to remember to change the Data Sync option first.

While an accelerated sync is already running, the start controls are hidden or disabled so another full sync cannot accidentally be launched on top of the active one.

Sync cancellation support

Accelerated syncs can now be cancelled while they are running. When cancellation is requested, pending accelerated sync actions are unscheduled and the sync state is marked as cancelled.

The admin interface updates to show the current status, then clears completed or cancelled messages after a short period so stale status messages do not keep reappearing after page reloads.

Clearer progress feedback

The sync UI now reports progress while a full sync is running, including how many sync items have completed and which items are currently active.

This gives admins better visibility into long sync runs, especially on sites with several synced properties or multiple enabled integrations.

Safer synced-data deletion

The old “delete synced data” radio option has been replaced with a safer deletion workflow.

Admins now use a dedicated “Delete synced data” action that opens a confirmation modal. The modal shows how many synced properties, floor plans, and units are available to delete, and requires typing “delete” before the destructive action can begin.

This makes accidental synced-data deletion much harder, and more performant, in that we should no longer crash the site when we’re deleting over a couple thousand records at the same time.

Queued deletion with progress tracking

Deleting synced data now runs through a queue instead of attempting to delete everything immediately in one request.

The deletion process works through synced units, floor plans, and properties in batches, reports progress as it goes, and shows a breakdown of how many records have been deleted from each content type.

This is safer for larger sites and reduces the chance of timeouts during cleanup.

Data Sync is paused before deletion

When synced-data deletion begins, Rent Fetch Sync automatically sets Data Sync to “No sync” and unschedules normal sync actions. This prevents new sync work from running while synced records are being removed.

If an accelerated sync is running, it is cancelled before deletion starts.

Better handling of optional sync data

Some synced data sources are useful extras, but should not make an entire property look like a failed sync if they return no usable records.

In this release, missing or unusable Yardi property images and Yardi lease-fee responses are treated as partial sync states instead of hard failures. This gives a more accurate admin status when the main property data synced successfully but optional enrichment data was unavailable.

Improved sync status rollups

Sync status rollups now understand partial sync states. A record can show as partially synced when optional endpoints had issues, while still distinguishing that from a true failed sync.

This should make the sync status indicators more useful for day-to-day troubleshooting.

Cleaner status messages

Completed and cancelled sync/delete messages now clear more quickly. This prevents old “complete” or “cancelled” messages from lingering in the admin after the action has already finished.

Overall

Rent Fetch Sync 0.15.1 is mainly an operational release. It gives admins better control over full syncs, makes destructive cleanup safer, improves progress visibility, and makes sync statuses more accurate when optional API data is incomplete.

0.36.2 Rent Fetch June 1, 2026

This release cycle focused on making Rent Fetch easier to manage inside WordPress, improving visibility into sync and cache status, and adding a few practical property-level tools for leasing teams.

Property specials are now easier to manage

Properties now have a dedicated Property Specials box in the editor. Site admins can toggle specials on or off, add a short specials heading, and add a brief specials message.

When a heading or message is entered, the single property page can show a specials banner near the top of the property details section. The banner uses the site’s existing Rent Fetch accent colors, includes a sale-style icon on larger screens, and simplifies down on mobile.

Resident portal links are now supported

Property editors now include a Resident Portal Link field. When this is filled in, the single property page displays a Resident Portal item alongside the property’s contact information.

The link is formatted like the existing website link, including shortened display text and opening external links in a new tab.

Property editor layout improvements

Several property editor boxes were cleaned up to make them easier to scan and use.

The Property Contact Information and Property Location boxes now use a more compact layout that better fits common fields like email, phone number, address, city, state, and ZIP code. Input heights were normalized so these fields feel more consistent with the rest of WordPress.

The Property Fees box was also adjusted for properties where authoritative API fee data is available. In that case, Rent Fetch now keeps the editor focused on the synced API fee preview instead of showing manual fee tools that are not relevant for that property.

Better sync visibility in WordPress

Rent Fetch now includes clearer sync status indicators in the WordPress admin. Properties, floor plans, and units can show sync status dots, hover details, and filtering options so site managers can more quickly understand which content is current and which content may need attention.

This is especially useful for sites with multiple properties or multiple synced data sources.

New Rent Fetch admin bar tools

A compact Rent Fetch dropdown was added to the WordPress admin bar. It gives quick access to useful operational information, including content counts, sync status summaries, cache controls, and performance-related links.

This makes common maintenance checks easier to reach without digging through settings screens.

Search cache controls and reporting were improved

Search cache controls are clearer and more useful. Rent Fetch now gives better visibility into cache and preload status, includes easier cache clearing, and supports preloading popular searches.

Cache statistics were also refined so administrator and logged-in user activity does not inflate public cache hit and miss reporting. This makes the performance data more representative of real visitor behavior.

General admin polish

Several admin screens received small visual and usability refinements, including spacing, headings, links, toggle controls, dropdown styling, and metabox layout improvements. The goal was to make Rent Fetch’s backend tools feel more organized and easier to work with during day-to-day property updates.

0.14.2 Rent Fetch Sync May 28, 2026

This update improves background sync reliability and server performance by spacing out large sync workloads, reducing duplicate API calls, and automatically cleaning up old scheduled task records. The primary impact here is actually on a local development site or on sites that receive very little traffic, but have significant numbers of properties. So it shouldn’t affect all that much “in the wild,” but it’s become an annoyance when working on this plugin: the very first time that I load it up (when it has hundreds of queued jobs), it’s taking 30 seconds to start up the site.

• Improved how background syncs are scheduled so that large sites do not try to process every property at the same moment after a quiet period or restart.
• Reduced the chance of a sudden burst of requests to the Rent Fetch API by reusing recent site/bootstrap information when multiple sync tasks start close together.
• Changed scheduled sync tasks to store less information up front, so they use current connection details when they actually run.
• Added cleanup for old completed, canceled, and failed scheduled tasks so the database does not keep growing from routine background activity.
• These updates should make first-load and cold-start behavior calmer and more predictable, especially on sites with hundreds of properties.

0.35.8 Rent Fetch May 14, 2026

This release includes a broad set of improvements across single-property pages, floor plan displays, search behavior, caching, and frontend styling. The main goal is to make Rent Fetch pages easier for visitors to use, more predictable for site owners, and easier for developers to customize.

Single Property Pages

Single-property pages have been reorganized and polished so property details, contact information, and floor plans work together more cleanly.

• Redesigned the property details and floor plans area into a unified layout with main content on the left and key property links in a sidebar.
• Added a cleaner sidebar experience for address, website, phone, email, office hours, tour booking, and video tour links.
• Improved sidebar spacing, sticky positioning, button alignment, and tour-link styling.
• Added unique classes to sidebar contact fields so developers can target address, website, phone, and email output more precisely.
• Added a “More” control for longer property descriptions so pages stay easier to scan.
• Refined property statistics, section headings, spacing, and divider styles.

Floor Plan Display Improvements

Floor plan cards and search results have been refined, especially on mobile screens.

• Improved floor plan card spacing so pricing, attributes, and dividers feel more balanced.
• Refined mobile typography for floor plan names, pricing, availability, and attributes.
• Improved mobile availability spacing and filter button padding.
• Updated default card styling to use cleaner borders with hover-only shadow treatment.
• Improved responsive wrapping for floor plan attributes and two-column mobile layouts.
• Adjusted card overlay stacking and attribute separator spacing.

Smarter Filters

Filters now behave more appropriately when Rent Fetch is showing floor plans for a specific property or property group.

• Scoped floor plan filter options to the current property or property list when searches are property-specific.
• Kept global filter caching for general floor plan searches while avoiding stale cached options in property-specific contexts.
• Hid bed and bath filters when there is not enough useful choice to show visitors.
• Reduced property and floor plan filter font sizing for a cleaner interface.

Search Improvements

Search results should now feel more relevant and more reliable, especially for property searches.

• Property text search now matches address, city, state, and zip code fields without requiring Relevanssi.
• Property search avoids matching broad taxonomy, description, and content fields by default, keeping results focused on dedicated search fields and filters.
• Improved error handling for property and floor plan searches, with clearer frontend messages when something goes wrong.
• Added more specific server-side error references to help diagnose search issues.

Performance And Caching

This release includes several changes intended to keep searches fast while making cache behavior easier to understand and manage.

• Added configurable search/query cache lifetime handling.
• Reduced the default search/query cache lifetime from 10 days to 1 day while keeping stale refresh behavior.
• Added 1-hour stale refresh behavior so older cached results can still be served while fresh results are rebuilt.
• Added a 500-entry cap for stored search/query combinations.
• Prioritized cache pre-fetching for the most common tracked searches.
• Added a Performance cache dashboard with cache counts, age details, and cache hit-rate history.
• Added an optional setting to log cache hits, misses, stale responses, and refresh scheduling in the browser console.
• Allowed logged-in users to read existing cached search results without creating new cache entries.
• Only sends REST search nonces for logged-in users, improving compatibility for public searches behind page caches or CDNs.

Map Updates

Property map behavior has been refined for better consistency after filtering.

• Improved property map updates with shared InfoWindow handling.
• Reduced repetitive map bounds fitting.
• Improved matching between filtered grid results and map markers.

Styling And Customization

Rent Fetch’s default frontend styles are now more consistent and easier to customize.

• Added Rent Fetch spacing tokens and responsive font-size tokens.
• Softened property fee table divider styling.
• Normalized single-property sidebar action buttons and spacing for tour-related links.
• Improved default frontend styling hooks for developers and theme overrides.

0.34.2 Rent Fetch May 1, 2026

This release fully launches synced fees in RentCafe. While nothing is done in this release that will affect users who are entering their data manually, for users who are using the Rent Fetch Sync plugin to pull in their fees via Yardi/RentCafe, this release changes the logic to allow for public display of those fees, overriding any csv uploads on the backend of their site.

0.14.1 Rent Fetch Sync April 17, 2026

This release adds Yardi lease-fee syncing for properties so Rent Fetch can use current lease-fee data provided by the API. We also improved sync reliability by clearing outdated lease-fee data when Yardi returns an invalid or failed response. In addition, empty synced fee payloads will no longer override existing manual fee settings.

0.34.0 Rent Fetch March 16, 2026

Rent Fetch now exposes a signed monitoring endpoint and richer site/property health rollups so the central Rent Fetch API can safely poll client sites and power the new network-status dashboard.

• Added a signed monitoring status endpoint so the Rent Fetch API can poll client sites directly instead of routing this through the existing sync/bootstrap endpoint.
• Built a monitoring payload with site metadata, summary counts, endpoint summaries, exceptions, and per-property rollups for dashboard use.
• Rolled child issues up more cleanly so floorplan and unit failures can surface at the property level for monitoring.
• Added a built-in fallback monitoring public key path so API-initiated polling can work even before Sync has refreshed bootstrap data on a client.

0.14.0 Rent Fetch Sync March 16, 2026

Rent Fetch Sync now extends its existing API bootstrap flow to register each client’s callable origin and monitoring verification data, with a safe-mode dependency guard so this support does not introduce fatal failures when Rent Fetch is missing.

• Extended the existing API bootstrap flow to send site_origin and store monitoring bootstrap data returned by the Rent Fetch API.
• Kept monitoring-related bootstrap work inside the normal Sync credential/bootstrap path rather than creating a separate phone-home system.
• Added a dependency guard in plugin bootstrap so Sync now stays in a safe mode with an admin notice instead of fatalling if Rent Fetch is not active.
• Bumped release metadata and changelog entries to reflect the monitoring/bootstrap work.

0.13.0 Rent Fetch Sync March 14, 2026

Rent Fetch Sync 0.13.0 adds endpoint-aware sync status tracking, source-aware cleanup, and unit-source normalization so sync state is more reliable across Yardi, Entrata, and Rent Manager. It also hardens malformed or incomplete unit failure paths so bad vendor payloads fail cleanly instead of producing misleading green states or PHP notices.

0.33.4 Rent Fetch March 14, 2026

Rent Fetch 0.33.4 updates the admin sync indicators to use normalized sync metadata rather than parsing raw API response payloads for freshness/status. It also aligns the core plugin with the new sync-state model used across properties, floorplans, and units.

0.33.2 Rent Fetch March 8, 2026

One part of this release focuses on Google Maps loading behavior. We updated the way map assets are loaded so maps appear more reliably in the places they’re used, including property search results and individual property map views. In practical terms, this should help reduce cases where a map loads inconsistently or later than expected, while also improving the overall stability of map-driven browsing.

This release also adds a new location-based map filter for property search. Visitors can now narrow down results more easily based on location while using the map experience, making it simpler to explore properties in the areas they care about most. The result is a more intuitive map search flow, especially for multi-property sites where location is a major part of the decision-making process.

0.33.1 Rent Fetch February 25, 2026

Pricing & Fee Integration

• Fee-Inclusive Pricing: Implemented major updates to pricing displays across properties, floorplans, and units, including two-line output where applicable.
• Automated CSV Parsing: Added property-level monthly required fees parsing from CSV data with strict matching:
  • Matches rows where notes are exactly “required” (case-insensitive).
  • Matches rows where frequency contains “month”.
  • Handles price ranges (e.g., “$10-20”) by selecting the higher value.
• Metadata Storage: Monthly required fees are now stored as property meta and used as the source of truth for all pricing displays.
• Admin Controls:
  • Added editable monthly required fees field at the property level.
  • Added a global monthly required fees fallback setting.
  • Improved helper text regarding CSV overwrite behavior.

Caching & Performance

• Smart Refresh: Updated fee refresh logic to trigger during single-property/floorplan views and upon saving settings.
• CSV Caching: Added 30-minute short-term caching keyed by CSV URL to reduce redundant hits.
• Cache Busting: Implemented automatic cache clearing when property settings, global settings, or general “clear cache” actions are triggered.
• Validation: Refined logic to ensure missing or unparseable CSV data does not persist invalid totals.

Template & UI Enhancements

• Pricing Consistency: Updated property and floorplan outputs to resolve fees via property_id, ensuring consistent “Range” vs “Minimum” display modes.
• Unit-Level Pricing: Expanded unit pricing to derive totals from the connected property’s fee data.
• New Tooltip System: Refactored property-specific tooltips into a general-purpose “Rent Fetch Tooltip” system.
  • Added global admin setting for tooltip text via textarea.
  • Improved initialization for AJAX-rendered content.
• Layout & CSS: Updated styles for search grids and single templates to improve typography, spacing, and wrapping behavior.

Bug Fixes & Refactoring

• SEOpress Integration: Updated integration to output fee-inclusive pricing only when fees actually exist.
• Search Logic: Fixed property search bug where bedroom filters were not accurately reflecting pricing and availability counts.
• Cleanup: Removed legacy AJAX search handlers to streamline the codebase.
• Audit Trail: Added “Last CSV Check” context in admin to display specific contributing fee rows (description + price).

0.12.5 Rent Fetch Sync February 24, 2026

We fixed an issue that could cause Entrata form submissions to fail.

Here’s the error we were seeing:

The 'createdDate' should not be greater than current date-time.

What happened

• Our Entrata payload used a fixed UTC offset (-6 hours) to approximate Mountain Time.
• That only matches Mountain Daylight Time (MDT, UTC-6).
• On Mountain Standard Time (MST, UTC-7), this could make createdDate one hour in the future, which Entrata rejects.

What we changed

• Entrata createdDate (lead/contact submissions) and event date (tour submissions) now use timezone-aware America/Denver time.
• This automatically handles DST transitions (MST/MDT) year-round.

Why this matters

• The fix prevents seasonal timestamp failures and keeps Entrata submissions valid regardless of WordPress/site/server timezone settings.
• This aligns with Entrata documentation expectations for Mountain Time on these fields: Entrata API v1 docs (while Entrata is no longer on this version of the API, we don’t have reason to think that this particular eccentricity of the Entrata API has changed).

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.