Skip to content
Snippets Groups Projects
Commit 353887d7 authored by Stephan Großberndt's avatar Stephan Großberndt Committed by Christian Kuhn
Browse files

[BUGFIX] Typos and wording issues in master documentation

Resolves: #78442
Releases: master
Change-Id: Ic081062296aad1353b80633b8f5a074ea0586d7f
Reviewed-on: https://review.typo3.org/50379


Tested-by: default avatarTYPO3com <no-reply@typo3.com>
Reviewed-by: default avatarMichael Oehlhof <typo3@oehlhof.de>
Tested-by: default avatarMichael Oehlhof <typo3@oehlhof.de>
Reviewed-by: default avatarChristian Kuhn <lolli@schwarzbu.ch>
Tested-by: default avatarChristian Kuhn <lolli@schwarzbu.ch>
parent 7fe55fc4
Branches
Tags
No related merge requests found
Showing
with 24 additions and 22 deletions
......@@ -30,7 +30,7 @@ provides test "TCA ext_tables check" to find such extensions.
Migration
=========
Neither direct write to `$GLOBALS['TCA']` and `$TCA` is allowed, nor indirect write
In :file:`ext_tables.php` neither direct write to `$GLOBALS['TCA']` and `$TCA` is allowed, nor indirect write
via `ExtensionManagementUtility` methods. An example list of calls and their new positions:
* `$GLOBALS['TCA`]['someTable'] = `: A full table `TCA` is added. This must be moved
......@@ -52,4 +52,4 @@ via `ExtensionManagementUtility` methods. An example list of calls and their new
is added to the `tt_content` table. Add this to `Configuration/TCA/Overrides/tt_content.php`.
.. index:: Frontend, TCA
\ No newline at end of file
.. index:: Frontend, TCA
......@@ -9,8 +9,8 @@ See :issue:`78417`
Description
===========
The DeletedRecordsCommand is now using Symfony Console. The new command which behaves like the old code, but uses certain
different parameters and is located under the following path now:
The DeletedRecordsCommand is now using Symfony Console. The new command behaves like the old one, but allows using certain
parameters and is located under the following path now:
`./typo3/sysext/core/bin/typo3 cleanup:deletedrecords`
......@@ -22,6 +22,7 @@ The following options can be set
The PHP class `TYPO3\CMS\Lowlevel\DeletedRecordsCommand` has been removed.
Impact
======
......@@ -33,7 +34,7 @@ Calling the PHP class results in a fatal PHP error.
Affected Installations
======================
Any TYPO3 installation using the previously functioned command or the related PHP class.
Any TYPO3 installation using the old CLI command or the related PHP class.
Migration
......
......@@ -9,7 +9,7 @@ See :issue:`57385`
Description
===========
The argument :php:`$caseSensitive` of the method :php:`Query::like` has been deprecated:
The argument :php:`$caseSensitive` of the method :php:`Query::like` has been marked as deprecated.
Impact
......
......@@ -15,21 +15,21 @@ The public member parentMenuArr has been added as public member and marked as de
Impact
======
The parentMenuArr will be publicly accessible until it is changed to protected in TYPO3 CMS 9.
The parentMenuArr will be publicly accessible until it is changed to protected in TYPO3 v9.
Affected Installations
======================
Instances that have menues with sublevels and using this member in the itemArrayProcFunc.
Instances that have menus with sublevels and using this member in the itemArrayProcFunc.
Migration
=========
Use the provided api function :php:`getParentMenuArr()` to get the parentMenuArr instead.
Use the provided API function :php:`getParentMenuArr()` to get the parentMenuArr instead.
This method always returns an array.
If you need the direct parent menuitem of the current sublevel use :php:`getParentMenuItem()` method.
.. index:: Frontend
\ No newline at end of file
.. index:: Frontend
......@@ -15,13 +15,13 @@ The TypoScript setting `config.noScaleUp` has been marked as deprecated.
Impact
======
Using this setting `config.noScaleUp` will trigger a deprecation log entry. It will work, until it get's removed in TYPO3 CMS 9.
Using this setting `config.noScaleUp` will trigger a deprecation log entry. It will work until it get's removed in TYPO3 v9.
Affected Installations
======================
Instances that use this Typoscript setting.
Instances that use this TypoScript setting.
Migration
......
......@@ -9,13 +9,13 @@ See :issue:`78279`
Description
===========
The property :js:`top.TYPO3.Backend.ContentContainer.iframe` has been deprecated.
The property :js:`top.TYPO3.Backend.ContentContainer.iframe` has been marked as deprecated.
Impact
======
Usage of this property will stop work with TYPO3 v9
Using this property will stop working in TYPO3 v9.
Affected Installations
......
......@@ -9,14 +9,15 @@ See :issue:`76085`
Description
===========
A new setting in the admin panel (Preview > Show fluid debug output) enable fluid debug output.
A new setting in the admin panel (Preview > Show fluid debug output) enables showing fluid debug output.
If the checkbox is enabled, the path to the template file of a partial and the name of a section will be shown in the
frontend directly above the markup.
With this feature an integrator can easily find the correct template and section.
Impact
======
Activating this option can break the output in frontend or result in unexpected behavior.
.. index:: Frontend
\ No newline at end of file
.. index:: Frontend
......@@ -9,13 +9,13 @@ See :issue:`78384`
Description
===========
The install tool has a new feature to check extensions for :file:`ext_tables.php` files that still change `TCA`.
The install tool has a new feature to check extensions for :file:`ext_tables.php` files that still change the global `TCA` array.
Impact
======
Changing `TCA` in :file:`ext_tables.php` is not allowed and can lead to failed or incomplete frontend requests.
Changing the global `TCA` array in :file:`ext_tables.php` is not allowed and can lead to failing or incomplete frontend requests.
The feature helps to find affected, loaded extensions.
.. index:: TCA, ext:install
\ No newline at end of file
.. index:: TCA, ext:install
......@@ -10,8 +10,8 @@ Description
===========
By storing Fluid's namespaces in $GLOBALS['TYPO3_CONF_VARS']['SYS']['fluid']['namespaces'] we can allow adding or
extending the global namespaces from third party packages in for example ext_localconf.php, or by simply specifying
the namespace arrays in LocalConfiguration.php.
extending the global namespaces from third party packages in for example :file:`ext_localconf.php` or by simply specifying
the namespace arrays in :file:`LocalConfiguration.php`.
In terms of performance there is nearly zero impact but in terms of flexibility this should provide the ultimate way
to manage global namespaces as configuration; something that currently is only possible by implementing custom
......@@ -27,4 +27,4 @@ Impact
* Template developers can use such global namespaces without first importing them and can use them
in all Fluid templates regardless of context.
.. index:: Fluid, LocalConfiguration
\ No newline at end of file
.. index:: Fluid, LocalConfiguration
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment