Maintains Drupal core changes needed to run on Google App Engine. To be used with Drupal module which contains root/core.patch generated from this repository.
PHP JavaScript CSS Shell
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Failed to load latest commit information.
includes Remove drupal_http_request() changes since the google_appengine modul… Feb 26, 2014
profiles Issue #1346098 by benjy | joachim: Standard install profile sets a po… Dec 25, 2013
scripts Issue #1693398 by donquixote, pounard, sun, Sylvain Lecoy: Allow PSR-… Apr 2, 2013
sites Issue #692366 by mariacha1, hosef, Albert Volkman, xjm, underq, kid_i… Sep 12, 2013
.gitignore Issue #917492 by kvanderw, rfay, claar, Bok Choy: add a sensible .git… Apr 24, 2011
.htaccess Issue #670454 by pwolanin, cburschka, effulgentsia: Support HTTP Auth… Aug 5, 2013
INSTALL.mysql.txt Issue #1399334 by ArtistConk: Two small grammar fixes. Jan 21, 2012
README.txt Issue #1539940 by jwilson3, ryanissamson, infiniteluke, mrf: Fix up s… Oct 9, 2012
UPGRADE.txt Issue #1167996 by BWPanda: Fix version number mistake in UPGRADE.txt Jun 6, 2012
authorize.php Issue #1606946 by Albert Volkman, udaksh, bunthorne: Fix up API docs … Nov 29, 2012
cron.php Stripping CVS keywords Feb 25, 2011
install.php Issue #1606946 follow-up by David_Rothstein: Remove note about const … Dec 27, 2012
mod_rewrite.php Update wrapper.php based on version that is now part of official docu… Feb 20, 2014
update.php Issue #1504522 by rahulbile, Chi: Strict warning: Only variables shou… Dec 27, 2013
web.config Issue #1041580 by Monochrome, daycrom, dcam | RumpledElf: Fixed Favic… Aug 6, 2013



 * 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: