FWRE 3D Tour

The 3D tour is saved by this add-on, so saving a property keeps it.

This version needs FW Real Estate 7.1.4.

Nothing about this add-on looks different.

The virtual tour pane now travels with this add-on. It used to live in the design, and it is now part of the add-on that provides the tours, so the same pane appears on the same properties. A design may still offer its own version of it, and where you have customised one, your version continues to be used.

The effect is on sites that do NOT have this add-on: they no longer carry the pane's markup at all.

The rest of the release is work inside the source that a site cannot observe.

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 3D / Panorama Tour on the current engine — escaping, scripts and styles now go through each platform's own pipeline — and adds no features and changes no behaviour. It is published so the add-on stays in step with the rest of the product.

360° tours on a property page.

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.