From dcc4e580993736c6cf271ca39a19a47b183f4c7a Mon Sep 17 00:00:00 2001 From: Travis 'Nep' Smith Date: Wed, 5 Nov 2025 02:41:20 -0700 Subject: [PATCH 1/2] Update entries.md with additional disable notes Clarified the implications of disabling custom fields and relationships in the documentation. --- docs/channels/entries.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/channels/entries.md b/docs/channels/entries.md index 8df31b26..b0c30bc9 100755 --- a/docs/channels/entries.md +++ b/docs/channels/entries.md @@ -177,7 +177,7 @@ The syntax for the disable parameter is this: `disable="ITEM YOU WANT TO DISABLE - `relationship_custom_fields` - `relationship_categories` -NOTE: **Note:** If you disable categories, category fields will automatically be disabled. +NOTE: **Note:** If you disable categories, category fields will automatically be disabled. If you disable custom_fields, that includes relationships. If you disable relationships, [relationship_custom_fields and relationship_categories](fieldtypes/relationships.md#optimizing-relationships-performance) will automatically be disabled. You may specify multiple items to disable by separating them with the pipe character: @@ -191,7 +191,7 @@ For example, let's say you are using an instance of your channel tag to show you {title}
{/exp:channel:entries} -In this example you are only showing the title of your entries and nothing else; yet, the channel tag automatically fetches categories and other data. Using the disable= parameter you can turn off the unneeded features from being queried. In this case, you don't need any of the features that can be disabled. +In this example you are only showing the title of your entries and nothing else; yet, the channel tag automatically fetches categories and other data. Using the disable= parameter you can turn off the unneeded features from being queried. In this case, you don't need any of the features and they all can be disabled. {exp:channel:entries orderby="date" sort="desc" limit="10" disable="categories|custom_fields|member_data|pagination"} {title}
From fd895b63c2dc7d2af832c67294fec704032a1597 Mon Sep 17 00:00:00 2001 From: Travis 'Nep' Smith Date: Wed, 5 Nov 2025 02:47:34 -0700 Subject: [PATCH 2/2] Improve clarity on optimizing relationship field performance Clarified recommendation for optimizing relationship fields performance by specifying the `disable` parameter link. --- docs/fieldtypes/relationships.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/fieldtypes/relationships.md b/docs/fieldtypes/relationships.md index c843e314..bf603461 100755 --- a/docs/fieldtypes/relationships.md +++ b/docs/fieldtypes/relationships.md @@ -336,7 +336,7 @@ Would output in the format: ## Optimizing Relationships Performance -If you are heavily using relationship fields, it is recommended that you disable certain features, such as custom fields or categories on related entries, to speed up template loading. That can be done by applying `disable` parameter to the `exp:channel:entries` tag that includes relationship field tag (or siblings / parents tag). +If you are heavily using relationship fields, it is recommended that you disable certain features such as custom fields or categories on the related entries to speed up template loading. That can be done by applying the [`disable` parameter](/channels/entries.md#disable) to the `exp:channel:entries` tag that includes the relationship field tag (or siblings / parents tag). The following items can be turned off: