Free
Free
Solo Agent+
IDX Realtor+
Solo Agent+
IDX Realtor+
Solo Agent+
IDX Realtor+
IDX Realtor+
IDX Realtor+
Solo Agent+
Free
IDX Realtor+
IDX Realtor+
IDX Realtor+
IDX Realtor+
IDX Realtor+
Solo Agent+
Solo Agent+
IDX Realtor+
Free
Free
Solo Agent+
IDX Realtor+
Solo Agent+
IDX Realtor+
Solo Agent+
Free
Free
Free
Free
Free
Free
Free
Solo Agent+
Solo Agent+
Solo Agent+
Solo Agent+
Solo Agent+
Solo Agent+
Solo Agent+
Solo Agent+
Solo Agent+
Solo Agent+
Solo Agent+
Solo Agent+
Solo Agent+
IDX Realtor+
IDX Realtor+
IDX Realtor+
Solo Agent+
IDX Realtor+
IDX Realtor+
Solo Agent+
IDX Realtor+
Solo Agent+
IDX Realtor+
IDX Realtor+
IDX Realtor+
IDX Realtor+
IDX Realtor+
IDX Realtor+
IDX Realtor+
Solo Agent+
Solo Agent+
Yes. The core is free and always has been: download it from the FW Real Estate product page on fastw3b.com, pick the package for your platform, agree to the terms and install that one file. There is nothing to buy first and no account needed to get it.
What a paid subscription adds is add-ons. The core covers properties, fields, dictionaries and the front end on its own, and a great many sites never need more than that.
Automatically. Install the core package for your platform, then connect the site to your fastw3b.com account, and every add-on you are entitled to is downloaded and switched on for you. There is no per-add-on Install button, and nothing to download by hand.
To connect, click Connect in the FW Real Estate admin header. The lock icon and the red This website is not verified text beside it do the same thing, and the Add-ons screen offers the same action as Connect to install. It is one click: your fastw3b.com client section opens, the store registers this website and sends the key straight back, and the admin returns already verified. There is nothing to copy and no key to paste.
From that moment the free add-ons and whatever your subscription covers install and enable themselves. The only manual actions afterwards are enabling, disabling and updating; add-ons cannot be deleted, so one you do not want is simply left disabled.
Connecting pairs this site with your fastw3b.com account. It is what makes the following possible:
One button does it: Connect, in the FW Real Estate admin header. It opens your client section, registers the site and brings the key back by itself.
Free add-ons come with connecting alone, no subscription required. An unconnected site keeps working, but it receives no add-ons and is offered no updates.
Add-ons are extensions that work only with FW Real Estate and add to what it can do. They come in three kinds: plugins (features such as maps, agents, favourites or rentals), designs (how the front end looks) and modules (blocks you can place on a page).
They are not Joomla extensions or WordPress plugins and will not appear in your platform's own extension or plugin manager. They live inside FW Real Estate and are managed from its Add-ons screen.
FW Real Estate is self-sufficient on its own: the core holds everything a property site cannot work without. Every other feature is an add-on, so that each site carries only what it actually uses.
That split is also why disabling an add-on is clean. Turn one off and its fields, its output and its columns disappear from the site; turn it back on and they return with the data intact.
Connect your website to your fastw3b.com account, using the Connect button in the FW Real Estate admin header. The add-ons your subscription covers are then downloaded and enabled on their own, and the free ones come with connecting by itself.
If the add-on you want is not among them, it needs a subscription that covers it. Take out or extend one on fastw3b.com and it will arrive automatically on a later visit to the admin, with nothing to download or install by hand.
Everything the site has received is listed under Admin, FW Real Estate, Add-ons, where you can enable, disable and update each one. Add-ons cannot be deleted: an add-on you do not want is simply left disabled.
If you can dream it, Fastw3b will design it. It is almost a year since I started working with Fastw3b. In fact, having started on the Joomla journey (three months prior) and with no development experience, Fastw3b was the perfect first date.
After the initial – dancing around – trying to understand each other, we quickly established a relationship based on frankness and directness and this was probably the single most important trait that I respect them for. It would have been easier to repeat the “customer is king” mantra and get paid for the job. Not with Fastw3b. It seemed as if they genuinely were as interested and excited about the project as I was. It was as if I was working with my own inhouse team, rather than distant consultants.
If you are new to Joomla or indeed to development and are looking for a professional yet empathetic partner, I highly recommend Fastw3b. They deliver on time, are willing to own-up to errors and fix them, and best of all are as invested in your project as you.
Solid extension with great support
Functionality. This extension had every function available that my client requested and a lot more too.
Ease of use. Even a beginner could configure it right out of the box.
Support. If I could score them 110 here I would. The support has been fantastic, even though I am on the other side of the world.
Documentation. Documentation is a little thin, but the support makes up for it.
Value for money. Yup. Definitely worth it. Going to have them install IDX integration next.
Perfect !
Perfect and great support. Help, trust and safe. Thank you all
FW Real Estate - EXCELLENT !!!
I recently bought the extension FW Real Estate, to build a project were the goals of the estensão it claims to do. And to my surprise, the project is being built surpassing my expectations.
Support is fast, simple and very objective: Fantastic!
I recommend everyone this robust extension!
CONGRATULATIONS TO ITS DEVELOPERS AND SUPPORT YOUR TEAM!
Excellent component
We used some of Real Estate components for Joomla. We pay money and in most of cased we do not received a good component and good support.
But we found this component and for low money (it`s really very low money) we received a excellent Real Estate component with very very good support.
So - I recommend use this Real Estate component - it`s very cheaper, very good quality, very good support, and very easy to use it for building a real estate site.
The criteria for any successful project is for it to be on time, within budget and meets business and customer requirements. In order to achieve this you need a highly skilled team who are knowledgeable efficient in what they do and prepared to go the extra mile to ensure that the required work is completed to the highest quality. It is for this reason that I partner with Fastw3b as I can rely on them to always deliver a successful project.
The strongest skill of Fastw3b is their ability to develop and deliver innovative technical solutions whilst always ensuring a high level of customer service.
I believe it is the willingness of Fastw3b to collaborate with a client during the project initiation phase by providing suggestions and advice on how to best solve a problem to ensure that a quality product and service is delivered.
Great component and support
I have been using this component for about 2 years now. Everything works perfectly. Recently I migrated to a new Joomla! website and installed the new component, something wasn't right and the support desk of FW helped me fast and good.
Couple of years ago when I wanted to redesign my art website I was looking for an easy to navigate and attractive picture gallery component with Lightbox effect and have found Fastw3b Gallery. With some customization of the FW Gallery extension I was able to showcase my extensive art and photography collection with specific information I needed in a clean, contemporary style. This is a well organized, expandable structure with many features.
I could count on expert advise regarding website development, customization or upgrade questions, reliable communication and delivering work by schedule.
Why do you choose Fastw3b as provider for your projects?
At the time I selected Fastw3b, you offered what appeared to be the best Real Estate component for Joomla at a reasonable price.
What do you think is our strongest skill as a company?
I am very satisfied with your customization services. I have hired your team numerous times for FW Real Estate customization for one of my clients.
I appreciate the personal service and quick attention to issues that I’ve experienced with your customization services.
A maintenance release for the component. Nothing it changes is visible on a page, and there is nothing to adjust after installing it.
Template names are validated before they are used. A template is chosen by name, and some of those names are assembled from settings a page carries. The name is now checked to be a name, so one that has been tampered with resolves to nothing instead of to a file. Every template a design or an add-on actually ships is unaffected: the check describes the shape they already have.
Submitted values are cleaned as they arrive. Text that a form sends is stripped of markup at the point it is read, in one place, rather than at each of the places that use it. Fields written in the rich-text editor are the exception, and they keep what the editor produced: a property description keeps its formatting, its links and its tables. Nothing was added to what that filter allows, because nothing needed to be: the video and the virtual tour a listing shows are built when the page is drawn, from the address stored with the property, and were never part of the description's own text.
Nothing else changes. No setting moves, no data is rewritten, and a site that was working before is working the same way after.
Nothing in this release changes what the component does. Files moved; behaviour did not. Every page renders what it rendered before and every setting means what it meant.
What moved: the markup for a feature now lives with the feature rather than in the design, so an add-on brings its own appearance with it and a design no longer has to know about every add-on that might be installed.
A design still has the last word, and a site that has customised one keeps every customisation. If the design offers its own version of a template, that version is used exactly as before; the add-on's copy is consulted only after the design and its parents have been asked. Updating the component replaces its files and removes none, so templates already on your site stay where they are and keep being used.
⚠️ Update the component before the add-ons. An add-on published alongside this release carries its own templates and needs the core that knows to look for them. The catalogue will not offer such an add-on to an older core, so the order takes care of itself if you update the component first.
Share via e-mail on the map listing was visible and did nothing, and now works.
There is nothing to do after installing this beyond the update itself.
This release carries engine 7.0.6, and nothing in it changes what you see. The English text the product ships was prepared so that platforms which translate software themselves can read it. On this platform that changes nothing at all: the fourteen translations install and work exactly as before, and the screen for reading, editing and ordering them is untouched.
There is nothing to do after installing this beyond the update itself.
This release carries engine 7.0.5, whose one visible change is that downloading an add-on or an update now uses your site's own connection settings, so a server that does not allow software to open its own connections can install and update normally.
Nothing else here changes what you see. The way pages are assembled internally was reworked; every screen, in the back office and on the site, was captured before and after and compared element by element, and none of them changed. There is nothing to do after installing this beyond the update itself.
Upgrading from version 6 no longer costs you your feed importer setup. Its address, access token, filter and fetch size are carried across, along with the licence key for your site — which means the site stays connected to the update server instead of appearing never to have been activated. The categories each feed imports into are re-pointed at the upgraded catalogue when the add-on is installed, so imported properties land where you configured them rather than in no category at all.
Modules the upgrade switched off come back on their own. Upgrading has to unpublish the version 6 modules, because their own code writes errors into whatever page they sit on. Until now they stayed off and putting them back was manual. The upgrade now remembers exactly which ones it switched off, and publishes those again once the replacement module is installed — only those. Anything you had switched off yourself is left alone, and anything you moved to the trash meanwhile stays in the trash.
The rest of this release is invisible on purpose. The component's markup and the way its screens read a request were reworked to the letter of what each platform expects. No screen changes: the back office and the site were captured before and after and compared element by element.
Buttons on the back-office screens work again. On this platform every script the product added was being placed at the top of the page, before the controls it was meant to attach to — so the control was drawn, looked normal, responded to nothing. Check updates on the Add-ons screen was the one people noticed; the search box and the status filter beside it were dead for the same reason, as were the CSV import form on Data Management and the message strip on Translation. Nothing was wrong with the site or the data: the page simply ran its instructions before the thing they referred to existed. All of them respond now.
A profile no longer changes an existing account's password. Creating an agent or contributor profile on an e-mail address that already had an account reset that account's password — an address match was being treated as proof of ownership. An existing account is now left untouched. If you created a profile on an address belonging to someone else, that person's password was changed at the time and they will need to set a new one.
A repair release for sites upgrading from 6.x.
FW Real Estate 7.0 is a complete rebuild, not an incremental update.
The component has been rewritten on a new engine: the database tables have been rebuilt, template and layout names have changed, CSS class names have changed, and several features that used to be built in are now separate add-ons delivered with your subscription.
Your content is migrated for you. Properties, agents, categories, dictionaries and enquiries all carry over. Nothing you have entered is discarded.
What does not carry over is anything written against the old component — template and layout overrides, custom CSS, bespoke plugins or modules, direct database queries, and third-party extensions that read FW Real Estate data. These will need to be redone or reviewed against the new structure.
If your site has any customisation at all, do not update it in place. Copy the site to a staging environment, run this update there, and check the front end, the property edit form and your integrations before you update the live site.
A stock installation with no customisation can be updated directly.
This update cannot be undone from inside the component. Returning to the previous version means restoring your backup.
FW Real Estate 7.0 is a rebuild of the product on a new cross-platform engine — the same product, now built from one codebase for both Joomla and WordPress. See the component release notes for what changed.
Not an install-over: install 7.0, then import your 6.x backup from FW Real Estate → Data. The importer repairs the old archive's collation, settings keys and users as it goes, and stages everything in isolation so your live tables are untouched.
A maintenance release for the plugin. Nothing it changes is visible on a page, and there is nothing to adjust after installing it.
Template names are validated before they are used. A template is chosen by name, and some of those names are assembled from settings a page carries. The name is now checked to be a name, so one that has been tampered with resolves to nothing instead of to a file. Every template a design or an add-on actually ships is unaffected: the check describes the shape they already have.
Submitted values are cleaned as they arrive. Text that a form sends is stripped of markup at the point it is read, in one place, rather than at each of the places that use it. Fields written in the rich-text editor are the exception, and they keep what the editor produced: a property description keeps its formatting, its links and its tables. Nothing was added to what that filter allows, because nothing needed to be: the video and the virtual tour a listing shows are built when the page is drawn, from the address stored with the property, and were never part of the description's own text.
Nothing else changes. No setting moves, no data is rewritten, and a site that was working before is working the same way after.
Nothing in this release changes what the plugin does. Files moved; behaviour did not. Every page renders what it rendered before and every setting means what it meant.
What moved: the markup for a feature now lives with the feature rather than in the design, so an add-on brings its own appearance with it. A design still has the last word: where it offers its own version of a template, that version is used, exactly as before.
The plugin is materially smaller. Code that could never run on this platform has been removed, and the shared machinery a feed importer needs now travels with the importer instead of shipping to every site whether or not one is installed. The archive is about six thousand eight hundred lines lighter, with no feature removed.
⚠️ Update the plugin before any add-on pack. An add-on published alongside this release carries its own templates and needs the core that knows to look for them.
Share via e-mail on the map listing was visible and did nothing, and now works.
There is nothing to do after installing this beyond the update itself.
Translations for this plugin now come from WordPress rather than from the plugin itself. The plugin no longer carries translation files of its own. Its English text is prepared so that translate.wordpress.org can read it, and a finished translation reaches your site as a WordPress language pack — installed and kept up to date the same way as for any other plugin.
What that means for a site that is not in English: until a translation for your language has been made there, the plugin's screens are in English. Nothing you have entered is affected, and there is nothing to do — a language pack installs itself once one exists.
The screen for ordering a translation is gone on this platform, for the same reason: translations here are WordPress's to host, not ours.
Everything else in this release is invisible — further work to match what WordPress expects of a plugin published in its directory.
Print, quick view and the map window now load their styling through WordPress itself. Each of these opens as a page of its own rather than inside your theme, and its stylesheets were being requested in a way that let a browser go on using a copy it had already cached. They are now handed to WordPress like every other stylesheet the plugin uses, so a change reaches them straight away instead of after the visitor clears their cache.
This release carries engine 7.0.5, whose visible change is that downloading an add-on or an update now uses your site's own connection settings, so a server that does not allow software to open its own connections can install and update normally.
Everything else here is invisible on purpose — further work to match what WordPress expects of a plugin published in its directory. No page changes: every screen, in the back office and on the site, was captured before and after and compared element by element.
The account area works again. Every page built on it — the dashboard, favourites, saved searches, the property manager, the agent profile and compare — answered a server error instead of loading. It affected every visitor and every site; there was no configuration that avoided it and nothing to do about it. Those pages load normally after installing this.
The block editor offers its choices again. When placing one of the plugin's blocks, the design list and the per-module layout list were empty, so the only option was the default. Both are populated again, including designs delivered by an add-on pack rather than bundled.
Everything else in this release is invisible on purpose. The plugin's markup and its handling of the request were reworked to match what WordPress expects of a plugin published in its directory. No page changes: every screen, in the back office and on the site, was captured before and after and compared element by element.
This release carries engine 7.0.4. The importer add-ons published alongside it declare that engine as their minimum, so a site on this version can install them; a site on the previous one cannot yet. The engine work in 7.0.4 is about carrying a configuration across an upgrade from version 6, which is a situation that does not arise on WordPress, where the product is new.
A profile no longer changes an existing account's password. Creating an agent or contributor profile on an e-mail address that already had an account reset that account's password — an address match was being treated as proof of ownership. An existing account is now left untouched. If you created a profile on an address belonging to someone else, that person's password was changed at the time and they will need to set a new one.
A maintenance release.
FW Real Estate is now available for WordPress — the same product as the Joomla edition, built from one cross-platform codebase, so both editions stay in step.
wp-content/uploads/fwre/ — property images, language packs, backups. A plugin update replaces the plugin folder and leaves them alone.Install the plugin, then import your existing backup from FW Real Estate → Data. The importer recognises an old-generation archive and repairs its collation, settings keys and users as it goes, staging everything in isolation so nothing live is touched.