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 (note: Hangouts limits active participants to 10 or 15)

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 (@shauntyndall had set up the Hangout after coordination in this issue's comments.) 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.)

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

bloomt’s picture

I am also curious about moving this module to drupal 8.

JonFreed’s picture

I'm also interested, and I'm willing to work on this, preferably in coordination with one of the experienced module maintainers. I have a client broker in southeast Ohio that is interested in doing a D8 site.

ncswi’s picture

I am also willing to provide testing and servers to help move this forward.

JonFreed’s picture

Title: Drupal 8 Plan? » Plan for dRealty for Drupal 8 (Drupal RETS Real Estate Framework)

Changing title to help others find this "issue" and understand what it is.

Here is a module related to upgrading a 7.x module for 8.x: https://www.drupal.org/documentation/modules/drupalmoduleupgrader

I'll add more info later.

kevinquillen’s picture

To be fair, a lot of work will be involved making a Drupal 8 version available. It's not as simple as a 'port' or module conversion. There is a lot going on under the hood that touches Drupal and a lot that doesn't touch Drupal at all. At the same time, a new version of the phrets wrapper for working with RETS systems is available, so it is likely a lot of code interfacing with phrets would need to be adjusted or flat out rewritten to conform.

I don't even work on real estate sites anymore as I have made an effort to move away from it, so if anyone wants to step up and tackle the mountain of drealty, commit away.

JonFreed’s picture

@kevinquillen, please consider adding me as a project co-maintainer with commit rights so that I can collaborate with others on a D8 version through this project. All I can offer at the moment is a good faith effort to the extent that I have time, and I don't have much time. But it's better than nothing?

I'll admit, I'm fairly new to the Drupal project module development process. I've been working through the process lately for the creation and release of a new D8 module, "View area Button". (That module doesn't have any particular relevance to dRealty. I have just referenced it to provide some indication as to how much -- or how little -- experience I have with the project module development process.)

kevinquillen’s picture

Plus I just don't have any access to MLS systems (which makes development on this impossible), I don't like to deal with REALTOR boards because they've been a huge pain in the #$^@ in the past. It's a shame because I like working with data.

You now have access.

ncswi’s picture

Again, I would be more than happy to dedicated a Fedora-based server and an MLS RETS connection for this project. Please let me know...

JonFreed’s picture

@kevinquillen, thank you! I have access through a client that isn't likely to end soon because she's my wife. :)

@ncswi, thank you for the offer! It was not clear from your earlier comment that you had access to an MLS through RETS. That will be very helpful for testing. Perhaps I can develop and unit test some things and you can then test the things that I commit up to a dev version in this project. It will be slow going though, probably.

JonFreed’s picture

Issue summary: View changes

An 8.x branch has been created. Initially, it contains 7.x-3.x code that was merged into the 8.x-3.x branch through a git merge.

With apologies to glass.dimly, who originally reported this issue, I'm boldly but hopefully respectfully and appropriately commandeering this issue's summary text to contain an update about the status of the 8.x release.

shauntyndall’s picture

@JonFreed Inclind is planning continued sponsorship of the drealty module (including the 8.x release). I'd be glad to coordinate with you on this effort.

JonFreed’s picture

@shauntyndall, that sounds great! I certainly do not feel as if I own the 8.x effort in any way, so by all means please don't let me give you any reason to hesitate in leading onward, especially when the project's front page notes that development is sponsored by Inclind. (Incidentally, the Inclind services page's link for "Drupal real estate" just gave me a 404.)

I am more than happy to watch others lead the 8.x work on this module because the time I have to contribute is very limited and sporadic. My core interest at this time is just helping 8.x happen sooner rather than later. Still, I'm sure I'll come up with a few feature requests at some point. :) For example, and if dRealty doesn't already do this, my client has a requirement that views of listings shall, when appropriate, show her listings first, then her office's, and then others.

I am a newcomer to Drupal module development, especially collaborative Drupal module development, and a relative newcomer to git as well. So, I'm very open to details about how to coordinate development work with you and others through any regular practices that exist for collaborative Drupal module develoment. I wouldn't want to accidentally commit my changes over anybody else's. Hopefully what I have done in the past week for setting up the 8.x branch is okay. If it isn't, feel free to blow it away.

bloomt’s picture

Version: 7.x-3.x-dev » 8.x-3.x-dev
shauntyndall’s picture

@johnfreed please don't have the impression that Inclind "owns" the project. We, like others just have a number of clients using the module so there is an interest nurturing its progress.

Since the D6 version there have been contributors that have taken the torch and forged ahead. I don't see this as any different as not all participant have the interest or the availability to participate as they may have in the past. The biggest challenge to any open source effort like this is leadership / organization as previous efforts have left this module bug ridden and generally difficult to implement.

I think the first step toward progress would be a discovery meeting. Maybe we could schedule a hangout for contributors and agree on the scope of an initial release?

