Pantheon Pressflow 7 for DROPs
Switch branches/tags
Clone or download
Failed to load latest commit information.
.circleci CircleCI 2.0 tests. Oct 18, 2018
includes Drupal 7.60 Oct 18, 2018
misc Updated db.check.php healthcheck to be PHP7-compatible. Oct 18, 2018
modules SA-CORE-2018-006 by alexpott, attilatilman, bkosborne, catch, bonus, … Oct 18, 2018
profiles Update to Drupal 7.40. For more information, see https://www.drupal.o… Oct 15, 2015
scripts Issue #2660766 by David_Rothstein, twistor: UpgradePathTaxonomyTestCa… Jul 3, 2016
sites Update to Drupal 7.51. For more information, see https://www.drupal.o… Oct 6, 2016
themes Revert "Issue #578400 by tbradbury, therealssj, joshi.rohit100, aaron… Oct 2, 2016
.drush-lock-update Add a .drush-lock-update file to tell folks not to update Pantheon Dr… Mar 25, 2015
.editorconfig Issue #1713662 by nod_, Eric_A, treyhunner, sun, basvredeling: Introd… Jul 1, 2016
.gitignore Update to PHP 5.6. For more information about PHP versions, see https… Jun 29, 2017
.htaccess Issue #1599774 by longwave, ben.bunk, Rob C, stefan.r, David_Rothstei… Jun 6, 2017
CHANGELOG.txt Drupal 7.60 Oct 18, 2018
COPYRIGHT.txt Issue #2078101 by Xano: Update cpyright date Sep 12, 2013
INSTALL.mysql.txt Issue #1969108 by danblack, cs_shadow | Robert S: INSTALL.mysql.txt d… May 5, 2014
INSTALL.pgsql.txt Stripping CVS keywords Feb 25, 2011
INSTALL.sqlite.txt Stripping CVS keywords Feb 25, 2011
INSTALL.txt Issue #2583743 by jcnventura: Correct required version of SQLite in I… Oct 14, 2015
LICENSE.txt Stripping CVS keywords Feb 25, 2011
MAINTAINERS.txt Issue #2794547: Remove xjm from MAINTAINERS.txt in D7 Sep 5, 2016
README.txt Issue #2181809 by davidneedham, Les Lim: Fix bullet list in README file Feb 27, 2014
UPGRADE.txt Issue #2516842 by er.pushpinderrana, thejacer87, jhodgdon: UPGRADE.tx… Oct 14, 2015
authorize.php Issue #1606946 by Albert Volkman, udaksh, bunthorne: Fix up API docs … Nov 29, 2012
cron.php Stripping CVS keywords Feb 25, 2011
index.php Stripping CVS keywords Feb 25, 2011
install.php Issue #1606946 follow-up by David_Rothstein: Remove note about const … Dec 27, 2012
pantheon.upstream.yml Update to PHP 7.1. For details see… Aug 15, 2018
robots.txt Issue #2364343 by damien_vancouver, criz, ksenzee, Neograph734, joegr… Jul 2, 2016
update.php Issue #1504522 by rahulbile, Chi: Strict warning: Only variables shou… Dec 27, 2013
web.config Issue #2392153 by mparker17, hussainweb, chris.smith, alexpott, daweh… Feb 1, 2016
xmlrpc.php Stripping CVS keywords Feb 25, 2011



 * About Drupal
 * Configuration and features
 * Installation profiles
 * Appearance
 * Developing for Drupal


Drupal is an open source content management platform supporting a variety of
websites ranging from personal weblogs to large community-driven websites. For
more information, see the Drupal website at, and join the
Drupal community at

Legal information about Drupal:
 * Know your rights when using Drupal:
   See LICENSE.txt in the same directory as this document.
 * Learn about the Drupal trademark and logo policy:


Drupal core (what you get when you download and extract a drupal-x.y.tar.gz or file from has what you need to
get started with your website. It includes several modules (extensions that add
functionality) for common website features, such as managing content, user
accounts, image uploading, and search. Core comes with many options that allow
site-specific configuration. In addition to the core modules, there are
thousands of contributed modules (for functionality not included with Drupal
core) available for download.

More about configuration:
 * Install, upgrade, and maintain Drupal:
   See INSTALL.txt and UPGRADE.txt in the same directory as this document.
 * Learn about how to use Drupal to create your site:
 * Download contributed modules to sites/all/modules to extend Drupal's
 * See also: "Developing for Drupal" for writing your own modules, below.


Installation profiles define additional steps (such as enabling modules,
defining content types, etc.) that run after the base installation provided
by core when Drupal is first installed. There are two basic installation
profiles provided with Drupal core.

Installation profiles from the Drupal community modify the installation process
to provide a website for a specific use case, such as a CMS for media
publishers, a web-based project tracking tool, or a full-fledged CRM for
non-profit organizations raising money and accepting donations. They can be
distributed as bare installation profiles or as "distributions". Distributions
include Drupal core, the installation profile, and all other required
extensions, such as contributed and custom modules, themes, and third-party
libraries. Bare installation profiles require you to download Drupal Core and
the required extensions separately; place the downloaded profile in the
/profiles directory before you start the installation process. Note that the
contents of this directory may be overwritten during updates of Drupal core;
it is advised to keep code backups or use a version control system.

Additionally, modules and themes may be placed inside subdirectories in a
specific installation profile such as profiles/your_site_profile/modules and
profiles/your_site_profile/themes respectively to restrict their usage to only
sites that were installed with that specific profile.

More about installation profiles and distributions:
 * Read about the difference between installation profiles and distributions:
 * Download contributed installation profiles and distributions:
 * Develop your own installation profile or distribution:


In Drupal, the appearance of your site is set by the theme (themes are
extensions that set fonts, colors, and layout). Drupal core comes with several
themes. More themes are available for download, and you can also create your own
custom theme.

More about themes:
 * Download contributed themes to sites/all/themes to modify Drupal's
 * Develop your own theme:


Drupal contains an extensive API that allows you to add to and modify the
functionality of your site. The API consists of "hooks", which allow modules to
react to system events and customize Drupal's behavior, and functions that
standardize common operations such as database queries and form generation. The
flexible hook architecture means that you should never need to directly modify
the files that come with Drupal core to achieve the functionality you want;
instead, functionality modifications take the form of modules.

When you need new functionality for your Drupal site, search for existing
contributed modules. If you find a module that matches except for a bug or an
additional needed feature, change the module and contribute your improvements
back to the project in the form of a "patch". Create new custom modules only
when nothing existing comes close to what you need.

More about developing:
 * Search for existing contributed modules:
 * Contribute a patch:
 * Develop your own module:
 * Follow best practices:
 * Refer to the API documentation: