Posted by camidoo on June 10, 2010 at 8:16pm
Released a new IDX / RETS module today called dRealty IDX. Take a look if you like and leave all the feedback you can, both good and bad!
some of the features include:
- Provides an interface to define multiple RETS service connections.
- Provides an interface to Setup a MLS feed, allowing a user to import various entities into the Drupal system.
- Users can select to import Property Listings, Real Estate Agents, Real Estate Offices, and Open Houses
- There are four node_types defined by the module, drealty_properties, drealty_agents, drealty_offices, and drealty_open_houses
- The module leverages the power of CCK in that when a feed is setup by a user, cck fields are created and added to the corresponding node types.
- Users have the ability to choose cck_field_names and labels during the feed setup process, easing theming and usability
- Once feeds have been setup users can then define correlations to further integrate with location and filefield
- Users have the ability to update and flush their MLS feeds
- Feeds are then processed according to the feed profile during cron
- Connections and all feed profiles can be exported and then imported to facilitate ease of development and setting up similar feeds for other clients
- dRealty IDX makes use of the Batch API
- drush integration.
- apache_solr integration
- and much more
Thanks goes out to Garrett Albright and his PIRETS module for the inspiration and jump start.
Comments
iMac
Fork moar. =P
The Boise Drupal Guy!
I got a Fatal Error of Death
I got a Fatal Error of Death upon installation saying that the function to add a fieldgroup (sorry, can't recall the exact name) could not be found when I tried to install this and the Fieldgroup module at the same time. I ran into similar issues with PIRETS recently. It seems that CCK stuff creation doesn't happen properly at least some of the time when a CCK-related module that provides stuff to create and the module trying to create that stuff are enabled at the same time.
The Boise Drupal Guy!
Please post issues in the
Please post issues in the issue queue, tyvm.
Your point? I thought we had
Your point? I thought we had this discussion once before. Had you been a bit more open to changes, this code would have all resided inside the PIRETS module to begin with, not exactly sure what the purpose of this post was. I make no illusion that i took the PIRETS module and 'improved' upon it, it was your choice not include those changes and encourage me to release my own module. And yes, this is a fork of PIRETS, get over it.
Woah, there. Yes, we've
Woah, there. Yes, we've discussed it, and I'm fine with this being a fork of PIRETS. I'm just pointing out some places where you're still trying to do PIRETS stuff that isn't going to work, that's all.
Please note the smiley at the end of my post.
The Boise Drupal Guy!