Well... I'm messing around with dRealty IDX 7.x-3.x-dev (2012-03-21) ...
I like the new field mappings.
I have been able to import RETS text data successfully.
However, I was not successful at getting images to show.
Now...
I'm not sure what the issue is here. But using the 'rets property' listing connection, creating an 'image' field, and enabling 'Process Images?' doesn't do anything. I.e. I'm able to select everything just fine, however viewing the property doesn't show the image. Also there is in 'manage display' image field there is just the option to select the image styles i have previously created (there isn't anything specific referencing drealty). Same thing with the actual image field, there is no mapping of any sort--but i'm assuming this is due to the fact that this is selected at the 'connection' level under the checkbox 'Process Images?'
Also...
Noticed that my RETS has a seperate table (or whatever it's called) for images, called 'media' (see attached). This table has all the pic info, however, it's separate from the 'Property: listing_mrmls_resi - listing_mrmls_resi - Residential' table.
Both RETS tables 'media' and 'Property: listing_mrmls_resi - listing_mrmls_resi' have a 'object types':
LargePhoto pictures image/jpeg
Photo pictures image/jpeg
Thumbnail pictures image/jpeg
However, all the image data appears to be in the 'media' table...
I'm trying to wrap my head around this. If the property listing table doesn't have the actual image data, and the real image data is stored on a separate table, then how will this actually work?
Do I have to create 2 separate connections (e.g. 'properties' and 'images') and then map the 'images' content into a 'properties' image field?
anyhow... i've attached all relevant images to hopefully help clear things a bit.
| Comment | File | Size | Author |
|---|---|---|---|
| #4 | drealty-image-field-setup.jpg | 374.83 KB | duntuk |
| #3 | drealty-3.0-connection-setting.jpg | 339.72 KB | duntuk |
| #1 | drealty-3.0-resource-management-property.jpg | 111.16 KB | duntuk |
| drealty-3.0-property-type-image.jpg | 47.83 KB | duntuk | |
| drealty-3.0-rets-property-object-types-.jpg | 141.3 KB | duntuk |
Comments
Comment #1
duntuk commentedattached is my 'Process Images?' setting.
Comment #2
camidoo commentedyou don't have to do two separate connections. Make sure that your key field is set to matrix_unique_id, that "may" be the reason you can't download images.
Comment #3
duntuk commentedThanks again for your input.
I do already have 'matrix_unique_id' set in the key field of the property listing connection. Please see attached.
Comment #4
duntuk commentedSide question: How is the dRealty image field suppose to be setup? My main question is what suppose to go under "Number of values"? 'unlimited'?
I don't thing that has been touched upon.
What happens if a listing has multiple images? How would those get mapped? I'm assuming that the 'number of values' should be set to 'unlimited' if any amount of images can be associated with a property listing.
Comment #5
camidoo commentedyea, it should be set to unlimited
Comment #6
camidoo commentedis this still an issue with the latest, if so please reopen this issue.
Comment #7
zxaos commentedI'm still having this issue.
If I run grab the debug log from phrets, I see the image/jpeg mime type being returned but no file is created on my system. I've tried with the media module both not installed and installed.
Comment #8
zxaos commentedSome further debugging revealed that for the RETS server I'm targeting the Images are keyed to ID and not Counter (although Counter does exist). This was causing valid images to be rejected because the mlskey wasn't matching the image rets_id.
Although this is working correctly, some debug/status messages on Update Single Listing would have significantly helped fix the misconfiguration. Something like "Associated image was skipped because it didn't match MLS ID", maybe.
Comment #8.0
zxaos commentedadded additional notes about images not displaying