Per Kevin Pittman's insight posted on the GTDUG Team:
With Drupal 7.61, be aware that you're now likely to see a bunch of "SimpleXMLElement" errors on the Modules Update screen. This is caused whenever a module's project status data can't be retrieved.
There are two cases that will have to be addressed:
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 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.
To use the CAS PEM certificate installed on websites hosted on OIT webhosting, please use the following path:
/etc/pki/tls/certs/ca-bundle.crt
Certain fields likely need additional explanatory text accompanying it.
Per Georgia Tech's accessibility requirements, any publicly-available video must be captioned for end-users. YouTube's automatic captions are not enough to meet full guidance. Please see the Video Captioning and Audio Transcripts for more information.
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.
Kevin Pittman has written a blog post called "So, You Blew Up Your Drupal 8 Site - Now What?" that covers multiple methods for recovering a dead Drupal 8 website (on the assumption you hadn't made a backup right before it died).
Drupal 8 has a much more sophisticated and ultimately aggressive caching system. While this is supposed to be a good change, sometimes it really gets in your way.
Kevin Pittman has written an blog post on Drupal 8 Internal Caching for Dummies that helps clarify the different types of caching that occur and how to configure them to work to your advantage.
Many Georgia Tech websites have been built using Drupal Express (DX), which is a custom version of Drupal 7 that allows you to create a website with little technical or design expertise. The ready-made site comes with built in features and tools like news and events listings, and mobile optimization.
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.