Skip to content

Commit 8cf2738

Browse files
[Backport 14.3] [TASK] Clarify usage of extension configuration settings in _ForeignTableWhere.rst.txt, section "###SITE:<KEY>.<SUBKEY>###" (#1412)
[TASK] Clarify usage of extension configuration settings in _ForeignTableWhere.rst.txt, section "###SITE:<KEY>.<SUBKEY>###" (#1394) Update _ForeignTableWhere.rst.txt, section "###SITE:<KEY>.<SUBKEY>###" Add hint for usage of extension configuration settings (cherry picked from commit 962e732) Co-authored-by: Markus <markus.zipfel@aimcom.de>
1 parent 4f96973 commit 8cf2738

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

Documentation/ColumnsConfig/Type/Select/Single/_Properties/_ForeignTableWhere.rst.txt

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -53,7 +53,7 @@ It is possible to use markers in the WHERE clause:
5353
A value you can set from Page TSconfig dynamically.
5454

5555
###SITE:<KEY>.<SUBKEY>###
56-
A value from the site configuration, for example: `###SITE:mySetting.categoryPid###` or `###SITE:rootPageId###`.
56+
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###`
5757

5858
The markers are preprocessed so that the value of CURRENT\_PID and PAGE\_TSCONFIG\_ID are always integers
5959
(default is zero), PAGE\_TSCONFIG\_IDLIST will always be a comma-separated list of integers (default is zero)

0 commit comments

Comments
 (0)