FAQ
Frequently asked questions
In order to access a custom/user-defined node, you just have to concatenate the XML-xpath into one identifier and use it within the getProperty ViewHelper. For example:
<immobilie>
<kontaktperson>
<email_direkt>mail(at)example(dot)org</email_direkt>
</kontaktperson>
</immobilie>{oi:getProperty(object: immobilie, index: 'kontaktperson_emailDirekt')}or:
<immobilie>
<verwaltung_techn>
<user_defined_simplefield feldname="reserviert">ja</user_defined_simplefield>
</verwaltung_techn>
</immobilie>{oi:getProperty(object: immobilie, index: 'verwaltungTechn_userDefinedSimplefield_reserviert')}In the identifier each XML nodename is divided by a _. If the nodename contains a _ it will be transformed to lower-camel-case.
In order to access the meta data of an attached file or image, you can use the following Fluid code:
<f:for each="{immobilie.images}" as="image" iteration="imageIteration">
<span>{image.file.originalResource.properties.size}</span>
<span>{image.file.originalResource.properties.mime_type}</span>
</f:for>Der Importer greift während der Ausführung auf deine TypoScript-Einstellungen zurück. Um diese zu finden hangelt er sich vom Daten-Container die Rootline hoch und versucht ein TypoScript-Template zu finden. Wenn er kein TypoScript-Template bzw. keine Root-Seite findet, entsteht dieser Fehler.
Der Fehler ist aber schnell korrigiert. Verschiebe einfach den Daten-Container für die OpenImmo-Datensätze in einen Seitenzweig. Wenn Du mehrere Seitenzweige hast auf denen Immobilien dargestellt werden, ist es egal in welchen Zweig Du die Daten verschiebst - es ist nur wichtig zu wissen, das der Importer im TypoScript-Template seine Konfiguration findet.
The search/list view shows the following SQL error:
An exception occurred while executing 'SELECT `geo_ort`, `geo_regionaler_zusatz` FROM `tx_openimmo_domain_model_immobilie` WHERE (`uid` > 0) AND ((`tx_openimmo_domain_model_immobilie`.`deleted` = 0) AND (`tx_openimmo_domain_model_immobilie`.`hidden` = 0) AND (`tx_openimmo_domain_model_immobilie`.`starttime` <= 1634053020) AND ((`tx_openimmo_domain_model_immobilie`.`endtime` = 0) OR (`tx_openimmo_domain_model_immobilie`.`endtime` > 1634053020))) GROUP BY `geo_regionaler_zusatz` ORDER BY `geo_regionaler_zusatz` ASC': Expression #1 of SELECT list is not in GROUP BY clause and contains nonaggregated column 'dwg-online.tx_openimmo_domain_model_immobilie.geo_ort' which is not functionally dependent on columns in GROUP BY clause; this is incompatible with sql_mode=only_full_group_byTry to set the SQL mode:
sql_mode = ''The TypoScript settings from settings.list. * have been removed because they were outdated. Changes must be transferred over into settings.search. *.
In addition, the for-each loop in the Property / Search / Item.html Partial must be changed.
From:
<f:for each="{settings.list.fieldsets}" as="fieldset" key="fieldsetKey">To:
<f:for each="{settings.search.fieldsets}" as="fieldset" key="fieldsetKey">We always try to keep our extensions compatible with the current TYPO3-LTS versions. Have a look at the product page compatibility selection.
TYPO3 OpenImmo
TYPO3 OpenImmo is a real estate extension that reads in your objects via an OpenImmo import and displays them on your website.