Yes. FWRE Custom Fields is included in the 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.
The Custom Fields addon is a paid addon included in all FW Real Estate subscription packages (Start, Medium, Pro). Install it from your Client Section.
Four types are available: text input for single-line text or numbers, dropdown select for single-choice menus, checkbox list for multi-select options, and boolean toggle for yes/no values. Select and checkbox types support unlimited predefined options with translatable labels.
Create custom groups and assign them to tabs. Fields display according to their tab ordering number: 0-99 shows before property details, 100-199 after details, and 200+ as additional sections. The frontend automatically renders each tab as a separate section.
Yes. When creating or editing a field, toggle the Required setting to yes. Agents will not be able to save a property without filling in mandatory custom fields. Enforcement happens at save time.
Yes. Each custom field has an Access Level setting. Restrict sensitive data to agents or admins, while hiding it from guests or registered users. Fields respect Joomla access levels and inheritance.
Yes, when combined with the Search Layouts addon. Visitors can filter properties by your custom field values in search forms and results. Without Search Layouts, custom fields display on property pages but are not filterable.
Version 5.2.0: 2 new features, 1 fix.
New: Edit forms now open in your site's default language, as your site's own language settings set it. Settings shows that default with a link to where you change it, and the Editing language switch lists the languages your site publishes content in. A site with one language, such as WordPress without a multilingual plugin, shows no switch.
New: A listing with no text in your site's default language now says so, for example "Needs English text", and nothing is moved for you. The list and the edit form show the text the listing has, and saving without typing never blanks its title. If many listings were saved under the wrong language, a notice offers to re-key them as your default language, after making a backup.
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.
Version 5.1.5: 1 fix.
Bugfix: Editing in a second language no longer loses your changes. When you edited a listing, a dictionary value or an agent in another language, the price, categories, contact details and other values that are the same in every language were thrown away while the screen still said "saved". They're now saved from any language, every multilingual screen has a labelled Editing language switch with a line that says which language you're editing and what a save keeps, and switching with unsaved changes asks first. On WordPress the chosen language now lasts until you log out, as it does elsewhere.
No change to how this add-on behaves. Released together with FW Real Estate 7.1.4 so that the update server holds the current build.
A custom field belongs to whatever created it. Fields added by another part of the product are no longer listed among the ones you defined here, so the list on this screen is the set you manage.
Existing fields are untouched, and nothing needs adjusting after installing this.
No change to how this add-on behaves. Nothing a site can observe is different: the English catalogue was rewritten into the form the WordPress directory extracts translations from, and comments inside the code were shortened. The fifteen languages this add-on ships are unchanged.
Published so that what the update server holds matches the product exactly.
No change you will notice. This release rebuilds Custom Fields on the current engine. Its controls no longer carry their behaviour inside the page — the buttons and selects work exactly as before, driven from the shared script file instead — and the markup it produces is written the way each platform expects it. No features are added and no behaviour changes; every page it draws was compared before and after, and they are identical.
No change you will notice. This release rebuilds Custom Fields 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.
Your own fields on a property — grouped into tabs and cards, with the values you define.
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.