Below is a quick summary of what you need to do if you are changing your Drupal site's host name / domain name without moving it to a new web hosting location.
If you are moving the site to another location, then you'll also need to see the Site Migration section for additional guides.
Forking creates a copy of a repository which you can work on. You can then submit a pull request to have your changes reviewed and integrated with the master repo. This is the order of operations:
FORK > SYNC > BRANCH > COMMIT > PUSH > PULL REQUEST
Download a PDF version of this guide.
This section is for general developer and administrator questions that commonly come up and their answers - particularly questions that don't really fit under any of the other existing topics. Please list one question per sub-page and follow the format of the first question about Drupal Sites on OIT Web Hosting Unable to Send Emails.
If not properly secured, forms can easily be used by hackers and automated "bot" programs to gain access to information within our sites, deface a site, or or even gain access to all the sites on a shared server. The following is a non-exhaustive list of tips for making any web-based form more secure.
Editor's Note: The following instructions may be out-of-date now, but are left here for future educational reference.
Below is sample code for embedding a live stream from OIT's JW Player and Wowza server onto your Georgia Tech Drupal site, and includes sample code to embed live captions, which are required for accessibility compliance. For more information, visit the test live stream site.
Courtesy of Doug Curtis in OIT:
People are receiving a 500 error when using the "GT Logout" link on a Drupal page. It looks like the problem is that the Drupal CAS module is appending the "service=" query string to the end of the CAS logout URL. The GT CAS server will accept "url=" query string but it doesn't accept the "service=" query string. Previously, the CAS service would quietly ignore appended query strings it didn't recognize but that isn't currently the case.
The GT Account Username is the standard computer account for everyone at Georgia Tech. It is used to access a variety of systems including TechWorks, BuzzPort, and Mercury, and can be used to access your Drupal site by installing the CAS module.
You may often find that need to add someone to a group in Mercury or to your Drupal site, and you need to know the person's GT Account Username. Here are several ways that you can look up that information:
Mercury provides a variety of ways to categorize and tag your content, and understanding their meanings will help you to utilize them effectively.
Georgia Tech has organized its research into core areas of special interest, and encourages you to tag News items with these areas in Mercury. These research area tags are used to help find stories:
CAS is capable of delivering some GTED attributes for the person logging in to Drupal, as part of the login process. This means you don't have to configure and maintain an LDAP module nor manage an LDAP service account (read: no need to keep up with an expiring service account password).
Note: If you are running in a shared hosting environment, like OIT Web Hosting, then you are not likely to get many if any general permission errors, as each website runs under its own hosting account in these environments. Thus, it is nearly impossible to mess up file and directory ownership in these environments. However, it is worth checking the file and directory permissions, as they are often changeable, and if the owner-write permission is removed from a file or directory then the web server will not be able to modify that f
