Upgrade to tether_stats 2.0.0 breaks site: Declaration of Drupal\\tether_stats\\TetherStatsIdentitySet::get(string $key, $default = null): mixed must be compatible with Symfony\\Component\\HttpFoundation\\ParameterBag::get($key, $default = null)

Created on 21 September 2023, about 1 year ago
Updated 25 September 2023, about 1 year ago

Problem/Motivation

Sites running since a few years on 1.x branch upgraded to 2.0.0 get a WSOD with the following in Apache error logs:
PHP Fatal error: Declaration of Drupal\\tether_stats\\TetherStatsIdentitySet::get(string $key, $default = null): mixed must be compatible with Symfony\\Component\\HttpFoundation\\ParameterBag::get($key, $default = null) in /webroot/web/modules/contrib/tether_stats/src/TetherStatsIdentitySet.php on line 270

Steps to reproduce

Have 1.4.0 installed.
Do a composer update.
drush updb says "No pending updates".
Both drush cr and/or drush php:eval "drupal_flush_all_caches();" performed.
Navigating to the site's root or to /user/login only gives a white screen.
No way to access the site.

Downgrading to 1.4.0 makes it work again.

symfony/http-foundation v4.4.49 (latest stable) installed.

🐛 Bug report
Status

Fixed

Version

2.0

Component

Code

Created by

🇦🇹Austria tgoeg

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @tgoeg
    • rzan committed 261d9470 on 2.x
      Issue #3388782 by rzan: Changed the Drupal version requirement due to an...
  • 🇨🇦Canada rzan

    Thank you for bringing this to my attention, tgoeg.

    It looks like an unexpected compatibility issue with Symfony 4, so I have changed the version requirement to Drupal 10 and above which runs on Symfony 6.

    Sorry for the trouble.

  • Status changed to Fixed about 1 year ago
  • 🇦🇹Austria tgoeg

    No worries, thanks for the quick fix.
    Drupal 9 is on its way out anyway, we're just not quite there, yet.
    Sorry I did not mention the Drupal version used.

    I'll close this as it is fixed for me and already pushed to 2.0.1.

  • Automatically closed - issue fixed for 2 weeks with no activity.

Production build 0.71.5 2024