You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: Documentation/Installation/Updates/Index.rst
+27-28Lines changed: 27 additions & 28 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -17,8 +17,8 @@ When and why should we perform TYPO3 updates?
17
17
With the newest version of TYPO3 you receive free bugfixes and free security patches
18
18
for at least three years from the time of the first LTS minor (for example v13.1) release.
19
19
20
-
In TYPO3 however, we follow a specific cycle which usually takes 1.5 years long. Every
21
-
1 and a half year a new TYPO3 version occurs. You can follow the cycle `here <https://typo3.org/cms/roadmap>`__.
20
+
In TYPO3 however, we follow a specific `cycle<https://typo3.org/cms/roadmap>`__ which usually takes 1.5 years long. Every
21
+
1 and a half year a new TYPO3 version occurs.
22
22
23
23
We explain the different parts in the `roadmap <https://typo3.org/cms/roadmap>`__ now.
24
24
When you follow the roadmap you see dark red strokes. They represent the **sprint releases**.
@@ -39,7 +39,7 @@ we summarize how a TYPO3 user should act with respect to TYPO3 updates:
39
39
40
40
* When a new major LTS version is released, users **should** focus on updating to this version as soon as possible.
41
41
* When a new minor version is released, users **must** update to the new minor version, since the previous minor version is **not** supported any more.
42
-
* When a new patch level version is released, users should always update to the new version, because it contains important bugfixes and security fixes (if announced). Here you find the `security advisories <https://typo3.org/help/security-advisories>`__.
42
+
* When a new patch level version is released, users **should** always update to the new version, because it contains **important** bugfixes and security fixes (if announced). Here you find the `security advisories <https://typo3.org/help/security-advisories>`__.
43
43
44
44
Additionally, users should take care of updated extensions on a regular schedule
45
45
in order to use the most recent versions.
@@ -57,17 +57,17 @@ Major, minor and patch level updates
57
57
In TYPO3 you can update your TYPO3 version. There exist three different types
58
58
of updates:
59
59
60
-
#. Major updates: from for example 12.4.23 to 13.0.0
61
-
#. Minor updates: from for example 13.0 to 13.1
62
-
#. Patch and bugfix level updates (often security updates): from for example 13.4.0 to 13.4.1
60
+
#. Major updates: for example, from 12.4.23 to 13.0.0
61
+
#. Minor updates: for example, from 13.0 to 13.1
62
+
#. Patch and bugfix level updates (often security updates): for example, from 13.4.0 to 13.4.1
63
63
64
64
65
65
.. _getting-started-major-typo3-updates:
66
66
67
67
Major updates
68
68
-------------
69
69
70
-
In major updates you will definitely have breaking changes and incompatible API
70
+
In major updates you will definitely have **breaking changes** and incompatible API
71
71
changes.
72
72
A breaking change can cause your system to break. You need to find a replacement
73
73
for any usage that was removed or changed. For example in version 13.0 was a
@@ -89,11 +89,11 @@ Minor updates
89
89
90
90
Minor changes - `11.*.2`: For example 11.5 has new functionalities compared to
91
91
11.4. The version 11.5 is compatible with 11. So within a version like major
92
-
11 the steps do not lead to breaking changes. For example in version 13.3
92
+
11, the steps do not lead to breaking changes. For example in version 13.3
93
93
compared to version 13.2 a new
94
94
:ref:`Feature: #101252 - Introduce ErrorHandler for 403 errors with redirect option <changelog:feature-101252-1715447531>`
95
95
was introduced.
96
-
When performing minor updates you often have to clear the cache, run the Upgrade wizard and to run a database compare.
96
+
When performing minor updates, you often have to clear the cache, run the Upgrade wizard, and run a database compare.
97
97
Usually minor and patch changes are also referred to as **non-breaking** changes.
98
98
99
99
.. _getting-started-patchlevel-typo3-updates:
@@ -102,21 +102,21 @@ Patchlevel updates
102
102
------------------
103
103
104
104
Patchlevel changes - `11.5.*`: The version 11.5.2 indicates a backwards-compatible bugfix or patch release.
105
-
It can be for example a security update. Clear the cache and check if website is working as expected. For further
106
-
information we refer to the :ref:`Patch/Bugfix update guide<t3coreapi:minor>`.
105
+
It can be for example a security update. Clear the cache and check if the website is working as expected. For
106
+
further information we refer to the :ref:`Patch/Bugfix update guide<t3coreapi:minor>`.
107
107
108
108
.. _getting-started-extension-updates:
109
109
110
110
Extension updates
111
111
=================
112
112
113
-
In a TYPO3 instance you have usually third party extensions installed. When you update your TYPO3 version you
114
-
have to update the thirdparty extensions too. In the **TYPO3 Extension Repository (TER)** you can enter the name of
115
-
that extension and get information about supported TYPO3 versions. You find the TER `here <https://extensions.typo3.org/>`__.
113
+
In a TYPO3 instance you have usually third party extensions installed. When you update your TYPO3 version, you
114
+
have to update the third-party extensions too. In the **`TYPO3 Extension Repository (TER) <https://extensions.typo3.org/>`__**
115
+
you can enter the name of that extension and get information about supported TYPO3 versions.
116
116
Some extension authors prefer to only publish their extensions on `packagist <https://packagist.org/packages/typo3/>`__.
117
117
When the extension does not exist for the current TYPO3 version you can create an
118
118
issue or search for an alternative extension offering the same functionality.
119
-
For example the `gridelements extension<https://extensions.typo3.org/extension/gridelements>`__
119
+
For example, the `gridelements extension<https://extensions.typo3.org/extension/gridelements>`__
120
120
was replaced by the `container extension<https://extensions.typo3.org/extension/container>`__, both
121
121
having equal functionalities.
122
122
@@ -129,30 +129,29 @@ Deprecations
129
129
130
130
In TYPO3, deprecations indicate that a specific functionality will be removed in the next TYPO3 version. For further
131
131
information we refer to the :ref:`article about deprecation <t3coreapi:deprecation>`. For example the
132
-
:ref:`deprecation: #105171 - INCLUDE_TYPOSCRIPT TypoScript syntax <changelog:deprecation-105171-1727785626>`- notice is
133
-
a deprecation notice telling you that in TYPO3 v14 you can't use the TypoScript syntax :typoscript:`INCLUDE_TYPOSCRIPT`
134
-
to include TypoScript files anymore.
132
+
:ref:`deprecation: #105171 - INCLUDE_TYPOSCRIPT TypoScript syntax <changelog:deprecation-105171-1727785626>` - a deprecation
133
+
notice telling you that in TYPO3 v14 you can't use the TypoScript syntax :typoscript:`INCLUDE_TYPOSCRIPT` to include TypoScript files anymore.
135
134
136
135
.. _getting-started-little-helpers:
137
136
138
137
Little Helpers: Rector and Fractor
139
138
==================================
140
139
141
-
In general you can use extensions like `rector<https://github.com/sabbelasichon/typo3-rector/blob/main/README.md>`__
142
-
or `fractor<https://github.com/andreaswolf/fractor>`__ to find and replace deprecations. To reach this you have to
143
-
fill out a configuration file (in rector file :file:`rector.php`, in fractor file:file:`fractor.php`) that defines
144
-
the scope in which you want to perform deprecation replacements. For both extension is valid, only the rules that
145
-
exist can find the respective deprecation. Here is an overview about the
0 commit comments