I have a project that I am working on that requires RETS integration. I myself have never used/heard of this. I installed your module (latest from bitbucket) and attempted to configure.

The RETS server that I am attempting to connect to is version 1.7.2 and is through Rapatoni (Southwest Michigan).

First issue I had was the version had to be updated in the header from 1.5 to 1.7.2 before the server would even authenticate. That problem was solved. I proceeded to configure everything else and achieved "all green checkmarks!!!!". However now when I go to fetch all listings I get nothing. I know that the connection is good because I have the field list and I can see all the possible location information for my area.

I am on drupal 6.2 with all required cck fields, imagecache and location fields enabled.

Any thoughts?

Much appriecitated

Comments

jerry’s picture

jerry commented

Subscribing; I have a Rapattoni project coming up as well.

rivalarrival’s picture

rivalarrival commented

I appear to have the same basic problems as the OP. The three photo support items are yellow, but everything else is checked green. It's a Rapattoni 1.7.2 server (they shut down their 1.5 servers on 3 Jan 2011) serving Northeast Ohio (NEOHREX)

Again, first problem was the version header needed to be updated. (Maybe an option to set this in the configuration?)

In Listings, each type displayed:
"0 in database; last updated (never)"
Clicking "update now" reports success:
"Class update for MULT completed. 0 created, 0 updated, 0 deleted, 0 unchanged."
And the type updates accordingly:
0 in database; last updated Wed, 2011-02-09 22:47

Repeated this for each listing type - no listings fetched.

bentekwork’s picture

bentekwork commented

So I got a few messages from people from this issue.

I have got this module working "somewhat" by changing a couple lines of code.

***Disclaimer****: It is quite possible that my issues pertain to a specific server setup with Rapattoni.

To fix the header issue I simply modified Line 14 in the pirets.connect.inc file to read:

define('PIRETS_RETS_VERSION', 'RETS/1.7.2');

I then realized that the query that was built by this module was returning a "invalid query" message. I discovered that it had to do with the listing Status field that was in the query. I changed line 103 in pirets.connect.inc to read:

$result = _pirets_query("?SearchType=Property&Format=COMPACT&QueryType=DMQL2&Limit=500&Offset={$offset}&Class={$class}&Query=(MLNumber=0+)&Select=" . implode(',', $fields), 'search');

I highly reccomend installing the devel module and pirets devel module. It contains a query builder which gives you clarity into what query you actually want to see returned. In the code above I am simply querying ALL listings that have a MLS number that is higher than 0. There is better documentation on RETS.org on how to build a query.

Hope this helps some other poor soul who has been tasked with a Real Estate website...

rivalarrival’s picture

rivalarrival commented

Original:

  $result = _pirets_query("?SearchType=Property&Format=COMPACT&QueryType=DMQL2&Limit={$limit}&Offset={$offset}&Class={$class}&Query=(" . implode('),(', $query) . ')&Select=' . implode(',', $fields), 'search');

Questionable modification:

  $result = _pirets_query("?SearchType=Property&Format=COMPACT&QueryType=DMQL2&Limit=500&Offset={$offset}&Class={$class}&Query=(MLNumber=0+)&Select=" . implode(',', $fields), 'search');

This will make it so that every search conducted will attempt to retrieve every record from the MLS (all properties of Class $class, with an MLNumber) This is almost surely NOT what we want to do...

bentekwork’s picture

bentekwork commented

Ok quick update.

I was probably a little quick to hack the module.

David discovered that you simply need to choose the correct price field. Rapattoni has a dozen or so price fields the only one that works on a search query is SearchPrice. So be sure to correlate the price field to the search price.

I discovered that in order to get the images to work you must correlate the ListingRid to the MLS number. This is due to some potential for dup MLS numbers on the RETS server. The image query will only work if you use this method.

You still must include this line on connect.inc Line 14 in the pirets.connect.inc file to read:

define('PIRETS_RETS_VERSION', 'RETS/1.7.2');

Thank you David for helping troubleshoot this!

This is a great module, thanks!

Garrett Albright’s picture

Garrett Albright commented

This will make it so that every search conducted will attempt to retrieve every record from the MLS (all properties of Class $class, with an MLNumber) This is almost surely NOT what we want to do...

Actually, this is exactly what PIRETS does. Since RETS and implementations thereof are so lousy that there's no sure way to say, for example, "send me all listings which have been updated in the last 24 hours," PRETS just fetches every listing in a class and then checks for itself to see if listings have been created, updated or deleted. Yes, it's awful, but it's the most consistent way I could find to synch listings regardless of the server.

Anyway, bentekwork, glad you found a work-around. This is the first I've heard of a RETS server refusing to send listings based on the RETS version the client requests. That being said, in the OP, when you said you're using Drupal 6.2, did you actually mean Drupal 6.20? I assume so, because I don't think PIRETS will work correctly on versions before 6.13 or so (whenever the semaphore handling got added), but if you really did mean the former, I strongly recommend you upgrade - you're about 18 months behind on performance and security upgrades!