JonFreed’s picture

@shauntyndall, a hangout for contributors sounds good. Hopefully the people who are the most interested in this topic are already following this thread. If perhaps you know others you could invite them.

How about March 22 (Tuesday) at 1 pm ET? That gives everybody two weeks to get it on their calendar.

Would you like to host through whatever hangout technology you prefer, e.g. Google Hangouts?

shauntyndall’s picture

@jonfreed I created a public Hangout (https://plus.google.com/events/cirt40aaqtfgtafok9sejaivf2o) for March 22 @ 1PM. We can start with that and if it needs rescheduling or different tech I'm flexible. Look forward to speaking with you.

In the mean time, we can continue to the discovery discussion and capture specific topics to discuss (if that's reasonable).

JonFreed’s picture

@[shauntyndall] thank you. I've updated the issue description with the meeting information and a proposed agenda. As far as I'm concerned, everybody should feel free to mercilessly edit it! Shaun, I'm propose that you are the moderator for the purpose of shepherding participants through any topics that are discussed.

JonFreed’s picture

Issue summary: View changes

Now that the scheduled 3/22 Google Hangout occurred, I'm deleting this issue's main text about a proposed agenda and providing an update based on the meeting discussion.

P.S. I am NOT in charge around here. :) I'm very new to this module, so I apologize if I'm overstepping any kind of role. Please let me know if there's any way that I can improve my participation in this effort. I just want to build and keep some forward momentum. My selfish interests are to lower costs for my wife's real estate business and to enjoy puttering around with some back-end code. If I'm anything, I'm no more than a voluntary and self-appointed scheduler and task tracker.

JonFreed’s picture

Issue summary: View changes

I'm now updating the issue texxt with a definite time for our next Google Hangout for coordination: 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 on this Google Calendar link to add the meeting details to your calendar (date, time, agenda, hangout url, etc)

JonFreed’s picture

Issue summary: View changes
JonFreed’s picture

Cross-posted event to Real Estate group. See https://groups.drupal.org/node/509949

camidoo’s picture

I've put the 4/22 meeting on my calendar. I plan to attend and provide any answers that I can.

JonFreed’s picture

Sandbox 8.x version found (it's by alexweber), but no commits since August 2014. I don't know if it's at all usable.

I sent alexweber a Drupal.org email and let him know about this thread. If any of you know Alex and can reach out to him as well then please do so. Also, if anybody wants to review his code and provide us with your thoughts that would be great! Maybe it represents a good start or even a nearly-complete 8.x version? (We can always hope.)

shauntyndall’s picture

I've reviewed all 150 issue in the queue. Hopefully I didn't step on any toes but I found lots of seemingly outdated issues.

There are a number of user stories and documentation considerations captured in @jonfreed's spreadsheet: https://docs.google.com/spreadsheets/d/1ZRP6eMEppZSaW78QJgDHzng6X2LdK9Qk....

I'm now going to shift my focus to clarifying / accomplishing a D7 stable release...see #1951580: Drealty 7.x-3.x roadmap. Which I hope leads to full focus on the 8.x version.

jcandan’s picture

subscribed.

alexweber’s picture

Hey all, I'm here :) My sandbox is completely outdated, was a start during one of the early D8 alphas and won't really help as far as I can recall. I'm no longer working on RETS stuff at the moment but wish you all the best of luck! :)

Jalite1991’s picture

Hello. I wondering if I could be of any help in moving this project into D8. I am not that strong with module development yet, and this would actually be my first time contributing to the community. Still I would like to give it a shot if you guys would have me.

bloomt’s picture

I am also willing to contribute, but have minimal experience with contributing but have worked quite a bit with phrets.

Mig2000’s picture

I am really interested in this module for Drupal 8.

Bala72’s picture

Any update on DRealty for D8? Last update is 2 years ago. I use D7 Drealty and can help with testing since I have access to MLS data as I am licenced.

shauntyndall’s picture

Not really. Not much capacity or customer interest from our group.

thavap’s picture

Hi

I am new to Drupal, I want to build a real-estate website with RETS database connection

anyone guide me which drupal version support drealty (version) module and how to configure this module, how to show up in front end

Please help me....

Thanks

Thava

gisle’s picture

thavap, if you take a look on this extension's project page: https://www.drupal.org/project/drealty - and scroll down to bottom, you see a green box and inside it

7.x-3.0 realeased 27 December 2016
Requires Drupal: 7.x

This means that you should be able to run this on Drupal 7. That version reaches EOL in 2022, so you may be better off looking elsewhere.

It is also stated on that page that the development version for Drupal 8 is "unusable and unsupported" I.e. it will not work with any newer version of Drupal (i.e. Drupal 8 or Drupal 9). I think that what can be inferred from this thread is that the project has run out of steam ("Not much capacity or customer interest"). I.e. those who once maintained it has moved on and no new people has committed to helping out.

To learn how to configure this module read its documentation. If you're unable to figure it out from the documentation, hire someone to assist you. I think is unlikely that anyone will commit to such provide you with this type of assistance pro bono.

platinum1’s picture

Hard to believe that there is not real estate solution for Drupal. I could not even find a real estate oriented theme or distribution to start a project. When one looks on Themeforest.net, one can find more than a dozen for Wordpress. Frustrating...

camidoo’s picture

What's more frustrating is someone 'part' of the drupal community for 8+ years without a single contribution credited to them complaining that Drupal doesn't have a solution to their problem. The beauty of any open source project is the ability to add/remove/modify what you need to make it work for you.

If you can't find something you are looking for, you can take what's here already and build upon it and make it work for yourself. Then share it back to the community. This is exactly what I did 11 years ago. I have not really done any real Drupal development in over 8 years. I am fairly certain that if you wanted to pick up the dRealty torch no one is going to have an issue with that.

Try to at least keep the spirit of open source software alive, especially in the community for an open source project. It's not good form to complain about what's not available to you for free, it's better to do something about it and give back to the community, pay it forward for all, if anything, you have gained from the community.

Have a great day.

shauntyndall’s picture

Inclind remains interested in contributing but we've not found the opportunity to leverage dRealty (PHPRets) in Drupal 8/9. I'm sure with the Drupal 7 to Drupal 8/9 upgrades coming down the pipeline we'll find that opportunity but it's difficult to justify the resources toward porting this module.

jrb’s picture

There is the Drupal Real Estate module, too. The D8 version of the code there doesn't actually work, but I created a fork of it about a year ago when that maintainer didn't respond:

https://www.drupal.org/sandbox/jrb/3143094

We are using this on a production D8 site right now. The version in that sandbox isn't completely up-to-date with what we're using, but we can update it if there's interest.

platinum1’s picture

@camidoo The various real estate focused Wordpress themes and distributions on Themeforest.net are all commercial projects, in other words not free or open source.

I think you missed my point. My point is that most commercial themes are for a general purpose Drupal site. None are specialized for real estate. I find that surprising. And frustrating for someone that pushes Drupal whenever he can.

I have no problem paying for a theme or distribution or making a financial contribution, which we have done for projects like webform.

gisle’s picture

platinum1’s picture

@gisle Thank you. Very helpful!

shauntyndall’s picture

We've found some upcoming projects to justify the development of a Drupal 9.x version of dRealty. A couple of our developers started working on the project this week. Hopefully, we'll have progress to share over the next month.

The Drupal Real Estate project has been part of our evaluation and has inspired a re-think of how the administrative experience can be simplified to make dRealty more approachable. However, we see dRealty as a more efficient path to achieving the goals our projects have.

Early UX draft: https://www.drupal.org/files/issues/2021-09-15/Screen%20Shot%202021-09-1...

karangarske’s picture

@shauntyndall "upcoming projects to justify the development of a Drupal 9.x version of dRealty."
did you get anywhere on this? and is this version using RESO api?
thanks
Karan

shauntyndall’s picture

@karangarske We have made progress. We produced eatonrealty.com (with mlsgrid.com) and currently are in final QA with another brokerage site using a Drupal 9 version of dRealty (still using PHPRETS).

Our plan is to share the D9 version of dRealty once we finish QA on the current project.

DrupalRanger’s picture

@shauntyndall: Currently considering a project for a simple Real Estate Lead Gen site for an agent friend. Trying to decide between Drupal 7 with dRealty or waiting for the new version for D9. I would like your thoughts. I have used dRealty for D7 in the past and I remember having to create a ton of fields and that the setup took a few weeks at least.

Any insights would be great.

Cheers

shauntyndall’s picture

@drupalranger I think the D9 version will be available in May. The UI for field mapping is now directly tied to the “normal” Drupal field creation process so we think it is easier to understand / manage. No matter what it is a decent amount of work depending on the number of entities / fields you decide to import and configure.

andreayaya’s picture

Great news about D9 being available in May! When do you think it will appear as a RC? I see there has been no updates to the dev version since 2016.

shauntyndall’s picture

@andreayaya Hopefully in a couple of weeks. We just pushed out a version today for more internal testing. It takes time to package the work up and provide some documentation.

bfajen’s picture

@shauntyndall Do you have any update regarding the Drupal 9 version of dRealty?

timb’s picture

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

shauntyndall’s picture

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.

timb’s picture

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

BeatnikDude’s picture

Following, I am interested trying the Drupal 9 version

timb’s picture

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.

timb’s picture

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

veronicaSeveryn’s picture

Version: 8.x-3.x-dev » 4.0.0
Status: Active » Fixed

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.

Status: Fixed » Closed (fixed)

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