Archive for REAXML

Once you have a portal provider in place and you’ve uploaded your listings and photographs into it you’re ready to configure the FeedSync for your website.

Step 1: Decide where the final hosting server will be

Its much easier to to this once on the final server then to change things later. You have enough to do when launching a new website that you don’t want to add another step in the way and have to wait for your provider to adjust their settings on your tight schedule.

For example: You are developing a new WordPress web site on your local development server which will eventually replace an existing one but the client plans on keeping their current hosting.

We’ve just updated FeedSync to version 1.1.3 which now supports REAXML files that are delivered in zip files which also contain property images. This is a major version release that adds support for zip format REAXML files as supplied by some providers like Rockend Rest and Console.

What it now does to support the zip REAXML format is:

Unzips the zip file(s) and moves the images into the processed/images folder.

While processing the REAXML xml files it rewrites the image location with a valid URL so they hey can be imported.

Moves the processed zip filed into processed/zips.

Lists zip files waiting to be processed.

Transfers content from current and appends new status when input file only contains status update.

In this tutorial we are going to walk through the steps of importing REAXML files into your WordPress real estate website.

Basically we are going to create two import jobs for each REAXML property element, one for current and one for sold/leased. FeedSync merges the REAXML files and creates three output files: current, sold/leased, withdrawn/offmarket. We only need to import the current and sold/leased as because this is more efficient by reducing import file sizes, leaves the withdrawn/offmarket out of the database.

Here is a script that you can upload to your server and configure in a few minutes with ease and you can do it all without FTP software and it is only $87 for a single site license.

The core of FeedSync was developed over 3 years ago to solve the problem of dealing with multiple REAXML files that need to be merged into a single file that can then be imported by your software. So FeedSync has been working on dozens of different real estate websites

I didn’t realise that there are so many developers looking to solve this same very problem.

My requirements when developing this REAXML parser script was to make sure it was fast, efficient and not repeat imports if NO changes are detected and be able to use WP-Property to import the files and manage the property and rental listings.

So after countless hours searching for a REA XML parser to no avail I set out to find a developer to build my REA XML parser.

The script had to do the following:

Combine the individual REAXML files into a single, or multiple import files.

Process the results and store them in 3 new separate REAXML files: Current, SOLD/LEASED, and withdrawn to increase speed.

When the property status changes to sold/leased/withdrawn delete the property entry from the current REAXML output file.

Just added: Geocode the property address during import and add another field so my new property plugin did not have to also geocode the entry on import.