Issue Feature Closed

#87113RECORDS type should have content fallback support on multi language sites

Till Schweneker 12/10/18, 08:45 updated 02/19/22, 13:48

Description

When using the RECORDS type in a multi language site, the record is only fetched correctly if it is translated. It would be nice, if the content fallback to the configured language would work.

e.g.:
temp.receiverName = RECORDS
temp.receiverName {
dontCheckPid = 1
tables = tt_address
source.data = GP:tx_ttaddress_listview|address
conf.tt_address = TEXT
conf.tt_address.value = {field:first_name} {field:last_name}
conf.tt_address.value.insertData = 1
}

Reviews 0

No change resolves or names this issue in its commit message, and no comment links one.