Plan for dRealty for Drupal 8 (Drupal RETS Real Estate Framework)

Created on 27 July 2015, almost 9 years ago
Updated 15 May 2023, about 1 year ago

Development on a release for Drupal 8.x has begun. There is not any timeline for getting it to a releasable state.

=-=-=-=-=-=-=-=-=-=-=-=-=-=

Want to help? Join a Google Hangout for dRealty on Friday, April 22, 2016, at 1 pm ET at https://plus.google.com/hangouts/_/ftechs.com/drealty-coord ()

If you use Google Calendar then click here to add the meeting details to your Google calendar (date, time, agenda, hangout url, etc)

UPDATE AS OF MARCH 22 2016 (by @JonFreed):

On March 22, around five to ten people joined a Google Hangout to discuss a D8 version of this "dRealty" module () I didn't note any dissension on the following points, though that doesn't mean that everybody on the same page. :)

Participants (& listeners :): @shauntyndall, @JonFreed, @bryan-cordrey, Phil Everton. (And I think there were at least one or two listeners and maybe up to four or five. I think they included @nickBumgarner and @veronicaSeveryn.)

Discussion Points:

  1. @shauntyndall of Inclind conveyed a very brief history and status of this module that is currently 7.x-3.x.
  2. The existing 7.x-3.0-beta6 version is pretty stable. Nobody identified anything that was strongly keeping the release from being called a production release instead of a "beta6" release.
  3. There is some notable level of interest among real estate people in a D8 version. However, nobody had the name of a company or individual that would provide financial support.
  4. A D8 version should use the latest version of phrets.
  5. Two development approaches for a D8 version were considered: (1) modify the existing code piecemeal, or (2) start with a bare skeleton of code for a D8 version with loosely-coupled components that could be divided among interested developers. (Therefore the developers wouldn't need D7 version knowledge though they could copy-paste D7 version code if appropriate.)
  6. Verbal consensus was for the second approach: Start with a bare skeleton of loosely coupled components then divide and conquer with copy-paste reuse as appropriate.
  7. To keep some momentum, we should have one-hour Hangouts approximately monthly. In lieu of any other volunteers, I (@JonFreed) volunteered to advertise them (e.g. through the Drupal Real Estate Group), set up the Google Hangouts, and facilitate the meetings. (But I am loathe to say or assert that I am any kind of leader for this module because he/I am very new to Drupal module development and even newer to participating in this module's development!)
  8. However, participants seemed to all recognize that this project has a lot of history with many different contributors and it seems that nobody wants to step forward and inadvertently step on anybody's toes . So, achieving a sense of balance between module participants' different priorities and their senses of their historical and current roles will be a challenge in this open-source initiative, just as it is for others.
  9. Support is a big concern. To address that, the monthly hangouts for now will have two main agenda items: (1) what are the hot issues for active deployments and why and who can do anything about them, and (2) what are the current priorities for the D8 version and who can work on them.
  10. Let's update the module front page with information about any upcoming meetings. Can @JonFreed be granted edit access?
  11. Perhaps there could be a dRealty-oriented meetup at the DrupalCon around May 9-11.
  12. @JonFreed solicited @shauntyndall to provide a conceptual sketch of a possible bare skeleton for D8 with loosely coupled components (that can be worked separately by developers). It will hopefully be ready a week or more before our next hangout that will be April 22 at 1 pm ET so that people can digest it and react. Hangout link: https://hangouts.google.com/hangouts/_/ftechs.com/hangoutfordrealtycoordination
  13. ALL are invited to post comments prior to our late-April meeting with opinions about what's happening. ALL are especially invited to post ideas about the skeleton and its components. Such ideas certainly don't have to be very well organized or presented. For example, a picture of some scribblings on a piece of paper or whiteboard is better than anything we have in front of us now!

=-=-=-=-=-=-=-=-=-=-=-=-=-=

Iterative development of a D8 version will be done in the "8.x-3.x" git branch and released through the "8.x-3.x-dev" release.

For the latest status of what is in the "8.x-3.x-dev" release please view the 8.x-3.x-dev release's page β†’ . (It will probably be updated before this page is.)

The release that is marked as " 8.x-3.x-dev β†’ " will not be usable and will not be supported until further notice.

The initial code in the 8.x-3.x branch is from the 7.x-3.x git branch as of the morning of March 5, 2016. (Any subsequent changes that occur in a 7.x branch will have to be intentionally evaluated and migrated to the 8.x branch. Such migrations do not happen automatically.)

🌱 Plan
Status

Fixed

Version

4.0

Component

Code

Created by

πŸ‡ΊπŸ‡ΈUnited States glass.dimly

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • πŸ‡ΊπŸ‡ΈUnited States timb

    I too am interested in any updates to the D8/9 version of dReality. Thanks

  • πŸ‡ΊπŸ‡ΈUnited States shauntyndall

    Sorry. I just asked @veronicaSeveryn to see if she could find some time in March to package up the D9 version and get it posted. It has been operational on a client site for a while but we've not put together a decent README and linted the code for sharing.

  • πŸ‡ΊπŸ‡ΈUnited States timb

    @shauntyndall Thank you for following up on this. I would love to be able to use Drupal for an upcoming project.

  • πŸ‡ΊπŸ‡ΈUnited States timb

    I have begun developing a module using PHRets. Which will probably be hardcoded to the specific RETS server and queries I need to make.

    I would still like to see (and possibly use / improve upon) the solution that the Drupal community has come up with.

  • πŸ‡ΊπŸ‡ΈUnited States timb

    As an update to anyone else looking for this module and ending up here.

    It appears the development of this module has been taken private and is no longer being updated on drupal.org.

    Here was my quick (& dirty) solution to getting RETS queries into Drupal 8+:
    - use composer to include PHRets library in drupal install
    - create a module to run RETS query and store as CSV to drupal filesystem
    - use feeds (and feeds tamper) to read csv file into nodes

  • Status changed to Fixed about 1 year ago
  • πŸ‡ΊπŸ‡ΈUnited States veronicaSeveryn

    A new releases has been added to drupal.org project, which now supports Drupal ^8.9|9
    It is being used in production on one of the sites (PHP 8.0) and it proved to be operational (RETS system utilized for connection in this case is BRIGHT MLS).

    Feel free to test it out and report any issues found.

  • Automatically closed - issue fixed for 2 weeks with no activity.

Production build 0.69.0 2024