[TASK] Add v10.2 deprecations and important info

TYPO3-Documentation · Dec 2, 2019 · 6ad75dc · 6ad75dc
1 parent 8547273
commit 6ad75dc
Show file tree

Hide file tree

Showing 8 changed files with 10 additions and 44 deletions.
diff --git a/Documentation/ApiOverview/Bootstrapping/Index.rst b/Documentation/ApiOverview/Bootstrapping/Index.rst
@@ -286,7 +286,7 @@ In file :file:`typo3conf/AdditionalConfiguration.php`:
 
 .. code-block:: php
 
-   switch (\TYPO3\CMS\Core\Utility\GeneralUtility::getApplicationContext()) {
+   switch (\TYPO3\CMS\Core\Core\Environment::getContext()) {
       case 'Development':
          $GLOBALS['TYPO3_CONF_VARS']['SYS']['displayErrors'] = 1;
          $GLOBALS['TYPO3_CONF_VARS']['SYS']['devIPmask'] = '*';

diff --git a/Documentation/ApiOverview/Database/QueryBuilder/Index.rst b/Documentation/ApiOverview/Database/QueryBuilder/Index.rst
@@ -681,7 +681,9 @@ Remarks:
 * `doctrine-dbal` always creates prepared statements: Any value that is added via :php:`->createNamedParameter()` creates
   a placeholder that is later substituted when the real query is fired via :php:`->execute()`. :php:`->getSQL()` does not show
   those values, instead the placeholder names are displayed, usually with a string like `:dcValue1`. There is no
-  simple solution to show the fully replaced query from within the framework, but you can go for :php:`->getParameters()` to see the array of parameters used to replace these placeholders within the query.
+  simple solution to show the fully replaced query from within the framework, but you can go for :php:`->getParameters()` to see the 
+  array of parameters used to replace these placeholders within the query. In the frontend, the queries and parameters are shown 
+  in the admin panel.
 
 
 getParameters()

diff --git a/Documentation/ApiOverview/Database/Statement/Index.rst b/Documentation/ApiOverview/Database/Statement/Index.rst
@@ -111,8 +111,7 @@ Re-use Prepared Statement()
 ===========================
 
 Doctrine usually prepares a statement first, and then executes it with given parameters. Implementing
-prepared statements depends on the given driver. For instance, the native mysql driver `mysqli` does implement
-prepared statements, while the pdo driver of mysql `pdo_mysql` does not, at least in some scenarios. A driver
+prepared statements depends on the given driver. A driver
 not properly implementing prepared statements fall back to a direct execution of given query.
 
 There is an API to make real use of prepared statements that becomes handy if the same query is executed

diff --git a/Documentation/ApiOverview/ErrorAndExceptionHandling/Configuration/Index.rst b/Documentation/ApiOverview/ErrorAndExceptionHandling/Configuration/Index.rst
@@ -124,19 +124,6 @@ part of :php:`$GLOBALS['TYPO3_CONF_VARS'][SYS]`:
             if :php:`$GLOBALS['TYPO3_CONF_VARS']['SYS']['displayErrors']` is "-1" or "2" and
             the :php:`$GLOBALS['TYPO3_CONF_VARS']['SYS']['devIPmask']` matches.
 
-
- - :Key:
-         syslogErrorReporting
-   :Data type:
-         integer
-   :Description:
-         Configures which PHP errors should be logged to the configured syslogs
-         (see: [SYS][systemLog]). If set to "0" no PHP errors are logged to the
-         syslog.
-
-         Default: :php:`E_ALL ^ E_NOTICE` (6135).
-
-
  - :Key:
          belogErrorReporting
    :Data type:
@@ -149,13 +136,6 @@ part of :php:`$GLOBALS['TYPO3_CONF_VARS'][SYS]`:
          Default: :php:`E_ALL ^ E_NOTICE` (6135).
 
 
- - :Key:
-         systemLog
-   :Data type:
-         boolean
-   :Description:
-         Configures whether logging is enabled. Logging itself can be
-         configured in detail via the :ref:`Logging Framework <logging>`.
 
 
 The table below shows which values can be set by the user and which

diff --git a/Documentation/ApiOverview/ErrorAndExceptionHandling/Examples/Index.rst b/Documentation/ApiOverview/ErrorAndExceptionHandling/Examples/Index.rst
@@ -34,8 +34,6 @@ In :file:`LocalConfiguration.php`::
       'exceptionalErrors' => E_ALL ^ E_NOTICE ^ E_WARNING ^ E_USER_ERROR ^ E_USER_NOTICE ^ E_USER_WARNING,
       'debugExceptionHandler' => 'TYPO3\\CMS\\Core\\Error\\DebugExceptionHandler',
       'productionExceptionHandler' => 'TYPO3\\CMS\\Core\\Error\\DebugExceptionHandler',
-      'systemLogLevel' => '0',
-      'systemLog' => true,
    ),
 
 You can also use the "Debug" preset in the Settings module "Configuration presets". 
@@ -84,8 +82,6 @@ In :file:`LocalConfiguration.php`::
       'displayErrors' => '2',
       'devIPmask' => '[your.IP.address]',
       'errorHandler' => 'TYPO3\\CMS\\Core\\Error\\ErrorHandler',
-      'systemLogLevel' => '2',
-      'systemLog' => true,
       'syslogErrorReporting' => E_ALL ^ E_NOTICE ^ E_WARNING,
       'belogErrorReporting' => '0',
    ),
