FWRE Property Manager

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.