John Picozzi Details Drupal 11 Upgrade and Contrib Readiness Work

Staff Reporter

Upgrade preparation on John Picozzi’s long-running Drupal site centred on contributed module readiness rather than the core update itself. In a post titled Drupal 11: The Upgrade Experience I've Been Waiting For, John Picozzi describes using the Upgrade Status module to identify deprecated code, module readiness issues, and remaining blockers before upgrading from Drupal 10 to Drupal 11.

The post notes PHP 8.4 readiness for Drupal 11.3, where PHP 8.4 is the recommended version while PHP 8.3 remains supported. Contributed modules, including Cloudflare and Mailgun, had compatibility issues tracked in active Drupal.org issue queues. John also used the upgrade to move away from Drupal core’s Contact module, which Drupal.org lists for deprecation in Drupal 11.4 and removal in Drupal 12. That work involved handling an uninstall issue with the Contact Storage module.

The remaining blocker was the Juicer.io module, where John had been contributing to a Drupal 11 compatibility issue before the Juicer team released a supported Juicer module for Drupal 10 and Drupal 11. After migrating to the new module and updating Webform to 6.3.0-rc1, Upgrade Status reported full readiness. John then followed the official Drupal.org upgrade guide, updated core, ran database updates, cleared caches, and brought the site onto Drupal 11.3.

Reference: Drupal 11: The Upgrade Experience I've Been Waiting For by John Picozzi

Drupal 11

Drupal Upgrade

Drupal Core

Contributed Modules

Webform

Disclosure: This content is produced with the assistance of AI.

Disclaimer: The opinions expressed in this story do not necessarily represent that of TheDropTimes. We regularly share third-party blog posts that feature Drupal in good faith. TDT recommends Reader's discretion while consuming such content, as the veracity/authenticity of the story depends on the blogger and their motives.

Note: The vision of this web portal is to help promote news and stories around the Drupal community and promote and celebrate the people and organizations in the community. We strive to create and distribute our content based on these content policy. If you see any omission/variation on this please reach out to us at #thedroptimes channel on Drupal Slack and we will try to address the issue as best we can.