Issue #3410210 by quietone, sourabhjain, smustgrave, Spokje, catch: Remove...

Issue #3410210 by quietone, sourabhjain, smustgrave, Spokje, catch: Remove statistics module from comments

autoload.php

@@ -8,7 +8,6 @@
  * @see index.php
  * @see core/install.php
  * @see core/rebuild.php
- * @see core/modules/statistics/statistics.php
  */
 
 return require __DIR__ . '/vendor/autoload.php';

composer/Plugin/Scaffold/GenerateAutoloadReferenceFile.php

@@ -113,7 +113,6 @@ protected static function autoLoadContents($relative_autoload_path) {
  * @see index.php
  * @see core/install.php
  * @see core/rebuild.php
- * @see core/modules/statistics/statistics.php
  */
 
 return require __DIR__ . '/{$relative_autoload_path}';

core/assets/scaffold/files/default.settings.php

@@ -355,14 +355,13 @@
  * security, or encryption benefits. In an environment where Drupal
  * is behind a reverse proxy, the real IP address of the client should
  * be determined such that the correct client IP address is available
- * to Drupal's logging, statistics, and access management systems. In
- * the most simple scenario, the proxy server will add an
- * X-Forwarded-For header to the request that contains the client IP
- * address. However, HTTP headers are vulnerable to spoofing, where a
- * malicious client could bypass restrictions by setting the
- * X-Forwarded-For header directly. Therefore, Drupal's proxy
- * configuration requires the IP addresses of all remote proxies to be
- * specified in $settings['reverse_proxy_addresses'] to work correctly.
+ * to Drupal's logging and access management systems. In the most simple
+ * scenario, the proxy server will add an X-Forwarded-For header to the request
+ * that contains the client IP address. However, HTTP headers are vulnerable to
+ * spoofing, where a malicious client could bypass restrictions by setting the
+ * X-Forwarded-For header directly. Therefore, Drupal's proxy configuration
+ * requires the IP addresses of all remote proxies to be specified in
+ * $settings['reverse_proxy_addresses'] to work correctly.
  *
  * Enable this setting to get Drupal to determine the client IP from the
  * X-Forwarded-For header. If you are unsure about this setting, do not have a

core/lib/Drupal/Core/Render/Element/Link.php

@@ -136,13 +136,6 @@ public static function preRenderLink($element) {
    *       // passing in to links.html.twig.
    *     ),
    *   ),
-   *   'statistics' => array(
-   *     '#theme' => 'links__node__statistics',
-   *     '#links' => array(
-   *       // An array of links associated with node statistics, suitable for
-   *       // passing in to links.html.twig.
-   *     ),
-   *   ),
    *   'translation' => array(
    *     '#theme' => 'links__node__translation',
    *     '#links' => array(

core/modules/tracker/help_topics/tracker.tracking_changed_content.html.twig

@@ -2,7 +2,6 @@
 label: 'Viewing lists of recently-updated content'
 related:
   - core.tracking_content
-  - statistics.tracking_popular_content
   - history.tracking_user_content
 ---
 {% set recent_link_text %}

sites/default/default.settings.php

@@ -355,14 +355,13 @@
  * security, or encryption benefits. In an environment where Drupal
  * is behind a reverse proxy, the real IP address of the client should
  * be determined such that the correct client IP address is available
- * to Drupal's logging, statistics, and access management systems. In
- * the most simple scenario, the proxy server will add an
- * X-Forwarded-For header to the request that contains the client IP
- * address. However, HTTP headers are vulnerable to spoofing, where a
- * malicious client could bypass restrictions by setting the
- * X-Forwarded-For header directly. Therefore, Drupal's proxy
- * configuration requires the IP addresses of all remote proxies to be
- * specified in $settings['reverse_proxy_addresses'] to work correctly.
+ * to Drupal's logging and access management systems. In the most simple
+ * scenario, the proxy server will add an X-Forwarded-For header to the request
+ * that contains the client IP address. However, HTTP headers are vulnerable to
+ * spoofing, where a malicious client could bypass restrictions by setting the
+ * X-Forwarded-For header directly. Therefore, Drupal's proxy configuration
+ * requires the IP addresses of all remote proxies to be specified in
+ * $settings['reverse_proxy_addresses'] to work correctly.
  *
  * Enable this setting to get Drupal to determine the client IP from the
  * X-Forwarded-For header. If you are unsure about this setting, do not have a