From aa8e55e7482f1a546bc7327f507815a8eb6b4e8c Mon Sep 17 00:00:00 2001 From: Markus Date: Thu, 4 Jun 2026 12:39:37 +0200 Subject: [PATCH] [TASK] Clarify usage of extension configuration settings in _ForeignTableWhere.rst.txt, section "###SITE:.###" (#1394) Update _ForeignTableWhere.rst.txt, section "###SITE:.###" Add hint for usage of extension configuration settings (cherry picked from commit 962e732af5707e9fcf25252be45f9d3588895acd) --- .../Type/Select/Single/_Properties/_ForeignTableWhere.rst.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Documentation/ColumnsConfig/Type/Select/Single/_Properties/_ForeignTableWhere.rst.txt b/Documentation/ColumnsConfig/Type/Select/Single/_Properties/_ForeignTableWhere.rst.txt index 0ef21b8f..148d239d 100644 --- a/Documentation/ColumnsConfig/Type/Select/Single/_Properties/_ForeignTableWhere.rst.txt +++ b/Documentation/ColumnsConfig/Type/Select/Single/_Properties/_ForeignTableWhere.rst.txt @@ -53,7 +53,7 @@ It is possible to use markers in the WHERE clause: A value you can set from Page TSconfig dynamically. ###SITE:.### - A value from the site configuration, for example: `###SITE:mySetting.categoryPid###` or `###SITE:rootPageId###`. + A value from the site configuration, for example: `###SITE:mySetting.categoryPid###` or `###SITE:rootPageId###`. Also values of extension configuration settings are possible. E.g. if there is `settings.sitepackage.imprintPageUid` defined in `EXT:sitepackage/Configuration/Sets/Sitepackage/settings.definitions.yaml` and set in `config/sites/mysite/settings.yaml`: `###SITE:settings.sitepackage.imprintPageUid###` The markers are preprocessed so that the value of CURRENT\_PID and PAGE\_TSCONFIG\_ID are always integers (default is zero), PAGE\_TSCONFIG\_IDLIST will always be a comma-separated list of integers (default is zero)