From d822ea93e63494dd23cf0eecf6bc8ac6be43382d Mon Sep 17 00:00:00 2001 From: Travis 'Nep' Smith Date: Wed, 17 Sep 2025 16:23:55 -0500 Subject: [PATCH 1/5] Update entries.md Calling more attention to the Related Category Mode, and making a few more tweaks to add detail. --- docs/channels/entries.md | 32 ++++++++++++++++++++++++++------ 1 file changed, 26 insertions(+), 6 deletions(-) diff --git a/docs/channels/entries.md b/docs/channels/entries.md index 8df31b26..cddc4bee 100755 --- a/docs/channels/entries.md +++ b/docs/channels/entries.md @@ -106,9 +106,9 @@ This parameter lets you set a different limit for the category display than the category="2" -Categories are specified by ID number (the ID number of each category is displayed in the Control Panel). The reason we use the ID is because categories can be called anything (with spaces, quotes, etc.), and also renamed. It would be much more difficult to have to update the tag parameters every time you updated a category name. Further, you can have multiple categories with the same name either in different Category Groups or in different parts of the hierarchy within the same Category Group. +Categories are specified by ID number, not name or category_url_title. The reason we use the ID is because categories can be called anything (with spaces, quotes, etc.), and are often renamed. It would be much more difficult to have to update the tag parameters every time you updated a category name. Furthermore, you can have multiple categories with the same name in different Category Groups or even in different parts of the hierarchy within the same Category Group. And category_url_title must be unique within a Category Group, but does not have to be across different Category Groups. -And as with some of the other parameters, you can stack categories to get entries with any of those categories +As with some of the other parameters, you can stack categories to get entries with any of those categories -- the pipe means OR. category="2|45|4|9" @@ -116,7 +116,7 @@ Or use "not" to exclude categories category="not 4|5|7" -And, you can use an inclusive stack to only get entries with _all_ of the categories +And, you can use an inclusive stack to only get entries matching _all_ of the categories category="3&7&8" @@ -130,6 +130,8 @@ NOTE: **Note:** If you are using exclusion (`category="not 3|4"`) and an entry i NOTE: **Note:** Using this parameter will automatically cause ExpressionEngine to _ignore_ any category information specified via the URL. For instance, if you are on a "category page" (e.g. a `/C13/` segment in the URL) that will be completely ignored in favor of whatever you have specified via the parameter. +NOTE: **Note:** If you want to list entries related to the current entry by its categories, use the [related_categories_mode](#related_categories_mode) parameter. + ### `category_group=` category_group="2" @@ -160,6 +162,18 @@ Or you can add the word "not" (with a space after it) to exclude channels: You must specify this parameter if you use the [category name in URL](control-panel/settings/content-design.md) feature. +### `channel_entries_limit=` + + channel_entries_limit="10" + +This is used only in [Related Categories Mode](#related_categories_mode). Do not get this confused with the more frequently used [limit=](#limit) parameter. + +### `custom_fields=` + + custom_fields="yes" + +This is used only in [Related Categories Mode](#related_categories_mode). Do not get this confused with the more frequently used [disable=](#disable) parameter. + ### `disable=` disable="categories" @@ -327,15 +341,21 @@ Or exclude roles using "not" limit="12" -This parameter limits the number of entries on any given page. The limit will default to 100 entries if a value is not specified. If you are using [pagination](templates/pagination.md) then this will determine the number of entries shown per page. +This common parameter limits the number of entries on any given page. The limit will default to 100 entries if a value is not specified. If you are using [pagination](templates/pagination.md) then this will determine the number of entries shown per page. You can simultaneously set alternative limits for [pages filtered by month](#year-month-day) (`month_limit`) and [pages filtered by category](#category) (`cat_limit`) and [Related Category pages](#related_categories_mode) (`related_categories_mode`). + +### `member_data=` + + member_data="yes" + +This is used only in [Related Categories Mode](#related_categories_mode). Do not get this confused with the more frequently used [disable=](#disable) parameter. ### `month_limit=` month_limit="30" -This parameter lets you set a different limit for the month display than the regular display. For example, let's say you normally only want 10 entries on your main channel page, but you want 100 entries shown when viewing a specific month. For that, you could do this: +This parameter lets you set a different limit for the month display than the regular display. For example, let's say you normally only want 10 entries on your main channel page, but you want 30 entries shown when viewing in the context of a specific month. For that, you could use this code, and the month limit would be used if the URL was something like: `example.com/blog/2025/10` - {exp:channel:entries limit="10" month_limit="100"} + {exp:channel:entries limit="10" month_limit="30"} ### `offset=` From 3188529432335ae1880bc7234894c801aa32a605 Mon Sep 17 00:00:00 2001 From: robinsowell Date: Thu, 18 Sep 2025 16:24:00 -0400 Subject: [PATCH 2/5] Documenting the entry_status parameter for comment forms --- docs/comment/entries.md | 2 ++ docs/comment/form.md | 6 ++++++ 2 files changed, 8 insertions(+) diff --git a/docs/comment/entries.md b/docs/comment/entries.md index 59a4c679..9b000dd0 100755 --- a/docs/comment/entries.md +++ b/docs/comment/entries.md @@ -78,6 +78,8 @@ NOTE: **Note:** This parameter takes precedence over any entry specified dynamic entry_status="Featured" +NOTE: **Note:** If this parameter is not specified, comments for entries with any status other than "closed" will be returned. + ### `limit=` limit="30" diff --git a/docs/comment/form.md b/docs/comment/form.md index ec8c696a..926e46df 100755 --- a/docs/comment/form.md +++ b/docs/comment/form.md @@ -74,6 +74,12 @@ You can hard code the comment form tag to display a comment form for a specific NOTE: **Note:** This parameter takes precedence over any entry specified dynamically in the URL, so when using this parameter you will want to make sure it is clear to the user which entry the displayed comment form belongs to. +### `entry_status=` + + entry_status="Featured" + +NOTE: **Note:** If this parameter is not specified, the form display will not be affected by an entry's status, unless the entry is set to "closed". + #### `form_class=` form_class="news_comment_form" From 35eff1a08080154f7b15c6006d6dda6c01f386ef Mon Sep 17 00:00:00 2001 From: Yuri Salimovskiy Date: Sun, 7 Dec 2025 12:14:29 +0200 Subject: [PATCH 3/5] Added `image_manipulation_quality` config override; #4992 --- docs/general/system-configuration-overrides.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/docs/general/system-configuration-overrides.md b/docs/general/system-configuration-overrides.md index 26cc3d44..2f31913f 100755 --- a/docs/general/system-configuration-overrides.md +++ b/docs/general/system-configuration-overrides.md @@ -1670,6 +1670,14 @@ Example Usage: **Also found in CP:** `Settings --> Content & Design`: [Image Resizing Protocol](control-panel/settings/content-design.md#protocol) +## `image_manipulation_quality` + +Default quality for [on-the-fly image manipulations](fieldtypes/file.md#on-the-fly-image-manipulations) (resizing, cropping, etc.). Value should be greater than 0 (lowest quality, smallest file size) and below or equal to 100 (highest quality, largest file size). When not set, the default quality is 75. + +Example Usage: + + $config['image_manipulation_quality'] = 90; + ## `include_seconds` Set the system to include seconds when time is displayed in the interface. From d2dc5789b69926594dd8adc6c0aee8a379fcb96e Mon Sep 17 00:00:00 2001 From: Bryan Nielsen Date: Wed, 25 Feb 2026 11:28:00 -0500 Subject: [PATCH 4/5] Version 7.5.20 --- docs/installation/changelog.md | 56 ++++++++++++++++++++++++++++++++++ 1 file changed, 56 insertions(+) diff --git a/docs/installation/changelog.md b/docs/installation/changelog.md index fd9f0db4..c10f9587 100755 --- a/docs/installation/changelog.md +++ b/docs/installation/changelog.md @@ -8,6 +8,62 @@ --> # ExpressionEngine v7 Change Log + +## Version 7.5.20 +(Release: February 25th, 2026) + +NOTE: **Important:** This version includes important security updates. + +
+
+ +
+
+ +**Enhancements** 🚀 + +- Add rate limiting and cleanup for member captchas +- Add must-interact functionality to modals to prevent closing +- Enable 1st-Party Addon Support for CLI Generators with AbstractGenerator Refactor +- Add support in Pro Search for signed parameters +- Added `image_manipulation_quality` config override; [#4992](https://github.com/ExpressionEngine/ExpressionEngine/issues/4992) +- Added `orderby` parameter to `exp:channel:categories` tag; [#4340](https://github.com/ExpressionEngine/ExpressionEngine/issues/4340) + +**Bug Fixes** 💃🐛 + +- Resolved [#4339](https://github.com/ExpressionEngine/ExpressionEngine/issues/4339) where it was not possible to validate custom field names outside of CP +- Resolved [#4690](https://github.com/ExpressionEngine/ExpressionEngine/issues/4690) MSM wrong config issue +- Resolved [#5011](https://github.com/ExpressionEngine/ExpressionEngine/issues/5011) where file size was not updated when file is replaced +- Resolved [#5018](https://github.com/ExpressionEngine/ExpressionEngine/issues/5018) where deleting an MSM site could fail due to upload destination error. +- Resolved [#5071](https://github.com/ExpressionEngine/ExpressionEngine/issues/5071) where saving Pro Search setting could show PHP warning +- Resolved [#5106](https://github.com/ExpressionEngine/ExpressionEngine/issues/5106) where Pro Variables: Select Entries Relationship UI Issue (Search and Channel Filtering returning no entries) +- Resolved [#5126](https://github.com/ExpressionEngine/ExpressionEngine/issues/5126) where RedactorX had a validation issue in a Grid field +- Resolved an issue where spellcheck and survey libraries had relaxed curl verification +- Resolved an issue where regex template routes could create PHP warnings +- Resolved a possible generator error when field type was missing +- Resolved an empty data error in Member fieldtype +- Resolved an issue causing TypeErrors when using Live Preview +- Resolved an issue where Live Preview origins could be handled more strictly +- Resolved an error with relationship single variable + +**Developers** 💻 + +- Added unit tests for several core Add-ons and libraries +- Cleaned up unused action in Stats Add-on +- Added stricter property casts in Image library +- Update handling of referrer in Member module's select_avatar + ## Version 7.5.19 (Release: January 21st, 2026)
From 3d06b5341f798bfc81ad9f7d48f205cb0aa22f46 Mon Sep 17 00:00:00 2001 From: Bryan Nielsen Date: Thu, 26 Feb 2026 10:34:20 -0500 Subject: [PATCH 5/5] Update 7.5.20 release date --- docs/installation/changelog.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/installation/changelog.md b/docs/installation/changelog.md index c10f9587..fd8414ca 100755 --- a/docs/installation/changelog.md +++ b/docs/installation/changelog.md @@ -10,7 +10,7 @@ ## Version 7.5.20 -(Release: February 25th, 2026) +(Release: February 26th, 2026) NOTE: **Important:** This version includes important security updates.