FWRE Property Manager

Version 5.0.10: 1 update, 6 fixes.

Update: The add-on pages look finished on a phone too. The property manager's filters, its inquiries and bookings tables and the agent's profile form no longer run off the side of the screen. Their buttons, fields and tabs are at least 44px tall, and so are the share and brochure dialogs'. On a property page the title gets its own row, with the share, favourite, print and brochure buttons under it. Compare lines its row labels up with their values, and the listing's tax switch sits after the currency menu with its full label. The white text on the Latest module's photo cards sits on a darker shade, so it's readable on a bright photo, and the mortgage calculator's chart and legend line up with its fields. Your account pages, saved searches and favourites use the design's buttons instead of plain blue ones. On a phone the manager's lists and the compare table read well, and the slideshow listing shows its photo again. The PDF brochures look exactly as before.

Bugfix: Updating an add-on before the component no longer breaks your site. Agents, Custom Fields and Floor Plans showed an error in the admin when they were updated ahead of FW Real Estate itself. A few other add-ons and the search module did the same on some pages. Each one now works with the component you have and does what it did before, and you'll get the new behaviour once you update the component too.

Bugfix: No more "0" before an address. A property without a street number no longer shows a 0 in front of its street, wherever this add-on writes the address.

Bugfix: Emails carry your site's name and working links. Enquiry replies, shares and alerts now sign off with your site's name, link to the property with a full address that opens from any mail app, and show the property's type and status.

Bugfix: The front property editor opens only your own listings. A signed-in member who opened another owner's property in the front editor, by changing the id in the address, saw its title, address, price and other details in the form. Now any property that isn't theirs shows their own list of listings instead, as it did in version 6.

Bugfix: A member who isn't an agent can no longer publish a listing from the front editor. Any signed-in member could add a property from the front editor and have it go live at once, with no review. Now a member without a published agent profile saves it hidden, the form starts at Published = No, and the save says to contact the administrator to make it visible, as it did in version 6. A listing the administrator has already published stays published when its owner edits it.

Bugfix: Every real estate page has exactly one main heading. The agents list, compare, favourites, saved searches and the account and agent pages now show their own title, and on WordPress the page title your theme prints above them is no longer repeated. Search engines and screen readers get one clear heading per page.

Version 5.0.9, a hotfix: 1 fix.

Bugfix: The House type list closes after you pick a type. On the property form, in the back office and on the front editor, the House type list stayed open after a pick until you pressed Esc. It now closes as soon as you pick, and you can open it again to add a second type.

Version 5.0.8, a hotfix: 1 update.

Update: House type and category come first in the property form. On the property form's Property Info card, the type and category now sit at the top, above bedrooms and bathrooms, in the admin and in the front-end submission form alike.

Version 5.0.7, a hotfix: 1 fix.

Bugfix: Photos you upload together keep their file-name order. Photo 2 now comes before photo 10, on the property form and on the agent's own edit form.

Your agents' property lists keep working. A menu item made on version 6 for an agent's own properties opens that list after the upgrade.

Area units on the contributor form follow the active design, including a design that names its units rather than pointing at one site's list.

The contributor form reads and saves a property's status through its status labels, and saving there keeps the data of other add-ons.

The contributor pages can be added from the first steps and the Site menu card.

Two fixes on the contributor's own pages.

The edit link on a listing opens it. A contributor following the link from their own property reached the manager rather than the property.

Searching keeps you where you were. A search made from the manager returned to the right page instead of the first one.

Nothing about this add-on behaves differently. Its site templates now travel with the add-on itself rather than living in the design, so exactly the same markup is rendered from a different place. A design still has the last word: where a design offers its own version of a template, that version is used, as before, and a site that has customised one keeps every customisation.

⚠️ This version requires core 7.1.0, which is the release that knows to look inside an add-on for its templates. The add-ons catalogue will not offer it to an older core, so update the core first.

The rest of the release is work inside the source that a site cannot observe: the English catalogue was rewritten into the form the WordPress directory extracts translations from, and comments were shortened. The fifteen languages this add-on ships are unchanged.

No change you will notice. This release rebuilds Property Manager on the current engine: the markup it produces is now written the way each platform expects it, so nothing it prints can be mistaken for unescaped output. It adds no features and changes no behaviour — every page it draws was compared before and after, and they are identical.

The front-office property manager: the area where an agent or owner adds and edits their own listings without reaching your back office.

FW Real Estate 7.0 rebuilds the product on a new cross-platform engine. What this add-on does for you is unchanged — the features you use in 6.x are the features you get here. What is new is where it runs and how it reaches you:

• It runs on WordPress as well as Joomla, from the same code, so both editions stay in step.
• It has a version of its own. On Joomla that means it is delivered and updated from the store on that version, instead of arriving whenever the component happens to ship a release that bundles it. On WordPress it arrives inside the plugin if it is one of the free add-ons, or in the subscription pack it belongs to.

See the component release notes for the 7.0 story and for how to bring your data across.