The 7.x-3.x branch of dRealty has been running in wild for years now. The 7.x-3.x-beta6 release has been performing in a reasonably stable manor since release. There are now a small handful of bug reports that should be addressed prior to a release candidate / stable release. This milestone will represent a reliable set of capabilities for implementing PHRETS within Drupal.

7.x-3.x Priorities

  1. Resolve open "major" bug reports - almost all of them have been patched. #2135893 remaining
  2. Resolve open "normal" bug reports
  3. Revise module documentation
  4. Release 7.x-3.0
  5. Evaluate open feature requests for 7.x-3.1

Feature Request Priorities

  1. #1426836: Entity Reference Support
  2. #2569901: Image File Directory Path with Tokens
  3. #1296680: Image retrieval Hot Linking vs. Downloading
  4. #2399819: Server not supported with mismatching key field index in media class
  5. #2035573: Integrate with the apachesolr module (this might remain as a future effort - won't be included in the next stable release )
  6. #1555740: Ignore expired listings not sure if this issue needs to be worked on, as we already have a "Reconciler" module (starting from RC1) to handle expired listings

Comments

webavant’s picture

webavant CreditAttribution: webavant commented

Awesome, great work! I will test the patches, and try to reproduce the other issues in hopes to find resolutions. It would be great to have as many people testing this as possible.

kevinquillen’s picture

kevinquillen CreditAttribution: kevinquillen commented

Most of these should be pretty straightforward - once we work at those and confirm they are no longer an issue, we can generate a second list of bugs. There are some issues that are feature requests (no code exists yet) and I'd like to hold that list off for RC2.

kevinquillen’s picture

kevinquillen CreditAttribution: kevinquillen commented

Adding #1927064: Image filenames need to be unique

kevinquillen’s picture

kevinquillen CreditAttribution: kevinquillen commented
Issue summary: View changes

Updating

shauntyndall’s picture

shauntyndall CreditAttribution: shauntyndall at Inclind Inc commented
Assigned: kevinquillen » shauntyndall
Category: Task » Plan
Issue summary: View changes
Status: Active » Needs work

I'm going to take ownership of this effort as discussed in our monthly call today. 7.x-3.x-beta6 seems to be reasonably stable for the portfolio of site Inclind maintains. However, I'm currently working to audit the issue queue to ensure we've captured relevant patches for a targeted stable 7.x release.

shauntyndall’s picture

shauntyndall CreditAttribution: shauntyndall at Inclind Inc commented
Title: Drealty RC 1 Release » Drealty 7.x-3.x roadmap
Issue summary: View changes

After auditing all 150 issues in the queue for dRealty I have a reasonable understanding of the module's status and direction. There seem to be a few major bug reports remaining. I think we can rally this 7.x-3.x branch to the finish line and take that knowledge into account as part of the #2540214: Plan for dRealty for Drupal 8 (Drupal RETS Real Estate Framework).

duntuk’s picture

duntuk CreditAttribution: duntuk commented

Cool. Nice to see development has resumed.

shauntyndall’s picture

shauntyndall CreditAttribution: shauntyndall at Inclind Inc commented
Issue summary: View changes
shauntyndall’s picture

shauntyndall CreditAttribution: shauntyndall at Inclind Inc commented
Issue summary: View changes
shauntyndall’s picture

shauntyndall CreditAttribution: shauntyndall at Inclind Inc commented

We possibly need to refactor the manor in which media objects are architected. Currently there seems to be a very rigid approach that restricts the module administrator to only synchronizing a single image field (and only to the getObject method).

It would seem the RETS specification allows for many types of media objects (images, video, pdf files etc.). Could we possibly deal with this better at the field level instead of the resource class level?

What would the impact be on current dRealty users?

shauntyndall’s picture

shauntyndall CreditAttribution: shauntyndall at Inclind Inc commented

Drealty 7.x-3.0-rc1 has been released today after a couple code sprints. There are more than a dozen issues addressed by the release along with a number of other improvements.

The largest change relates to media handling. Prior versions of Drealty were limited to the selection of a single image media object (and only to using GetObject). Media objects are now mappable directly to fields and their processing is centralized. Depending on the RETS implementation, you can now pull (or hotlink) multiple images, videos, file (e.q PDFs) and other media objects available.

Most of this effort was sponsored by Inclind's work on http://www.fitegroup.com. Some developer highlights include:

  • 23,000+ Drealty Listings
  • Less than 100 modules
  • 8 Views
  • 330+ Fields

We are going to be working at cleaning up the issue queue and documentation in the short-term. Then on to Drealty 8.x!

duntuk’s picture

duntuk CreditAttribution: duntuk commented

Thank you for your much appreciated work @shauntyndall! I'm sure many drupal RETS users, future and present, will now find this module immensely powerful--prior to your updates, using this module likely restricted many users from providing full RETS listings due to only having an option to download very large gigabytes of image data.

AvO WebWorks’s picture

AvO WebWorks CreditAttribution: AvO WebWorks commented

Thank you @Shauntyndall for all your hard work. It is an excellent module and super powerful.

mengi’s picture

mengi CreditAttribution: mengi commented

Thanks for all the effort! Can't wait to give it a spin.

Might want to consider changing the front page where it says that the module is in beta.

rolandoscott’s picture

rolandoscott CreditAttribution: rolandoscott commented

Parse error: syntax error, unexpected '=', expecting ')' in /var/www/vhosts/*********/httpdocs/sites/all/modules/drealty/modules/drealty_import/drealty_import.module on line 166

is no one else getting this error when they try to activate the import module? this happens for me on the RC (7.x-3.0-rc1) and the dev (7.x-3.x-dev). I can activate the main module just fine, but it gives me this error when I try to activate the Import submodule?

Thanks

veronicaSeveryn’s picture

veronicaSeveryn CreditAttribution: veronicaSeveryn at Inclind Inc commented
Issue summary: View changes