[DOCS] Rename Changelog compared to subject 51/62351/2
authorJoerg Kummer <typo3@enobe.de>
Thu, 21 Nov 2019 08:16:49 +0000 (09:16 +0100)
committerOliver Hader <oliver.hader@typo3.org>
Thu, 21 Nov 2019 09:37:24 +0000 (10:37 +0100)
Change filename of changelog for issue 88902
fixes ordering in rendered documentation menus.

Releases: master
Resolves: #89719
Change-Id: I2e9e6045610d601e904f7f5b46ff6a2f2d27774f
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/62351
Tested-by: TYPO3com <noreply@typo3.com>
Tested-by: Oliver Hader <oliver.hader@typo3.org>
Reviewed-by: Oliver Hader <oliver.hader@typo3.org>
typo3/sysext/core/Documentation/Changelog/master/Feature-88902-FeatureSwitchRedirectAndStaticRoutesMiddlewaresCanBeReordered.rst [new file with mode: 0644]
typo3/sysext/core/Documentation/Changelog/master/Important-88902-FeatureSwitchRedirectAndStaticRoutesMiddlewaresCanBeReordered.rst [deleted file]

diff --git a/typo3/sysext/core/Documentation/Changelog/master/Feature-88902-FeatureSwitchRedirectAndStaticRoutesMiddlewaresCanBeReordered.rst b/typo3/sysext/core/Documentation/Changelog/master/Feature-88902-FeatureSwitchRedirectAndStaticRoutesMiddlewaresCanBeReordered.rst
new file mode 100644 (file)
index 0000000..48f0a42
--- /dev/null
@@ -0,0 +1,33 @@
+.. include:: ../../Includes.txt
+Feature: #88902 - Feature Switch: Redirect and Base Redirect Middlewares can be reordered
+See :issue:`88902`
+A new feature switch :php:`rearrangedRedirectMiddlewares` has been introduced to rearrange the middlewares
+:php:`typo3/cms-redirects/redirecthandler` and :php:`typo3/cms-frontend/base-redirect-resolver`. If enabled, the
+middlewares are executed in reversed order, so the :php:`typo3/cms-redirects/redirecthandler` comes first.
+The new ordering aims to be a better default shipped by the TYPO3 core but might still need adjustment due to specific
+configuration setups.
+The feature switch is turned off by default to assure a non-breaking behaviour.
+If turned on, the new ordering has the following implications:
+By putting the :php:`typo3/cms-frontend/base-redirect-resolver` last, redirects are always resolved even if no
+configured base URL was requested. In most cases this is considered to be a bugfix. However, redirect behavior might
+Custom middlewares that have been put in between the two above mentioned middlewares most likely will lead to a circular
+dependency exception now. Such custom middlewares have to be revisited and registered differently.
+.. index:: Frontend, NotScanned, ext:redirects
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Important-88902-FeatureSwitchRedirectAndStaticRoutesMiddlewaresCanBeReordered.rst b/typo3/sysext/core/Documentation/Changelog/master/Important-88902-FeatureSwitchRedirectAndStaticRoutesMiddlewaresCanBeReordered.rst
deleted file mode 100644 (file)
index 48f0a42..0000000
+++ /dev/null
@@ -1,33 +0,0 @@
-.. include:: ../../Includes.txt
-Feature: #88902 - Feature Switch: Redirect and Base Redirect Middlewares can be reordered
-See :issue:`88902`
-A new feature switch :php:`rearrangedRedirectMiddlewares` has been introduced to rearrange the middlewares
-:php:`typo3/cms-redirects/redirecthandler` and :php:`typo3/cms-frontend/base-redirect-resolver`. If enabled, the
-middlewares are executed in reversed order, so the :php:`typo3/cms-redirects/redirecthandler` comes first.
-The new ordering aims to be a better default shipped by the TYPO3 core but might still need adjustment due to specific
-configuration setups.
-The feature switch is turned off by default to assure a non-breaking behaviour.
-If turned on, the new ordering has the following implications:
-By putting the :php:`typo3/cms-frontend/base-redirect-resolver` last, redirects are always resolved even if no
-configured base URL was requested. In most cases this is considered to be a bugfix. However, redirect behavior might
-Custom middlewares that have been put in between the two above mentioned middlewares most likely will lead to a circular
-dependency exception now. Such custom middlewares have to be revisited and registered differently.
-.. index:: Frontend, NotScanned, ext:redirects