Name: Realworks Integration
Description: This module uses cron to synchronise with the Dutch Realworks real estate service, xml is fetched once a day and included images are fetched only when needed (new or updated). The xml is parsed on the fly to provide Realworks real estate entries on your site, there are several templates to provide close integration with your site's theming.
At the moment not all fields from the xml are used, it's a very complex scheme and to make matters worse: Realworks explicitly states they can change it at any time as they please without prior notice.
Sandbox link: http://drupal.org/sandbox/cinnamon/1151546
| Comment | File | Size | Author |
|---|---|---|---|
| #11 | realworks.patch | 2.32 KB | cinnamon |
| #9 | realworks.module.patch | 821 bytes | cinnamon |
Comments
Comment #1
cinnamon commentedComment #2
ralt commentedHi,
Do you have a demo website?
Also, don't you think you can achieve the same thing with Feeds?
Comment #3
ralt commentedComment #4
jordojuice commentedUpdating title and tags. Why active? The normal workflow is to switch between needs work and needs review (unless a module is postponed or something).
Comment #5
ralt commentedWhen waiting for OP info, isn't active the right status?
Comment #6
jordojuice commentedNot according to common practice and documentation. Workflow documentation for project applications can be found at http://drupal.org/node/532400. It can be confusing that it is a bit different than most other queues. We normally change the status to a more appropriate status when there's an "Active" issue in the queue, as well as any applications with priorities other than "normal". Some of these items may change in the near future, but for now the workflow remains. By the way, you are doing a fantastic job! You seem to be getting a ton done, which is badly needed in this queue! (not just saying that either)
Comment #7
joachim commentedWeird. Either use a variable or a constant, not both.
Weirder. WTF?
This needs a lot of work, though bear in mind Ralt's comment above on Feeds.
Comment #8
cinnamon commentedDemo would be http://www.mennes.nl, all the property listings there are fetched, processed and displayed through this module. Perhaps feeds would get me half the way but I highly doubt it: we need to fetch the xml exactly once a day not more (penalty if the client exceeds this) and images need to be cached locally (same penalty there). Also the xml is very complex, one could argue they did that on purpose ;)
All and all this is very very specific to the Dutch Realworks realestate service, but perhaps it could be of use to the Dutch drupal community.
About the weird and weider parts: I started out with a piece of code my former college made and that bypassed Drupal completely ... this must be some of very little of that code left, could be done better agreed.
Comment #9
cinnamon commentedGot rid of the WTF part ;) Is it really mandatory to get rid of the constants? I understand it isn't pretty but safes me from quite at lot of typing.
The real module is in production and just works(tm), consider this an alpha release of a more generic module that might be of use to others working in the dutch realestate business with Drupal.
Comment #10
joachim commented> Is it really mandatory to get rid of the constants?
Defining a constant to be the value of a variable just seems very weird. Constants should be constant.
Comment #11
cinnamon commentedYou're right. Anyway I was making too much of a problem, it wasn't that much work.
Please let me know if there are more problems, as said the module is in use and just works for our client.
Comment #12
klausiNo activity in several months. Reopen and set the status to "needs review" if you are still pursuing this application.