Yes. FWRE Social Share is included in the Solo Agent, IDX Realtor, and IDX Agency tiers of the FW Real Estate subscription. You get the add-on plus updates and support as long as your subscription stays active.
Yes, Social Share is included in all FW Real Estate subscription packages. Install it from your Client Section.
No. The plugin uses standard social platform share endpoints that require no setup, API keys, or app registrations. Enable the buttons and they work immediately.
The property URL is shared. Social platforms automatically pull the property title, first image, price, and description from your page meta tags to create a rich preview.
The shared content comes from your property meta tags (title, description, image). Customize these in the property edit form or via your design template to control what appears in share previews. Combine with SEO Booster for richer meta data.
Version 5.0.6, a hotfix: 1 fix.
Bugfix: A listing a visitor shares by email shows in your Messages inbox as Shared with a friend again. As in your previous version, each share keeps the visitor's name, email address and note with the listing, so you can see which listings get passed around. The friends' addresses are never kept.
Version 5.0.5: 3 fixes.
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: 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: Share by email can no longer be used to send other people's mail from your site. The message always carries the real link to the property and the subject you set in the add-on's settings, the visitor's name and note arrive as plain text, and one share reaches at most 5 addresses.
Version 5.0.4, a hotfix: 1 fix.
Bugfix: Property links in emails open again. The link to the property in an inquiry email, the auto-reply, the brochure follow-ups and a shared listing now carries your website's address, so it opens from any mail program.
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.
A stray line of text has been removed from the add-on's settings screen. A sentence from the template's own notes was being printed just below the e-mail message editor instead of staying out of sight. Nothing else has changed, and there is nothing to do after installing this beyond the update itself.
No change you will notice. This release rebuilds Social Share 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.
Sharing a property — to a social network, or to someone's inbox.
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:
See the component release notes for the 7.0 story and for how to bring your data across.