Immobilienscout24 import for Contao Open Source CMS
This package is auto-updated.
Last update: 2021-03-28 11:47:06 UTC
This bundle allows you to import real estate objects from Immoscout24 into your Contao application (4.8+) and display them as native content.
Warning: This is an early release. There might be features missing. Use at your own risk.
Install the bundle and update your database. There is no further configuration necessary.
composer require derhaeuptling/contao-immobilienscout24-import-bundle
Add at least one
Immoscout24 Accountin the backend and enter your API credentials.
Setup a cron job that executes the
immoscout24:synccommand or run it yourself to import real estate objects from the API into your application. You can pass an account's id or description as a parameter to only sync this one account and
--dry-runto only see what would be updated without persisting the changes. Use the option
--purgeto clear the database table and all downloaded files completely beforehand.
If you also want to import attachments, set up a cron job that executes the
Add one or more Immoscout24 modules in your theme and use it in the frontend:
The Real estate list displays a list of real estate objects. If you want to generate a teaser list with 'read more' links, make sure to specify a 'jump to' page with the appropriate reader.
The Real estate reader displays a single real estate object based on the url parameter (id).
List items can be constrained individually by using a filter expression.
Some filter expression examples:
- one object by its ID
realEstateId == 111111111
- some objects by its IDs
realEstateId in [111111111,222222222,333333333]
- all active objects
state == STATUS_ACTIVE
- all objects published to the homepage channel
'Homepage' in publishChannels
- all objects with empty API-Searchfield1
apiSearchData1 != null
- all objects that match a KEYWORD in the title field
title matches "/KEYWORD/"
- combine filter
'Homepage' in publishChannels&&
priceMarketingType == "Kauf"
- one object by its ID
The real estate listings contain lots of fields - most likely you'll want to adapt the templates to your needs and only output some of the fields. To do this, there are some helpers for your convenience.
A) Real estate data comes in the form of an entity instance, you can type hint against it to get IDE auto-completion in your templates:
/** var Derhaeuptling\ContaoImmoscout24\Entity\RealEstate $realEstate */ $realEstate
B) You can also obtain a list of all available attributes:
$this->attributes // array [name => label] of publicly accessible fields of the real estate objects // e.g. 'descriptionNote' that can be accessed via $realEstate->descriptionNote
C) To retrieve and format data, you can use these helper functions:
$this->hasData(RealEstate $realEstate, string $attribute) : bool // will return wether $realEstate holds data for the $attribute $this->getFormatted(RealEstate $realEstate, string $attribute) : string // will return the formatted value of $attribute - enumerations, dates and // booleans will resolved to a string representation based on the language // files
D) If you want to resolve enumerations yourself you can find all of them as
public constants in the
Some enumeration values can occur multiple times per value. In this case they are implemented as binary flags:
FLAG__TYPE_A = 1; FLAG__TYPE_B = 2; FLAG__TYPE_C = 4; FLAG__TYPE_D = 8; FLAG__TYPE_E = 16; // n-of-value selecting 'type A' and 'type E' $value = -(FLAG__TYPE_A | FLAG__TYPE_E); // = 17
Note that flagged values are stored as negative numbers, so that they can easily be differentiated from regular enumeration values.
Real estate objects can have multiple attachments. Note: that currently only images are supported attachment types.
To render an attachment (as picture tag) you can utilize it's
It allows passing in an image size configuration:
// use the settings from the modules ... echo $attachment->render($this->defaultImageSize); echo $attachment->render($this->alternativeImageSize); // ... or define your own echo $attachment->render($myImageSizeConfiguration);
Keep in mind, that the attachment owns the referenced file. This means: Once the attachment is deleted the file will be gone as well.