@@ -117,7 +113,6 @@ In :file:`LocalConfiguration.php`::
       'errorHandler' => '',
       'debugExceptionHandler' => '',
       'productionExceptionHandler' => '',
-      'systemLog' => false,
       'syslogErrorReporting' => '0',
       'belogErrorReporting' => '0',
    ),

diff --git a/Documentation/ApiOverview/GlobalValues/Typo3ConfVars/Index.rst b/Documentation/ApiOverview/GlobalValues/Typo3ConfVars/Index.rst
@@ -101,7 +101,6 @@ A typical content of :file:`typo3conf/LocalConfiguration.php` looks like this:
          'encryptionKey' => '0396e1b6b53bf48b0bfed9e97a62744158452dfb9b9909fe32d4b7a709816c9b4e94dcd69c011f989d322cb22309f2f2',
          'exceptionalErrors' => 28674,
          'sitename' => 'New TYPO3 site',
-         'systemLogLevel' => 0,
       ],
    ];
 

diff --git a/Documentation/ApiOverview/Services/UsingServices/ServiceChain.rst b/Documentation/ApiOverview/Services/UsingServices/ServiceChain.rst
@@ -36,15 +36,12 @@ The following example is an extract of the user authentication process::
 
    protected function getAuthServices(string $subType, array $loginData, array $authInfo): \Traversable
    {
-      $serviceChain = '';
+      $serviceChain = [];
       while (is_object($serviceObj = GeneralUtility::makeInstanceService('auth', $subType, $serviceChain))) {
          $serviceChain .= ',' . $serviceObj->getServiceKey();
          $serviceObj->initAuth($subType, $loginData, $authInfo, $this);
          yield $serviceObj;
       }
-      if ($serviceChain) {
-         $this->logger->debug($subType . ' auth services called: ' . $serviceChain);
-      }
    }
 
 

diff --git a/Documentation/ApiOverview/SystemLog/Index.rst b/Documentation/ApiOverview/SystemLog/Index.rst
@@ -1,22 +1,16 @@
 .. include:: ../../Includes.txt
 
-
-
-
-
-
 .. _syslog:
 
 ========================
 System Log
 ========================
 
-.. note::
-
-   A :ref:`new logging API <logging>` was introduced in TYPO3 CMS 6.0. It is far more flexible than the old
-   one described here, but is not yet in use in the Core. Thus this section remains valid
-   if you want to write to the "sys_log" table. Otherwise please consider using the new API.
+.. warning::
 
+   A :ref:`new logging API <logging>` was introduced in TYPO3 CMS 6.0. It should be used by extension 
+   authors starting with TYPO3 v9 LTS. The following section is here as legacy reference,
+   but should not be used in installations with TYPO3 >= 9.
 
 Writing to the system log is done using the backend user object,
 which writes to the "sys_log" table::