Skip to content

Custom Fields

Under WP-ImmoMakler → Settings → Custom Fields you configure any WordPress post meta field as custom property data. The fields are then available for manual selection in all theme builder widgets (Elementor, Bricks, Divi, WPBakery) and can be shown automatically in the Classic skin between the general property data and the price data.

Custom Fields tab in the WP-ImmoMakler settings with two configured fields, meta key, name and the Show automatically option

Property portals such as FlowFact or Propstack, and individual import scripts, frequently write additional data into WordPress post meta fields that WP-ImmoMakler does not know out of the box. The “Custom Fields” feature lets you bring those fields into the property display without any programming.

Typical use cases:

  • The length of a swimming pool (flaechen-user_defined_simplefield-laenge_swimmingpool)
  • The number of underground parking spaces from a custom import field
  • Internal reference numbers that are meant to appear in the property brochure
  1. In the back end of your website (wp-admin), open WP-ImmoMakler → Settings → Custom Fields.
  2. Click + Add field.
  3. Fill in the row:
ColumnDescription
Meta key (post_meta)Technical key name of the WordPress post meta field, e.g. flaechen-user_defined_simplefield-laenge_swimmingpool. Mind upper and lower case; no spaces.
NameThe label shown in the front end, e.g. “Pool length”.
Show automaticallyWhen active, the field is shown automatically in the Classic skin between the general property data and the price data, provided a value exists.
  1. Click Save in the row.

If you transfer your properties via the onOffice API, a selection Custom fields from onOffice additionally appears below the table. It lists the individual fields you created yourself in onOffice, with their onOffice label, grouped by the onOffice area they belong to (e.g. features, prices or additional).

  1. Choose the field you want and click Adopt.
  2. WP-ImmoMakler creates a new row with the matching meta key and the label from onOffice. Adjust the label if needed and enable Show automatically if the field should appear in the Classic skin.
  3. Click Save in the row.

From the next sync onwards, the onOffice API transfers the values of this field. WP-ImmoMakler prepares the values in a readable form: selection fields appear with their onOffice label, dates in the format DD.MM.YYYY, and a yes/no field appears only if it is ticked in onOffice. Empty number and date fields are not transferred.

If you remove such a field from the table again, it is no longer retrieved at the next sync.

  • Edit: Click Edit in the field’s row, change the values and click Save again.
  • Delete: Click the red bin icon next to the field. The field is removed immediately and all remaining fields are saved.

If Show automatically is enabled for a field, it appears in the detail view between the general property data and the price data — provided the property in question has a value for that meta key.

All configured custom fields are available for manual selection in the following widgets:

Theme builderWidget / element
ElementorDynamic tag “Property: Value”, dynamic tag “Property: Name”, widgets Data Boxes, Single Data, Archive Inline List, Icon List, Display Condition
BricksElements Data Boxes, Single Data List
DiviModules Single Data Boxes, Single List
WPBakeryElements Data Boxes, Single Data

WP-ImmoMakler converts boolean raw values into readable terms automatically:

Raw value in post_metaDisplay in the front end
true, yes, ja, on, y, jYes
false, no, nein, off, nNo

All other values are shown unchanged.

Relationship to OpenImmo user_defined_simplefields

Section titled “Relationship to OpenImmo user_defined_simplefields”

WP-ImmoMakler imports OpenImmo user_defined_simplefield values automatically and displays them if the option Show custom OpenImmo-Fields automatically is active in the back end of your website (wp-admin) under Appearance → Customiser → WP-ImmoMakler → Property Detail View. If you additionally configure such a field under “Custom Fields”, it appears only once — controlled by the configuration under “Custom Fields”, no longer as an automatic user_defined_simplefield.