- Issue created by @project update bot
This is an automated patch generated using Upgrade Status and Drupal Rector. Please see the issue summary for more details. A merge request (MR) is also openend and updated.
It is important that any automated tests available are run and that you manually test the changes.
Drupal 11 Compatibility
According to the Upgrade Status module → these changes make this module compatible with Drupal 11! 🎉
Therefore these changes update theinfo.yml
file for Drupal 11 compatibility.Leaving this issue open, even after committing the current patch or merging the MR, will allow the Project Update Bot → to post additional Drupal 11 compatibility fixes as they become available in Drupal Rector.
Debug information
Bot run #11-127659These packages were used to generate the fixes:
- drupal/upgrade_status: 4.1.0
- mglaman/phpstan-drupal: 1.2.9
- palantirnet/drupal-rector: 0.20.1
- First commit to issue fork.
-
andileco →
committed 8c0e8cf2 on 1.0.x authored by
Project Update Bot →
Issue #3435549 by Project Update Bot: Automated Drupal 11 compatibility...
-
andileco →
committed 8c0e8cf2 on 1.0.x authored by
Project Update Bot →
- Status changed to Active
over 1 year ago 2:52am 2 April 2024 - 🇫🇷France jmary
After upgrade to d11 on a staging site, here is a patch correcting the error:
2025/09/09 09:28:07 [error] 201890#201890: *31 FastCGI sent in stderr: "PHP message: PHP Fatal error: Type of Drupal\views_timestamp_to_date\Plugin\views\field\TimestampToDate::$time must be Drupal\Component\Datetime\TimeInterface (as in class Drupal\views\Plugin\views\field\Date) in /var/www/*************/drupal/web/modules/contrib/views_timestamp_to_date/src/Plugin/views/field/TimestampToDate.php on line 20" while reading response header from upstream, client: 10.98.231.6, server: ******************, request: "GET / HTTP/2.0", upstream: "fastcgi://unix:/run/php/php8.4-fpm.sock:", host: "****************", referrer: "https://***************/admin/reports/updates"