Hi there!

I have installed PIRETS and configured everything so that the configuration page has no errors (all green! yay!). I am working locally on my iMac using MAMP Pro.

here is the server information:

Server response headers:

HTTP/1.1 200 OK
Cache-Control: private
Date: Fri, 01 Oct 2010 16:36:12 GMT
Content-Type: text/xml; charset=utf-8
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
X-AspNet-Version: 2.0.50727
RETS-Version: RETS/1.5
Set-Cookie: ASP.NET_SessionId=3sgrikvp2wsd1245qvs1as55; path=/; HttpOnly
Content-Encoding: deflate
Vary: Accept-Encoding
Transfer-Encoding: chunked

Search URI: http://matrixrets.victoriamls.ca/rets/search.ashx
GetObject URI: http://matrixrets.victoriamls.ca/rets/GetObject.ashx
GetMetadata URI: http://matrixrets.victoriamls.ca/rets/getmetadata.ashx

--------------------------------------------------------------------

3 Property classes were imported

  • Residential
  • Commercial
  • Land

--------------------------------------------------------------------

There were TONS of fields that showed up in the useful field selection. Like it said in the documentation, many did not make much sense and I had a difficult time figuring out what the MLS ID was (I actually tried using every single field that looked remotely like it might work).

I think I got it: boolean field on_idx (on_idx)

The other fields I am using is photo count, sale status, and current price. I have configured imagecache to handle the photos.

In search limits I selected current, pending, and sold with a 2000 record chunk size.

-------------------------------------------------------------------

In the listings tab, all 3 property types show up as expected. When I update one individually, it attempts to retrieve listings but returns zero. It does not give any errors.

If I click on "update all now" under all listings, It attempts to retrieve listings and then SOMETIMES an error shows that says:

mysqli_num_rows() expects parameter 1 to be mysqli_result, boolean given in /Users/production/Sites/mysite/includes/database.mysqli.inc on line 178.

No other errors are appearing anywhere, including the logs.

-------------------------------------------------------------------

Have any ideas off the top of your head? I did install PIRETS devel, but I'm not sure how to use it. I use devel all the time for theming, so I am familiar with it... but only through the drupal interface.

Could there be an issue with RETS while working locally? or using mysqli?
Is it possible that an error like that would show if I had the wrong field correlation for MLS ID (or price/sale status for that matter)?

Thanks in advance!

Amy

Comments

thomas.lucas’s picture

thomas.lucas commented

I have the same problem, Garrett and jday came up with some ideas:

http://drupal.org/node/922786

I just updated to a more powerful server but did no difference. Try changing the chunk size to 250 or 1000, it works for me (even if that means you are featuring just a portion of the mls). Also I assume you are checking the ''Recent log entries'' at all times (not only the onscreen errors) sometime you get no onscreen errors but pages and pages of the mysqli thing there -and every now and then a duplicate 039 something, but rarely appears -

I have interealty, I see you have something different... in my case ''sysid' (happens also to be the pirets_1) marked as MLS works fine. I am also unfamiliar with devel / Pirets devel, but I would be happy to run any tests if there is any step by step guide.

amysteen’s picture

amysteen commented

Hey thomas!

Thanks for the quick response :)

I tried changing the chunk size to 250 but did not seem to make a difference.
The only error in my logs is the mysqli one (mysqli_num_rows() expects parameter 1 to be mysqli_result, boolean given in mysite/includes/database.mysqli.inc on line 178.)

I will try playing around with the field correlation again. I don't have a field called "sysid" but there is many that include some sort of ID. I have already scoured the issue queue pretty heavily haha.

mcctnt2000’s picture

mcctnt2000 commented
Priority: Normal » Major

I am having the same issues with interrealty. Any solutions yet?

Garrett Albright’s picture

Garrett Albright commented

There were TONS of fields that showed up in the useful field selection. Like it said in the documentation, many did not make much sense and I had a difficult time figuring out what the MLS ID was (I actually tried using every single field that looked remotely like it might work).

I think I got it: boolean field on_idx (on_idx)

No, that wouldn't be it. The MLS ID field would not be a boolean; that sort of field can only store two values! The field type of the MLS ID field will probably be Character, but might also be Int, Long or Decimal.

Also, if you haven't already, check the Drupal log and see if PIRETS is logging anything interesting there.