Drupal Module Status Chart

The following table, initially provided by the College of Computing (many thanks!) attempts to summarize the details of a large number of commonly used Drupal 7 modules and any known issues with their latest full (not development) version under PHP 7. In addition, Kevin Pittman of the College of Liberal Arts has added Drupal 8 compatibility details and removal recommendations, to help site administrators decide what to do as they review the modules installed their Drupal 7 sites.

PHP 7 Upgrading Resources

PHP 5.6 (the last version in the PHP 5 line) reaches end-of-life on December 31, 2018. OIT is requiring everyone to be off of PHP 5.6 by December 17, 2018, and will be moving all web hosting sites to PHP 7.1 by the close of business on Tuesday, November 6, 2018. If you run into problems, you can request to move back to PHP 5.6, but you will be forced back to PHP 7.1 on December 17th.

Formatting breaks on Slideshow Carousel, SuperBlocks or other Content Types after 2.9 Theme upgrade


After updating to the 2.9 version of the GT Theme, the formatting is broken for custom content types (such as Super Blocks and Slideshow Carousels), usually those created via the Features module. Often the types show CSS classes as text instead of as visual styling.

Example of broken Super Blocks

super blocks showing css classes as text instead of styling

Upgrading Drupal 7 to 8

Migration, not Upgrading

Drupal 8, released in November of 2015, is a major rewrite of the Drupal core engine and APIs. Because Drupal 8 has changed so much, there is no direct in-place upgrade path to go from any earlier version of Drupal to Drupal 8. Instead, Drupal 7 and earlier sites must be migrated to Drupal 8, which involves setting up a whole new Drupal 8 website and copying into it (manually or automatically) the content of the older website.