[FEATURE] Store relations for schema:containedInPlace #184

Merged
Dirk Koritnik merged 1 commit from 13030_contained_in_place into main 2026-08-20 13:03:49 +00:00

Contrary to the initial assumption, 'schema:containedInPlace', shipped
on POIs and other of the Base 'Place', does not contain a single town
record, but it can in fact several of them and also all other kind of
data, like other attractions, organisations and so on.

This caused now the creation of several new fields to tourist attractions
to store those relations that have been silently discarded before.
The single town relation gained the capability to holding more than one.
The Town filter for plugins and Frontend Search learned about this change as
well and can now cope with the multi value.

Resolves: https://redmine.werkraum-media.de/issues/13030
Assisted-by: Claude Opus 5 noreply@anthropic.com

Contrary to the initial assumption, 'schema:containedInPlace', shipped on POIs and other of the Base 'Place', does not contain a single town record, but it can in fact several of them and also all other kind of data, like other attractions, organisations and so on. This caused now the creation of several new fields to tourist attractions to store those relations that have been silently discarded before. The single town relation gained the capability to holding more than one. The Town filter for plugins and Frontend Search learned about this change as well and can now cope with the multi value. Resolves: https://redmine.werkraum-media.de/issues/13030 Assisted-by: Claude Opus 5 noreply@anthropic.com
[FEATURE] Store relations for schema:containedInPlace
All checks were successful
CI / base-qa (pull_request) Successful in 26s
CI / advanced-qa (82, ^13.4) (pull_request) Successful in 4m15s
CI / advanced-qa (82, ^14) (pull_request) Successful in 4m18s
CI / advanced-qa (83, ^13.4) (pull_request) Successful in 4m5s
CI / advanced-qa (83, ^14) (pull_request) Successful in 4m20s
CI / advanced-qa (84, ^13.4) (pull_request) Successful in 4m6s
CI / advanced-qa (84, ^14) (pull_request) Successful in 4m29s
CI / advanced-qa (85, ^13.4) (pull_request) Successful in 4m0s
CI / advanced-qa (85, ^14) (pull_request) Successful in 4m13s
CI / base-qa (push) Successful in 27s
CI / advanced-qa (82, ^13.4) (push) Successful in 4m12s
CI / advanced-qa (82, ^14) (push) Successful in 4m22s
CI / advanced-qa (83, ^13.4) (push) Successful in 4m6s
CI / advanced-qa (83, ^14) (push) Successful in 4m20s
CI / advanced-qa (84, ^13.4) (push) Successful in 4m12s
CI / advanced-qa (84, ^14) (push) Successful in 4m27s
CI / advanced-qa (85, ^13.4) (push) Successful in 4m1s
CI / advanced-qa (85, ^14) (push) Successful in 4m10s
f47fa76b0c
Contrary to the initial assumption, 'schema:containedInPlace', shipped
on POIs and other of the Base 'Place', does not contain a single town
record, but it can in fact several of them and also all other kind of
data, like other attractions, organisations and so on.

This caused now the creation of several new fields to tourist attractions
to store those relations that have been silently discarded before.
The single town relation gained the  capability to holding more than one.
The Town filter for plugins and Frontend Search learned about this change as
well and can now cope with the multi value.

Resolves: https://redmine.werkraum-media.de/issues/13030
Assisted-by: Claude Opus 5 noreply@anthropic.com
Dirk Koritnik deleted branch 13030_contained_in_place 2026-08-20 13:03:49 +00:00
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
typo3/thuecat!184
No description provided.