Browse Source

import from SVN/unfuddle.

tags/intro_KPN
Bèr Kessels 12 years ago
commit
36b9b0794e
100 changed files with 31205 additions and 0 deletions
  1. 113
    0
      .htaccess
  2. 970
    0
      CHANGELOG.txt
  3. 25
    0
      COPYRIGHT.txt
  4. 40
    0
      INSTALL.mysql.txt
  5. 28
    0
      INSTALL.pgsql.txt
  6. 350
    0
      INSTALL.txt
  7. 340
    0
      LICENSE.txt
  8. 86
    0
      MAINTAINERS.txt
  9. 110
    0
      UPGRADE.txt
  10. 11
    0
      cron.php
  11. 367
    0
      includes/actions.inc
  12. 354
    0
      includes/batch.inc
  13. 1201
    0
      includes/bootstrap.inc
  14. 24
    0
      includes/cache-install.inc
  15. 183
    0
      includes/cache.inc
  16. 3677
    0
      includes/common.inc
  17. 587
    0
      includes/database.inc
  18. 533
    0
      includes/database.mysql-common.inc
  19. 371
    0
      includes/database.mysql.inc
  20. 374
    0
      includes/database.mysqli.inc
  21. 931
    0
      includes/database.pgsql.inc
  22. 1358
    0
      includes/file.inc
  23. 2547
    0
      includes/form.inc
  24. 221
    0
      includes/image.gd.inc
  25. 270
    0
      includes/image.inc
  26. 737
    0
      includes/install.inc
  27. 117
    0
      includes/install.mysql.inc
  28. 112
    0
      includes/install.mysqli.inc
  29. 140
    0
      includes/install.pgsql.inc
  30. 144
    0
      includes/language.inc
  31. 2633
    0
      includes/locale.inc
  32. 481
    0
      includes/mail.inc
  33. 2512
    0
      includes/menu.inc
  34. 492
    0
      includes/module.inc
  35. 434
    0
      includes/pager.inc
  36. 243
    0
      includes/path.inc
  37. 171
    0
      includes/session.inc
  38. 200
    0
      includes/tablesort.inc
  39. 1982
    0
      includes/theme.inc
  40. 288
    0
      includes/theme.maintenance.inc
  41. 542
    0
      includes/unicode.inc
  42. 487
    0
      includes/xmlrpc.inc
  43. 313
    0
      includes/xmlrpcs.inc
  44. 39
    0
      index.php
  45. 1174
    0
      install.php
  46. 225
    0
      misc/ahah.js
  47. BIN
      misc/arrow-asc.png
  48. BIN
      misc/arrow-desc.png
  49. 298
    0
      misc/autocomplete.js
  50. 38
    0
      misc/batch.js
  51. BIN
      misc/blog.png
  52. 77
    0
      misc/collapse.js
  53. BIN
      misc/draggable.png
  54. 296
    0
      misc/drupal.js
  55. BIN
      misc/druplicon.png
  56. 35
    0
      misc/farbtastic/farbtastic.css
  57. 315
    0
      misc/farbtastic/farbtastic.js
  58. BIN
      misc/farbtastic/marker.png
  59. BIN
      misc/farbtastic/mask.png
  60. BIN
      misc/farbtastic/wheel.png
  61. BIN
      misc/favicon.ico
  62. BIN
      misc/feed.png
  63. 10
    0
      misc/form.js
  64. BIN
      misc/forum-closed.png
  65. BIN
      misc/forum-default.png
  66. BIN
      misc/forum-hot-new.png
  67. BIN
      misc/forum-hot.png
  68. BIN
      misc/forum-new.png
  69. BIN
      misc/forum-sticky.png
  70. BIN
      misc/grippie.png
  71. 13
    0
      misc/jquery.form.js
  72. 13
    0
      misc/jquery.js
  73. BIN
      misc/menu-collapsed-rtl.png
  74. BIN
      misc/menu-collapsed.png
  75. BIN
      misc/menu-expanded.png
  76. BIN
      misc/menu-leaf.png
  77. BIN
      misc/powered-black-135x42.png
  78. BIN
      misc/powered-black-80x15.png
  79. BIN
      misc/powered-black-88x31.png
  80. BIN
      misc/powered-blue-135x42.png
  81. BIN
      misc/powered-blue-80x15.png
  82. BIN
      misc/powered-blue-88x31.png
  83. BIN
      misc/powered-gray-135x42.png
  84. BIN
      misc/powered-gray-80x15.png
  85. BIN
      misc/powered-gray-88x31.png
  86. 8
    0
      misc/print-rtl.css
  87. 26
    0
      misc/print.css
  88. BIN
      misc/progress.gif
  89. 107
    0
      misc/progress.js
  90. 1096
    0
      misc/tabledrag.js
  91. 117
    0
      misc/tableheader.js
  92. 87
    0
      misc/tableselect.js
  93. 96
    0
      misc/teaser.js
  94. 36
    0
      misc/textarea.js
  95. BIN
      misc/throbber.gif
  96. BIN
      misc/tree-bottom.png
  97. BIN
      misc/tree.png
  98. BIN
      misc/watchdog-error.png
  99. BIN
      misc/watchdog-ok.png
  100. 0
    0
      misc/watchdog-warning.png

+ 113
- 0
.htaccess View File

@@ -0,0 +1,113 @@
#
# Apache/PHP/Drupal settings:
#

# Protect files and directories from prying eyes.
<FilesMatch "\.(engine|inc|info|install|module|profile|test|po|sh|.*sql|theme|tpl(\.php)?|xtmpl|svn-base)$|^(code-style\.pl|Entries.*|Repository|Root|Tag|Template|all-wcprops|entries|format)$">
Order allow,deny
</FilesMatch>

# Don't show directory listings for URLs which map to a directory.
Options -Indexes

# Follow symbolic links in this directory.
Options +FollowSymLinks

# Make Drupal handle any 404 errors.
ErrorDocument 404 /index.php

# Custom php memory limit
php_value memory_limit 32M

# Force simple error message for requests for non-existent favicon.ico.
<Files favicon.ico>
# There is no end quote below, for compatibility with Apache 1.3.
ErrorDocument 404 "The requested file favicon.ico was not found.
</Files>

# Set the default handler.
DirectoryIndex index.php

# Override PHP settings. More in sites/default/settings.php
# but the following cannot be changed at runtime.

# PHP 4, Apache 1.
<IfModule mod_php4.c>
php_value magic_quotes_gpc 0
php_value register_globals 0
php_value session.auto_start 0
php_value mbstring.http_input pass
php_value mbstring.http_output pass
php_value mbstring.encoding_translation 0
</IfModule>

# PHP 4, Apache 2.
<IfModule sapi_apache2.c>
php_value magic_quotes_gpc 0
php_value register_globals 0
php_value session.auto_start 0
php_value mbstring.http_input pass
php_value mbstring.http_output pass
php_value mbstring.encoding_translation 0
</IfModule>

# PHP 5, Apache 1 and 2.
<IfModule mod_php5.c>
php_value magic_quotes_gpc 0
php_value register_globals 0
php_value session.auto_start 0
php_value mbstring.http_input pass
php_value mbstring.http_output pass
php_value mbstring.encoding_translation 0
</IfModule>

# Requires mod_expires to be enabled.
<IfModule mod_expires.c>
# Enable expirations.
ExpiresActive On

# Cache all files for 2 weeks after access (A).
ExpiresDefault A1209600

# Do not cache dynamically generated pages.
ExpiresByType text/html A1
</IfModule>

# Various rewrite rules.
<IfModule mod_rewrite.c>
RewriteEngine on

# If your site can be accessed both with and without the 'www.' prefix, you
# can use one of the following settings to redirect users to your preferred
# URL, either WITH or WITHOUT the 'www.' prefix. Choose ONLY one option:
#
# To redirect all users to access the site WITH the 'www.' prefix,
# (http://example.com/... will be redirected to http://www.example.com/...)
# adapt and uncomment the following:
# RewriteCond %{HTTP_HOST} ^example\.com$ [NC]
# RewriteRule ^(.*)$ http://www.example.com/$1 [L,R=301]
#
# To redirect all users to access the site WITHOUT the 'www.' prefix,
# (http://www.example.com/... will be redirected to http://example.com/...)
# uncomment and adapt the following:
# RewriteCond %{HTTP_HOST} ^www\.example\.com$ [NC]
# RewriteRule ^(.*)$ http://example.com/$1 [L,R=301]

# Modify the RewriteBase if you are using Drupal in a subdirectory or in a
# VirtualDocumentRoot and the rewrite rules are not working properly.
# For example if your site is at http://example.com/drupal uncomment and
# modify the following line:
# RewriteBase /drupal
#
# If your site is running in a VirtualDocumentRoot at http://example.com/,
# uncomment the following line:
# RewriteBase /

# Rewrite URLs of the form 'x' to the form 'index.php?q=x'.
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteCond %{REQUEST_URI} !=/favicon.ico
RewriteRule ^(.*)$ index.php?q=$1 [L,QSA]
</IfModule>

# $Id: .htaccess,v 1.90.2.3 2008/12/10 20:04:08 goba Exp $

+ 970
- 0
CHANGELOG.txt View File

@@ -0,0 +1,970 @@
// $Id: CHANGELOG.txt,v 1.253.2.29 2009/05/13 19:11:04 goba Exp $

Drupal 6.12, 2009-05-13
----------------------
- Fixed security issues (Cross site scripting), see SA-CORE-2009-006.
- Fixed a variety of small bugs.

Drupal 6.11, 2009-04-29
----------------------
- Fixed security issues (Cross site scripting and limited information
disclosure), see SA-CORE-2009-005
- Fixed performance issues with the menu router cache, the update
status cache and improved cache invalidation
- Fixed a variety of small bugs.

Drupal 6.10, 2009-02-25
----------------------
- Fixed a security issue, (Local file inclusion on Windows),
see SA-CORE-2009-003
- Fixed node_feed() so custom fields can show up in RSS feeds.
- Improved PostgreSQL compatibility.
- Fixed a variety of small bugs.

Drupal 6.9, 2009-01-14
----------------------
- Fixed security issues, (Access Bypass, Validation Bypass and Hardening
against SQL injection), see SA-CORE-2009-001
- Made HTTP request checking more robust and informative.
- Fixed HTTP_HOST checking to work again with HTTP 1.0 clients and
basic shell scripts.
- Removed t() calls from all schema documentation. Suggested best practice
changed for contributed modules, see http://drupal.org/node/322731.
- Fixed a variety of small bugs.

Drupal 6.8, 2008-12-11
----------------------
- Removed a previous change incompatible with PHP 5.1.x and lower.

Drupal 6.7, 2008-12-10
----------------------
- Fixed security issues, (Cross site request forgery and Cross site scripting), see SA-2008-073
- Updated robots.txt and .htaccess to match current file use.
- Fixed a variety of small bugs.

Drupal 6.6, 2008-10-22
----------------------
- Fixed security issues, (File inclusion, Cross site scripting), see SA-2008-067
- Fixed a variety of small bugs.

Drupal 6.5, 2008-10-08
----------------------
- Fixed security issues, (File upload access bypass, Access rules bypass,
BlogAPI access bypass), see SA-2008-060.
- Fixed a variety of small bugs.

Drupal 6.4, 2008-08-13
----------------------
- Fixed a security issue (Cross site scripting, Arbitrary file uploads via
BlogAPI, Cross site request forgeries and Various Upload module
vulnerabilities), see SA-2008-047.
- Improved error messages during installation.
- Fixed a bug that prevented AHAH handlers to be attached to radios widgets.
- Fixed a variety of small bugs.

Drupal 6.3, 2008-07-09
----------------------
- Fixed security issues, (Cross site scripting, cross site request forgery,
session fixation and SQL injection), see SA-2008-044.
- Slightly modified installation process to prevent file ownership issues on
shared hosts.
- Improved PostgreSQL compatibility (rewritten queries; custom blocks).
- Upgraded to jQuery 1.2.6.
- Performance improvements to search, menu handling and form API caches.
- Fixed Views compatibility issues (Views for Drupal 6 requires Drupal 6.3+).
- Fixed a variety of small bugs.

Drupal 6.2, 2008-04-09
----------------------
- Fixed a variety of small bugs.
- Fixed a security issue (Access bypasses), see SA-2008-026.

Drupal 6.1, 2008-02-27
----------------------
- Fixed a variety of small bugs.
- Fixed a security issue (Cross site scripting), see SA-2008-018.

Drupal 6.0, 2008-02-13
----------------------
- New, faster and better menu system.
- New watchdog as a hook functionality.
* New hook_watchdog that can be implemented by any module to route log
messages to various destinations.
* Expands the severity levels from 3 (Error, Warning, Notice) to the 8
levels defined in RFC 3164.
* The watchdog module is now called dblog, and is optional, but enabled by
default in the default install profile.
* Extended the database log module so log messages can be filtered.
* Added syslog module: useful for monitoring large Drupal installations.
- Added optional e-mail notifications when users are approved, blocked, or
deleted.
- Drupal works with error reporting set to E_ALL.
- Added scripts/drupal.sh to execute Drupal code from the command line. Useful
to use Drupal as a framework to build command-line tools.
- Made signature support optional and made it possible to theme signatures.
- Made it possible to filter the URL aliases on the URL alias administration
screen.
- Language system improvements:
* Support for right to left languages.
* Language detection based on parts of the URL.
* Browser based language detection.
* Made it possible to specify a node's language.
* Support for translating posts on the site to different languages.
* Language dependent path aliases.
* Automatically import translations when adding a new language.
* JavaScript interface translation.
* Automatically import a module's translation upon enabling that module.
- Moved "PHP input filter" to a standalone module so it can be deleted for
security reasons.
- Usability:
* Improved handling of teasers in posts.
* Added sticky table headers.
* Check for clean URL support automatically with JavaScript.
* Removed default/settings.php. Instead the installer will create it from
default.settings.php.
* Made it possible to configure your own date formats.
* Remember anonymous comment posters.
* Only allow modules and themes to be enabled that have explicitly been
ported to the correct core API version.
* Can now specify the minimum PHP version required for a module within the
.info file.
* Drupal core no longer requires CREATE TEMPORARY TABLES or LOCK TABLES
database rights.
* Dynamically check password strength and confirmation.
* Refactored poll administration.
* Implemented drag-and-drop positioning for blocks, menu items, taxonomy
vocabularies and terms, forums, profile fields, and input format filters.
- Theme system:
* Added .info files to themes and made it easier to specify regions and
features.
* Added theme registry: modules can directly provide .tpl.php files for
their themes without having to create theme_ functions.
* Used the Garland theme for the installation and maintenance pages.
* Added theme preprocess functions for themes that are templates.
* Added support for themeable functions in JavaScript.
- Refactored update.php to a generic batch API to be able to run time-consuming
operations in multiple subsequent HTTP requests.
- Installer:
* Themed the installer with the Garland theme.
* Added form to provide initial site information during installation.
* Added ability to provide extra installation steps programmatically.
* Made it possible to import interface translations at install time.
- Added the HTML corrector filter:
* Fixes faulty and chopped off HTML in postings.
* Tags are now automatically closed at the end of the teaser.
- Performance:
* Made it easier to conditionally load .include files and split up many core
modules.
* Added a JavaScript aggregator.
* Added block-level caching, improving performance for both authenticated
and anonymous users.
* Made Drupal work correctly when running behind a reverse proxy like
Squid or Pound.
- File handling improvements:
* Entries in the files table are now keyed to a user instead of a node.
* Added reusable validation functions to check for uploaded file sizes,
extensions, and image resolution.
* Added ability to create and remove temporary files during a cron job.
- Forum improvements:
* Any node type may now be posted in a forum.
- Taxonomy improvements:
* Descriptions for terms are now shown on taxonomy/term pages as well
as RSS feeds.
* Added versioning support to categories by associating them with node
revisions.
- Added support for OpenID.
- Added support for triggering configurable actions.
- Added the Update status module to automatically check for available updates
and warn sites if they are missing security updates or newer versions.
Sites deploying from CVS should use http://drupal.org/project/cvs_deploy.
Advanced settings provided by http://drupal.org/project/update_advanced.
- Upgraded the core JavaScript library to jQuery version 1.2.3.
- Added a new Schema API, which provides built-in support for core and
contributed modules to work with databases other than MySQL.
- Removed drupal.module. The functionality lives on as the Site network
contributed module (http://drupal.org/project/site_network).
- Removed old system updates. Updates from Drupal versions prior to 5.x will
require upgrading to 5.x before upgrading to 6.x.

Drupal 5.18, 2009-05-13
----------------------
- Fixed security issues (Cross site scripting), see SA-CORE-2009-006.
- Fixed a variety of small bugs.

Drupal 5.17, 2009-04-29
-----------------------
- Fixed security issues (Cross site scripting and limited information disclosure) see SA-CORE-2009-005.
- Fixed a variety of small bugs.

Drupal 5.16, 2009-02-25
-----------------------
- Fixed a security issue, (Local file inclusion on Windows), see SA-CORE-2009-004.
- Fixed a variety of small bugs.

Drupal 5.15, 2009-01-14
----------------------
- Fixed security issues, (Hardening against SQL injection), see SA-CORE-2009-001
- Fixed HTTP_HOST checking to work again with HTTP 1.0 clients and
basic shell scripts.
- Fixed a variety of small bugs.

Drupal 5.14, 2008-12-11
----------------------
- Removed a previous change incompatible with PHP 5.1.x and lower.

Drupal 5.13, 2008-12-10
-----------------------
- fixed a variety of small bugs.
- fixed security issues, (Cross site request forgery and Cross site scripting), see SA-2008-073
- updated robots.txt and .htaccess to match current file use.

Drupal 5.12, 2008-10-22
-----------------------
- fixed security issues, (File inclusion), see SA-2008-067

Drupal 5.11, 2008-10-08
-----------------------
- fixed a variety of small bugs.
- fixed security issues, (File upload access bypass, Access rules bypass,
BlogAPI access bypass, Node validation bypass), see SA-2008-060

Drupal 5.10, 2008-08-13
-----------------------
- fixed a variety of small bugs.
- fixed security issues, (Cross site scripting, Arbitrary file uploads via
BlogAPI and Cross site request forgery), see SA-2008-047

Drupal 5.9, 2008-07-23
----------------------
- fixed a variety of small bugs.
- fixed security issues, (Session fixation), see SA-2008-046

Drupal 5.8, 2008-07-09
----------------------
- fixed a variety of small bugs.
- fixed security issues, (Cross site scripting, cross site request forgery, and
session fixation), see SA-2008-044

Drupal 5.7, 2008-01-28
----------------------
- fixed the input format configuration page.
- fixed a variety of small bugs.

Drupal 5.6, 2008-01-10
----------------------
- fixed a variety of small bugs.
- fixed a security issue (Cross site request forgery), see SA-2008-005
- fixed a security issue (Cross site scripting, UTF8), see SA-2008-006
- fixed a security issue (Cross site scripting, register_globals), see SA-2008-007

Drupal 5.5, 2007-12-06
----------------------
- fixed missing missing brackets in a query in the user module.
- fixed taxonomy feed bug introduced by SA-2007-031

Drupal 5.4, 2007-12-05
----------------------
- fixed a variety of small bugs.
- fixed a security issue (SQL injection), see SA-2007-031

Drupal 5.3, 2007-10-17
----------------------
- fixed a variety of small bugs.
- fixed a security issue (HTTP response splitting), see SA-2007-024
- fixed a security issue (Arbitrary code execution via installer), see SA-2007-025
- fixed a security issue (Cross site scripting via uploads), see SA-2007-026
- fixed a security issue (User deletion cross site request forgery), see SA-2007-029
- fixed a security issue (API handling of unpublished comment), see SA-2007-030

Drupal 5.2, 2007-07-26
----------------------
- changed hook_link() $teaser argument to match documentation.
- fixed a variety of small bugs.
- fixed a security issue (cross-site request forgery), see SA-2007-017
- fixed a security issue (cross-site scripting), see SA-2007-018

Drupal 5.1, 2007-01-29
----------------------
- fixed security issue (code execution), see SA-2007-005
- fixed a variety of small bugs.

Drupal 5.0, 2007-01-15
----------------------
- Completely retooled the administration page
* /Admin now contains an administration page which may be themed
* Reorganised administration menu items by task and by module
* Added a status report page with detailed PHP/MySQL/Drupal information
- Added web-based installer which can:
* Check installation and run-time requirements
* Automatically generate the database configuration file
* Install pre-made 'install profiles' or distributions
* Import the database structure with automatic table prefixing
* Be localized
- Added new default Garland theme
- Added color module to change some themes' color schemes
- Included the jQuery JavaScript library 1.0.4 and converted all core JavaScript to use it
- Introduced the ability to alter mail sent from system
- Module system:
* Added .info files for module meta-data
* Added support for module dependencies
* Improved module installation screen
* Moved core modules to their own directories
* Added support for module uninstalling
- Added support for different cache backends
- Added support for a generic "sites/all" directory.
- Usability:
* Added support for auto-complete forms (AJAX) to user profiles.
* Made it possible to instantly assign roles to newly created user accounts.
* Improved configurability of the contact forms.
* Reorganized the settings pages.
* Made it easy to investigate popular search terms.
* Added a 'select all' checkbox and a range select feature to administration tables.
* Simplified the 'break' tag to split teasers from body.
* Use proper capitalization for titles, menu items and operations.
- Integrated urlfilter.module into filter.module
- Block system:
* Extended the block visibility settings with a role specific setting.
* Made it possible to customize all block titles.
- Poll module:
* Optionally allow people to inspect all votes.
* Optionally allow people to cancel their vote.
- Distributed authentication:
* Added default server option.
- Added default robots.txt to control crawlers.
- Database API:
* Added db_table_exists().
- Blogapi module:
* 'Blogapi new' and 'blogapi edit' nodeapi operations.
- User module:
* Added hook_profile_alter().
* E-mail verification is made optional.
* Added mass editing and filtering on admin/user/user.
- PHP Template engine:
* Add the ability to look for a series of suggested templates.
* Look for page templates based upon the path.
* Look for block templates based upon the region, module, and delta.
- Content system:
* Made it easier for node access modules to work well with each other.
* Added configurable content types.
* Changed node rendering to work with structured arrays.
- Performance:
* Improved session handling: reduces database overhead.
* Improved access checking: reduces database overhead.
* Made it possible to do memcached based session management.
* Omit sidebars when serving a '404 - Page not found': saves CPU cycles and bandwidth.
* Added an 'aggressive' caching policy.
* Added a CSS aggregator and compressor (up to 40% faster page loads).
- Removed the archive module.
- Upgrade system:
* Created space for update branches.
- Forms API:
* Made it possible to programmatically submit forms.
* Improved api for multistep forms.
- Theme system:
* Split up and removed drupal.css.
* Added nested lists generation.
* Added a self-clearing block class.

Drupal 4.7.11, 2008-01-10
-------------------------
- fixed a security issue (Cross site request forgery), see SA-2008-005
- fixed a security issue (Cross site scripting, UTF8), see SA-2008-006
- fixed a security issue (Cross site scripting, register_globals), see SA-2008-007

Drupal 4.7.10, 2007-12-06
-------------------------
- fixed taxonomy feed bug introduced by SA-2007-031

Drupal 4.7.9, 2007-12-05
------------------------
- fixed a security issue (SQL injection), see SA-2007-031

Drupal 4.7.8, 2007-10-17
----------------------
- fixed a security issue (HTTP response splitting), see SA-2007-024
- fixed a security issue (Cross site scripting via uploads), see SA-2007-026
- fixed a security issue (API handling of unpublished comment), see SA-2007-030

Drupal 4.7.7, 2007-07-26
------------------------
- fixed security issue (XSS), see SA-2007-018

Drupal 4.7.6, 2007-01-29
------------------------
- fixed security issue (code execution), see SA-2007-005

Drupal 4.7.5, 2007-01-05
------------------------
- Fixed security issue (XSS), see SA-2007-001
- Fixed security issue (DoS), see SA-2007-002

Drupal 4.7.4, 2006-10-18
------------------------
- Fixed security issue (XSS), see SA-2006-024
- Fixed security issue (CSRF), see SA-2006-025
- Fixed security issue (Form action attribute injection), see SA-2006-026

Drupal 4.7.3, 2006-08-02
------------------------
- Fixed security issue (XSS), see SA-2006-011

Drupal 4.7.2, 2006-06-01
------------------------
- Fixed critical upload issue, see SA-2006-007
- Fixed taxonomy XSS issue, see SA-2006-008
- Fixed a variety of small bugs.

Drupal 4.7.1, 2006-05-24
------------------------
- Fixed critical SQL issue, see SA-2006-005
- Fixed a serious upgrade related bug.
- Fixed a variety of small bugs.

Drupal 4.7.0, 2006-05-01
------------------------
- Added free tagging support.
- Added a site-wide contact form.
- Theme system:
* Added the PHPTemplate theme engine and removed the Xtemplate engine.
* Converted the bluemarine theme from XTemplate to PHPTemplate.
* Converted the pushbutton theme from XTemplate to PHPTemplate.
- Usability:
* Reworked the 'request new password' functionality.
* Reworked the node and comment edit forms.
* Made it easy to add nodes to the navigation menu.
* Added site 'offline for maintenance' feature.
* Added support for auto-complete forms (AJAX).
* Added support for collapsible page sections (JS).
* Added support for resizable text fields (JS).
* Improved file upload functionality (AJAX).
* Reorganized some settings pages.
* Added friendly database error screens.
* Improved styling of update.php.
- Refactored the forms API.
* Made it possible to alter, extend or theme forms.
- Comment system:
* Added support for "mass comment operations" to ease repetitive tasks.
* Comment moderation has been removed.
- Node system:
* Reworked the revision functionality.
* Removed the bookmarklet code. Third-party modules can now handle
This.
- Upgrade system:
* Allows contributed modules to plug into the upgrade system.
- Profiles:
* Added a block to display author information along with posts.
* Added support for private profile fields.
- Statistics module:
* Added the ability to track page generation times.
* Made it possible to block certain IPs/hostnames.
- Block system:
* Added support for theme-specific block regions.
- Syndication:
* Made the aggregator module parse Atom feeds.
* Made the aggregator generate RSS feeds.
* Added RSS feed settings.
- XML-RPC:
* Replaced the XML-RPC library by a better one.
- Performance:
* Added 'loose caching' option for high-traffic sites.
* Improved performance of path aliasing.
* Added the ability to track page generation times.
- Internationalization:
* Improved Unicode string handling API.
* Added support for PHP's multibyte string module.
- Added support for PHP5's 'mysqli' extension.
- Search module:
* Made indexer smarter and more robust.
* Added advanced search operators (e.g. phrase, node type, ...).
* Added customizable result ranking.
- PostgreSQL support:
* Removed dependency on PL/pgSQL procedural language.
- Menu system:
* Added support for external URLs.
- Queue module:
* Removed from core.
- HTTP handling:
* Added support for a tolerant Base URL.
* Output URIs relative to the root, without a base tag.

Drupal 4.6.11, 2007-01-05
-------------------------
- Fixed security issue (XSS), see SA-2007-001
- Fixed security issue (DoS), see SA-2007-002

Drupal 4.6.10, 2006-10-18
------------------------
- Fixed security issue (XSS), see SA-2006-024
- Fixed security issue (CSRF), see SA-2006-025
- Fixed security issue (Form action attribute injection), see SA-2006-026

Drupal 4.6.9, 2006-08-02
------------------------
- Fixed security issue (XSS), see SA-2006-011

Drupal 4.6.8, 2006-06-01
------------------------
- Fixed critical upload issue, see SA-2006-007
- Fixed taxonomy XSS issue, see SA-2006-008

Drupal 4.6.7, 2006-05-24
------------------------
- Fixed critical SQL issue, see SA-2006-005

Drupal 4.6.6, 2006-03-13
------------------------
- Fixed bugs, including 4 security vulnerabilities.

Drupal 4.6.5, 2005-12-12
------------------------
- Fixed bugs: no critical bugs were identified.

Drupal 4.6.4, 2005-11-30
------------------------
- Fixed bugs, including 3 security vulnerabilities.

Drupal 4.6.3, 2005-08-15
------------------------
- Fixed bugs, including a critical "arbitrary PHP code execution" bug.

Drupal 4.6.2, 2005-06-29
------------------------
- Fixed bugs, including two critical "arbitrary PHP code execution" bugs.

Drupal 4.6.1, 2005-06-01
------------------------
- Fixed bugs, including a critical input validation bug.

Drupal 4.6.0, 2005-04-15
------------------------
- PHP5 compliance
- Search:
* Added UTF-8 support to make it work with all languages.
* Improved search indexing algorithm.
* Improved search output.
* Impose a throttle on indexing of large sites.
* Added search block.
- Syndication:
* Made the ping module ping pingomatic.com which, in turn, will ping all the major ping services.
* Made Drupal generate RSS 2.0 feeds.
* Made RSS feeds extensible.
* Added categories to RSS feeds.
* Added enclosures to RSS feeds.
- Flood control mechanism:
* Added a mechanism to throttle certain operations.
- Usability:
* Refactored the block configuration pages.
* Refactored the statistics pages.
* Refactored the watchdog pages.
* Refactored the throttle module configuration.
* Refactored the access rules page.
* Refactored the content administration page.
* Introduced forum configuration pages.
* Added a 'add child page' link to book pages.
- Contact module:
* Added a simple contact module that allows users to contact each other using e-mail.
- Multi-site configuration:
* Made it possible to run multiple sites from a single code base.
- Added an image API: enables better image handling.
- Block system:
* Extended the block visibility settings.
- Theme system:
* Added new theme functions.
- Database backend:
* The PEAR database backend is no longer supported.
- Performance:
* Improved performance of the forum topics block.
* Improved performance of the tracker module.
* Improved performance of the node pages.
- Documentation:
* Improved and extended PHPDoc/Doxygen comments.

Drupal 4.5.8, 2006-03-13
------------------------
- Fixed bugs, including 3 security vulnerabilities.

Drupal 4.5.7, 2005-12-12
------------------------
- Fixed bugs: no critical bugs were identified.

Drupal 4.5.6, 2005-11-30
------------------------
- Fixed bugs, including 3 security vulnerabilities.

Drupal 4.5.5, 2005-08-15
------------------------
- Fixed bugs, including a critical "arbitrary PHP code execution" bug.

Drupal 4.5.4, 2005-06-29
------------------------
- Fixed bugs, including two critical "arbitrary PHP code execution" bugs.

Drupal 4.5.3, 2005-06-01
------------------------
- Fixed bugs, including a critical input validation bug.

Drupal 4.5.2, 2005-01-15
------------------------
- Fixed bugs: a cross-site scripting (XSS) vulnerability has been fixed.

Drupal 4.5.1, 2004-12-01
------------------------
- Fixed bugs: no critical bugs were identified.

Drupal 4.5.0, 2004-10-18
------------------------
- Navigation:
* Made it possible to add, delete, rename and move menu items.
* Introduced tabs and subtabs for local tasks.
* Reorganized the navigation menus.
- User management:
* Added support for multiple roles per user.
* Made it possible to add custom profile fields.
* Made it possible to browse user profiles by field.
- Node system:
* Added support for node-level permissions.
- Comment module:
* Made it possible to leave contact information without having to register.
- Upload module:
* Added support for uploading documents (includes images).
- Forum module:
* Added support for sticky forum topics.
* Made it possible to track forum topics.
- Syndication:
* Added support for RSS ping-notifications of http://technorati.com/.
* Refactored the categorization of syndicated news items.
* Added an URL alias for 'rss.xml'.
* Improved date parsing.
- Database backend:
* Added support for multiple database connections.
* The PostgreSQL backend does no longer require PEAR.
- Theme system:
* Changed all GIFs to PNGs.
* Reorganised the handling of themes, template engines, templates and styles.
* Unified and extended the available theme settings.
* Added theme screenshots.
- Blocks:
* Added 'recent comments' block.
* Added 'categories' block.
- Blogger API:
* Added support for auto-discovery of blogger API via RSD.
- Performance:
* Added support for sending gzip compressed pages.
* Improved performance of the forum module.
- Accessibility:
* Improved the accessibility of the archive module's calendar.
* Improved form handling and error reporting.
* Added HTTP redirects to prevent submitting twice when refreshing right after a form submission.
- Refactored 403 (forbidden) handling and added support for custom 403 pages.
- Documentation:
* Added PHPDoc/Doxygen comments.
- Filter system:
* Added support for using multiple input formats on the site
* Expanded the embedded PHP-code feature so it can be used everywhere
* Added support for role-dependant filtering, through input formats
- UI translation:
* Managing translations is now completely done through the administration interface
* Added support for importing/exporting gettext .po files

Drupal 4.4.3, 2005-06-01
------------------------
- Fixed bugs, including a critical input validation bug.

Drupal 4.4.2, 2004-07-04
------------------------
- Fixed bugs: no critical bugs were identified.

Drupal 4.4.1, 2004-05-01
------------------------
- Fixed bugs: no critical bugs were identified.

Drupal 4.4.0, 2004-04-01
------------------------
- Added support for the MetaWeblog API and MovableType extensions.
- Added a file API: enables better document management.
- Improved the watchdog and search module to log search keys.
- News aggregator:
* Added support for conditional GET.
* Added OPML feed subscription list.
* Added support for <image>, <pubDate>, <dc:date>, <dcterms:created>, <dcterms:issued> and <dcterms:modified>.
- Comment module:
* Made it possible to disable the "comment viewing controls".
- Performance:
* Improved module loading when serving cached pages.
* Made it possible to automatically disable modules when under heavy load.
* Made it possible to automatically disable blocks when under heavy load.
* Improved performance and memory footprint of the locale module.
- Theme system:
* Made all theme functions start with 'theme_'.
* Made all theme functions return their output.
* Migrated away from using the BaseTheme class.
* Added many new theme functions and refactored existing theme functions.
* Added avatar support to 'Xtemplate'.
* Replaced theme 'UnConeD' by 'Chameleon'.
* Replaced theme 'Marvin' by 'Pushbutton'.
- Usability:
* Added breadcrumb navigation to all pages.
* Made it possible to add context-sensitive help to all pages.
* Replaced drop-down menus by radio buttons where appropriate.
* Removed the 'magic_quotes_gpc = 0' requirement.
* Added a 'book navigation' block.
- Accessibility:
* Made themes degrade gracefully in absence of CSS.
* Grouped form elements using '<fieldset>' and '<legend>' tags.
* Added '<label>' tags to form elements.
- Refactored 404 (file not found) handling and added support for custom 404 pages.
- Improved the filter system to prevent conflicts between filters:
* Made it possible to change the order in which filters are applied.
- Documentation:
* Added PHPDoc/Doxygen comments.

Drupal 4.3.2, 2004-01-01
------------------------
- Fixed bugs: no critical bugs were identified.

Drupal 4.3.1, 2003-12-01
------------------------
- Fixed bugs: no critical bugs were identified.

Drupal 4.3.0, 2003-11-01
------------------------
- Added support for configurable URLs.
- Added support for sortable table columns.
- Database backend:
* Added support for selective database table prefixing.
- Performance:
* Optimized many SQL queries for speed by converting left joins to inner joins.
- Comment module:
* Rewrote the comment housekeeping code to be much more efficient and scalable.
* Changed the comment module to use the standard pager.
- User module:
* Added support for multiple sessions per user.
* Added support for anonymous user sessions.
- Forum module:
* Improved the forum views and the themability thereof.
- Book module:
* Improved integration of non-book nodes in the book outline.
- Usability:
* Added support for "mass node operations" to ease repetitive tasks.
* Added support for breadcrumb navigation to several modules' user pages.
* Integrated the administration pages with the normal user pages.

Drupal 4.2.0, 2003-08-01
------------------------
- Added support for clean URLs.
- Added textarea hook and support for onload attributes: enables integration of WYSIWYG editors.
- Rewrote the RSS/RDF parser:
* It will now use PHP's built-in XML parser to parse news feeds.
- Rewrote the administration pages:
* Improved the navigational elements and added breadcrumb navigation.
* Improved the look and feel.
* Added context-sensitive help.
- Database backend:
* Fixed numerous SQL queries to make Drupal ANSI compliant.
* Added MSSQL database scheme.
- Search module:
* Changed the search module to use implicit AND'ing instead of implicit OR'ing.
- Node system:
* Replaced the "post content" permission by more fine-grained permissions.
* Improved content submission:
+ Improved teasers: teasers are now optional, teaser length can be configured, teaser and body are edited in a single textarea, users will no longer be bothered with teasers when the post is too short for one.
+ Added the ability to preview both the short and the full version of your posts.
* Extended the node API which allows for better integration.
* Added default node settings to control the behavior for promotion, moderation and other options.
- Themes:
* Replaced theme "Goofy" by "Xtemplate", a template driven theme.
- Removed the 'register_globals = on' requirement.
- Added better installation instructions.

Drupal 4.1.0, 2003-02-01
------------------------
- Collaboratively revised and expanded the Drupal documentation.
- Rewrote comment.module:
* Reintroduced comment rating/moderation.
* Added support for comment paging.
* Performance improvements: improved comment caching, faster SQL queries, etc.
- Rewrote block.module:
* Performance improvements: blocks are no longer rendered when not displayed.
- Rewrote forum.module:
* Added a lot of features one can find in stand-alone forum software including but not limited to support for topic paging, added support for icons, rewrote the statistics module, etc.
- Rewrote statistics.module:
* Collects access counts for each node, referrer logs, number of users/guests.
* Export blocks displaying top viewed nodes over last 24 hour period, top viewed nodes over all time, last nodes viewed, how many users/guest online.
- Added throttle.module:
* Auto-throttle congestion control mechanism: Drupal can adapt itself based on the server load.
- Added profile.module:
* Enables to extend the user and registration page.
- Added pager support to the main page.
- Replaced weblogs.module by ping.module:
* Added support for normal and RSS notifications of http://blo.gs/.
* Added support for RSS ping-notifications of http://weblogs.com/.
- Removed the rating module
- Themes:
* Removed a significant portion of hard-coded mark-up.

Drupal 4.0.0, 2002-06-15
------------------------
- Added tracker.module:
* Replaces the previous "your [site]" links (recent comments and nodes).
- Added weblogs.module:
* This will ping weblogs.com when new content is promoted.
- Added taxonomy module which replaces the meta module.
* Supports relations, hierarchies and synonyms.
- Added a caching system:
* Speeds up pages for anonymous users and reduces system load.
- Added support for external SMTP libraries.
- Added an archive extension to the calendar.
- Added support for the Blogger API.
- Themes:
* Cleaned up the theme system.
* Moved themes that are not maintained to contributions CVS repository.
- Database backend:
* Changed to PEAR database abstraction layer.
* Using ANSI SQL queries to be more portable.
- Rewrote the user system:
* Added support for Drupal authentication through XML-RPC and through a Jabber server.
* Added support for modules to add more user data.
* Users may delete their own account.
* Added who's new and who's online blocks.
- Changed block system:
* Various hard coded blocks are now dynamic.
* Blocks can now be enabled and/or be set by the user.
* Blocks can be set to only show up on some pages.
* Merged box module with block module.
- Node system:
* Blogs can be updated.
* Teasers (abstracts) on all node types.
* Improved error checking.
* Content versioning support.
* Usability improvements.
- Improved book module to support text, HTML and PHP pages.
- Improved comment module to mark new comments.
- Added a general outliner which will let any node type be linked to a book.
- Added an update script that lets you upgrade from previous releases or on a day to day basis when using the development tree.
- Search module:
* Improved the search system by making it context sensitive.
* Added indexing.
- Various updates:
* Changed output to valid XHTML.
* Improved multiple sites using the same Drupal database support.
* Added support for session IDs in URLs instead of cookies.
* Made the type of content on the front page configurable.
* Made each cloud site have its own settings.
* Modules and themes can now be enabled/disabled using the administration pages.
* Added URL abstraction for links.
* Usability changes (renamed links, better UI, etc).
- Collaboratively revised and expanded the Drupal documentation.

Drupal 3.0.1, 2001-10-15
------------------------
- Various updates:
* Added missing translations
* Updated the themes: tidied up some HTML code and added new Drupal logos.

Drupal 3.0.0, 2001-09-15
------------------------
- Major overhaul of the entire underlying design:
* Everything is based on nodes: nodes are a conceptual "black box" to couple and manage different types of content and that promotes reusing existing code, thus reducing the complexity and size of Drupal as well as improving long-term stability.
- Rewrote submission/moderation queue and renamed it to queue.module.
- Removed FAQ and documentation module and merged them into a "book module".
- Removed ban module and integrated it into account.module as "access control":
* Access control is based on much more powerful regular expressions (regex) now rather than on MySQL pattern matching.
- Rewrote watchdog and submission throttle:
* Improved watchdog messages and added watchdog filter.
- Rewrote headline code and renamed it to import.module and export.module:
* Added various improvements, including a better parser, bundles and better control over individual feeds.
- Rewrote section code and renamed it to meta.module:
* Supports unlimited amount of nested topics. Topics can be nested to create a multi-level hierarchy.
- Rewrote configuration file resolving:
* Drupal tries to locate a configuration file that matches your domain name or uses conf.php if the former failed. Note also that the configuration files got renamed from .conf to .php for security's sake on mal-configured Drupal sites.
- Added caching support which makes Drupal extremely scalable.
- Added access.module:
* Allows you to set up 'roles' (groups) and to bind a set of permissions to each group.
- Added blog.module.
- Added poll.module.
- Added system.module:
* Moved most of the configuration options from hostname.conf to the new administration section.
* Added support for custom "filters".
- Added statistics.module
- Added moderate.module:
* Allows to assign users editorial/moderator rights to certain nodes or topics.
- Added page.module:
* Allows creation of static (and dynamic) pages through the administration interface.
- Added help.module:
* Groups all available module documentation on a single page.
- Added forum.module:
* Added an integrated forum.
- Added cvs.module and cvs-to-sql.pl:
* Allows to display and mail CVS log messages as daily digests.
- Added book.module:
* Allows collaborative handbook writing: primary used for Drupal documentation.
- Removed cron.module and integrated it into conf.module.
- Removed module.module as it was no longer needed.
- Various updates:
* Added "auto-post new submissions" feature versus "moderate new submissions".
* Introduced links/Drupal tags: [[link]]
* Added preview functionality when submitting new content (such as a story) from the administration pages.
* Made the administration section only show those links a user has access to.
* Made all modules use specific form_* functions to guarantee a rock-solid forms and more consistent layout.
* Improved scheduler:
+ Content can be scheduled to be 'posted', 'queued' and 'hidden'.
* Improved account module:
+ Added "access control" to allow/deny certain usernames/e-mail addresses/hostnames.
* Improved locale module:
+ Added new overview to easy the translation process.
* Improved comment module:
+ Made it possible to permanently delete comments.
* Improved rating module
* Improved story module:
+ Added preview functionality for administrators.
+ Made it possible to permanently delete stories.
* Improved themes:
+ W3C validation on a best effort basis.
+ Removed $theme->control() from themes.
+ Added theme "goofy".
- Collaboratively revised and expanded the Drupal documentation.

Drupal 2.0.0, 2001-03-15
------------------------
- Rewrote the comment/discussion code:
* Comment navigation should be less confusing now.
* Additional/alternative display and order methods have been added.
* Modules can be extended with a "comment system": modules can embed the existing comment system without having to write their own, duplicate comment system.
- Added sections and section manager:
* Story sections can be maintained from the administration pages.
* Story sections make the open submission more adaptive in that you can set individual post, dump and expiration thresholds for each section according to the story type and urgency level: stories in certain sections do not "expire" and might stay interesting and active as time passes by, whereas news-related stories are only considered "hot" over a short period of time.
- Multiple vhosts + multiple directories:
* You can set up multiple Drupal sites on top of the same physical source tree either by using vhosts or sub-directories.
- Added "user ratings" similar to SlashCode's Karma or Scoop's Mojo:
* All rating logic is packed into a module to ease experimenting with different rating heuristics/algorithms.
- Added "search infrastructure":
* Improved search page and integrated search functionality in the administration pages.
- Added translation / localization / internationalization support:
* Because many people would love to see their website showing a lot less of English, and far more of their own language, Drupal provides a framework to set up a multi-lingual website or to overwrite the default English text in English.
- Added fine-grained user permission (or group) system:
* Users can be granted access to specific administration sections. Example: a FAQ maintainer can be given access to maintain the FAQ and translators can be given access to the translation pages.
- Added FAQ module
- Changed the "open submission queue" into a (optional) module.
- Various updates:
* Improved account module:
+ User accounts can be deleted.
+ Added fine-grained permission support.
* Improved block module
* Improved diary module:
+ Diary entries can be deleted
* Improved headline module:
+ Improved parser to support more "generic" RDF/RSS/XML backend.
* Improved module module
* Improved watchdog module
* Improved database abstraction layer
* Improved themes:
+ W3C validation on a best effort basis
+ Added theme "example" (alias "Stone Age")
* Added new scripts to directory "scripts"
* Added directory "misc"
* Added CREDITS file
- Revised documentation

Drupal 1.0.0, 2001-01-15
------------------------
- Initial release

+ 25
- 0
COPYRIGHT.txt View File

@@ -0,0 +1,25 @@
// $Id: COPYRIGHT.txt,v 1.2.2.1 2008/02/06 12:45:55 goba Exp $

All Drupal code is Copyright 2001 - 2008 by the original authors.

This program is free software; you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation.

This program is distributed in the hope that it will be useful, but
WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY
or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License
for more details.

You should have received a copy of the GNU General Public License
along with this program as the file LICENSE.txt; if not, please see
http://www.gnu.org/licenses/old-licenses/gpl-2.0.txt.

Drupal is a registered trademark of Dries Buytaert.

Drupal includes works under other copyright notices and distributed
according to the terms of the GNU General Public License or a compatible
license, including:

jQuery - Copyright (c) 2008 John Resig


+ 40
- 0
INSTALL.mysql.txt View File

@@ -0,0 +1,40 @@
// $Id: INSTALL.mysql.txt,v 1.10 2007/11/19 19:53:51 goba Exp $

CREATE THE MySQL DATABASE
--------------------------

This step is only necessary if you don't already have a database set-up (e.g. by
your host). In the following examples, 'username' is an example MySQL user which
has the CREATE and GRANT privileges. Use the appropriate user name for your
system.

First, you must create a new database for your Drupal site (here, 'databasename'
is the name of the new database):

mysqladmin -u username -p create databasename

MySQL will prompt for the 'username' database password and then create the
initial database files. Next you must login and set the access database rights:

mysql -u username -p

Again, you will be asked for the 'username' database password. At the MySQL
prompt, enter following command:

GRANT SELECT, INSERT, UPDATE, DELETE, CREATE, DROP, INDEX, ALTER
ON databasename.*
TO 'username'@'localhost' IDENTIFIED BY 'password';

where

'databasename' is the name of your database
'username@localhost' is the username of your MySQL account
'password' is the password required for that username

Note: Unless your database user has all of the privileges listed above, you will
not be able to run Drupal.

If successful, MySQL will reply with:

Query OK, 0 rows affected


+ 28
- 0
INSTALL.pgsql.txt View File

@@ -0,0 +1,28 @@
// $Id: INSTALL.pgsql.txt,v 1.7 2007/11/26 16:36:42 dries Exp $

CREATE THE PostgreSQL DATABASE
------------------------------

Note that the database must be created with UTF-8 (Unicode) encoding.

1. CREATE DATABASE USER

This step is only necessary if you don't already have a user set up (e.g.
by your host) or you want to create new user for use with Drupal only. The
following command creates a new user named "username" and asks for a
password for that user:

createuser --pwprompt --encrypted --no-adduser --no-createdb username

If everything works correctly, you'll see a "CREATE USER" notice.

2. CREATE THE DRUPAL DATABASE

This step is only necessary if you don't already have a database set up (e.g.
by your host) or you want to create new database for use with Drupal only.
The following command creates a new database named "databasename", which is
owned by previously created "username":

createdb --encoding=UNICODE --owner=username databasename

If everything works correctly, you'll see a "CREATE DATABASE" notice.

+ 350
- 0
INSTALL.txt View File

@@ -0,0 +1,350 @@
// $Id: INSTALL.txt,v 1.61.2.4 2008/07/09 19:15:59 goba Exp $

CONTENTS OF THIS FILE
---------------------

* Requirements
* Optional requirements
* Installation
* Drupal administration
* Customizing your theme(s)
* Multisite Configuration
* More Information

REQUIREMENTS
------------

Drupal requires a web server, PHP 4 (4.3.5 or greater) or PHP 5
(http://www.php.net/) and either MySQL (http://www.mysql.com/) or PostgreSQL
(http://www.postgresql.org/). The Apache web server and MySQL database are
recommended; other web server and database combinations such as IIS and
PostgreSQL have been tested to a lesser extent. When using MySQL, version 4.1.1
or greater is recommended to assure you can safely transfer the database.

For more detailed information about Drupal requirements, see "Requirements"
(http://drupal.org/requirements) in the Drupal handbook.

For detailed information on how to configure a test server environment using
a variety of operating systems and web servers, see "Local server setup"
(http://drupal.org/node/157602) in the Drupal handbook.

OPTIONAL TASKS
--------------

- To use XML-based services such as the Blogger API and RSS syndication,
you will need PHP's XML extension. This extension is enabled by default.

- To use Drupal's "Clean URLs" feature on an Apache web server, you will need
the mod_rewrite module and the ability to use local .htaccess files. For
Clean URLs support on IIS, see "Using Clean URLs with IIS"
(http://drupal.org/node/3854) in the Drupal handbook.

- Various Drupal features require that the web server process (for
example, httpd) be able to initiate outbound connections. This is usually
possible, but some hosting providers or server configurations forbid such
connections. The features that depend on this functionality include the
integrated "Update status" module (which downloads information about
available updates of Drupal core and any installed contributed modules and
themes), the ability to log in via OpenID, fetching aggregator feeds, or
other network-dependent services.


INSTALLATION
------------

1. DOWNLOAD DRUPAL AND OPTIONALLY A TRANSLATION

You can obtain the latest Drupal release from http://drupal.org/. The files
are in .tar.gz format and can be extracted using most compression tools. On a
typical Unix command line, use:

wget http://drupal.org/files/projects/drupal-x.x.tar.gz
tar -zxvf drupal-x.x.tar.gz

This will create a new directory drupal-x.x/ containing all Drupal files
and directories. Move the contents of that directory into a directory within
your web server's document root or your public HTML directory:

mv drupal-x.x/* drupal-x.x/.htaccess /var/www/html

If you would like to have the default English interface translated to a
different language, we have good news. You can install and use Drupal in
other languages from the start. Check whether a released package of the
language desired is available for this Drupal version at
http://drupal.org/project/translations and download the package. Extract
the contents to the same directory where you extracted Drupal into.

2. CREATE THE CONFIGURATION FILE AND GRANT WRITE PERMISSIONS

Drupal comes with a default.settings.php file in the sites/default
directory. The installer uses this file as a template to create your
settings file using the details you provide through the install process.
To avoid problems when upgrading, Drupal is not packaged with an actual
settings file. You must create a file named settings.php. You may do so
by making a copy of default.settings.php (or create an empty file with
this name in the same directory). For example, (from the installation
directory) make a copy of the default.settings.php file with the command:

cp sites/default/default.settings.php sites/default/settings.php

Next, give the web server write privileges to the sites/default/settings.php
file with the command (from the installation directory):

chmod o+w sites/default/settings.php

So that the files directory can be created automatically, give the web server
write privileges to the sites/default directory with the command (from the
installation directory):

chmod o+w sites/default

3. CREATE THE DRUPAL DATABASE

Drupal requires access to a database in order to be installed. Your database
user will need sufficient privileges to run Drupal. Additional information
about privileges, and instructions to create a database using the command
line are available in INSTALL.mysql.txt (for MySQL) or INSTALL.pgsql.txt
(for PostgreSQL).

To create a database using PHPMyAdmin or a web-based control panel consult
the documentation or ask your webhost service provider.

Take note of the username, password, database name and hostname as you
create the database. You will enter these items in the install script.

4. RUN THE INSTALL SCRIPT

To run the install script point your browser to the base URL of your website
(e.g., http://www.example.com).

You will be guided through several screens to set up the database,
create tables, add the first user account and provide basic web
site settings.

The install script will attempt to create a files storage directory
in the default location at sites/default/files (the location of the
files directory may be changed after Drupal is installed). In some
cases, you may need to create the directory and modify its permissions
manually. Use the following commands (from the installation directory)
to create the files directory and grant the web server write privileges to it:

mkdir sites/default/files
chmod o+w sites/default/files

The install script will attempt to write-protect the settings.php file and
the sites/default directory after saving your configuration. However, you
may need to manually write-protect them using the commands (from the
installation directory):

chmod a-w sites/default/settings.php
chmod a-w sites/default

If you make manual changes to the file later, be sure to protect it again
after making your modifications. Failure to remove write permissions to that
file is a security risk. Although the default location for the settings.php
file is at sites/default/settings.php, it may be in another location
if you use the multi-site setup, as explained below.

5. CONFIGURE DRUPAL

When the install script succeeds, you will be directed to the "Welcome"
page, and you will be logged in as the administrator already. Proceed with
the initial configuration steps suggested on the "Welcome" page.

If the default Drupal theme is not displaying properly and links on the page
result in "Page Not Found" errors, try manually setting the $base_url variable
in the settings.php file if not already set. It's currently known that servers
running FastCGI can run into problems if the $base_url variable is left
commented out (see http://bugs.php.net/bug.php?id=19656).

6. REVIEW FILE SYSTEM STORAGE SETTINGS AND FILE PERMISSIONS

The files directory created in step 4 is the default file system path used
to store all uploaded files, as well as some temporary files created by Drupal.
After installation, the settings for the file system path may be modified
to store uploaded files in a different location.

It is not necessary to modify this path, but you may wish to change it if:

* your site runs multiple Drupal installations from a single codebase
(modify the file system path of each installation to a different
directory so that uploads do not overlap between installations); or,

* your site runs a number of web server front-ends behind a load
balancer or reverse proxy (modify the file system path on each
server to point to a shared file repository).

To modify the file system path:

* Ensure that the new location for the path exists or create it if
necessary. To create a new directory named uploads, for example,
use the following command from a shell or system prompt (while in
the installation directory):

mkdir uploads

* Ensure that the new location for the path is writable by the web
server process. To grant write permissions for a directory named
uploads, you may need to use the following command from a shell
or system prompt (while in the installation directory):

chmod o+w uploads

* Access the file system path settings in Drupal by selecting these
menu items from the Navigation menu:

Administer > Site configuration > File system

Enter the path to the new location (e.g.: uploads) at the File
System Path prompt.

Changing the file system path after files have been uploaded may cause
unexpected problems on an existing site. If you modify the file system path
on an existing site, remember to copy all files from the original location
to the new location.

Some administrators suggest making the documentation files, especially
CHANGELOG.txt, non-readable so that the exact version of Drupal you are
running is slightly more difficult to determine. If you wish to implement
this optional security measure, use the following command from a shell or
system prompt (while in the installation directory):

chmod a-r CHANGELOG.txt

Note that the example only affects CHANGELOG.txt. To completely hide
all documentation files from public view, repeat this command for each of
the Drupal documentation files in the installation directory, substituting the
name of each file for CHANGELOG.txt in the example.

For more information on setting file permissions, see "Modifying Linux, Unix,
and Mac file permissions" (http://drupal.org/node/202483) or "Modifying
Windows file permissions" (http://drupal.org/node/202491) in the online
handbook.

7. CRON MAINTENANCE TASKS

Many Drupal modules have periodic tasks that must be triggered by a cron
maintenance task, including search module (to build and update the index
used for keyword searching), aggregator module (to retrieve feeds from other
sites), ping module (to notify other sites about new or updated content), and
system module (to perform routine maintenance and pruning on system tables).
To activate these tasks, call the cron page by visiting
http://www.example.com/cron.php, which, in turn, executes tasks on behalf
of installed modules.

Most systems support the crontab utility for scheduling tasks like this. The
following example crontab line will activate the cron tasks automatically on
the hour:

0 * * * * wget -O - -q -t 1 http://www.example.com/cron.php

More information about cron maintenance tasks are available in the help pages
and in Drupal's online handbook at http://drupal.org/cron. Example scripts can
be found in the scripts/ directory.

DRUPAL ADMINISTRATION
---------------------

A new installation of Drupal defaults to a very basic configuration with only a
few active modules and minimal user access rights.

Use your administration panel to enable and configure services. For example:

General Settings Administer > Site configuration > Site information
Enable Modules Administer > Site building > Modules
Configure Themes Administer > Site building > Themes
Set User Permissions Administer > User management > Permissions

For more information on configuration options, read the instructions which
accompany the different configuration settings and consult the various help
pages available in the administration panel.

Community-contributed modules and themes are available at http://drupal.org/.

CUSTOMIZING YOUR THEME(S)
-------------------------

Now that your installation is running, you will want to customize the look of
your site. Several sample themes are included and more can be downloaded from
drupal.org.

Simple customization of your theme can be done using only CSS. Further changes
require understanding the phptemplate engine that is part of Drupal. See
http://drupal.org/handbook/customization to find out more.

MULTISITE CONFIGURATION
-----------------------

A single Drupal installation can host several Drupal-powered sites, each with
its own individual configuration.

Additional site configurations are created in subdirectories within the 'sites'
directory. Each subdirectory must have a 'settings.php' file which specifies the
configuration settings. The easiest way to create additional sites is to copy
the 'default' directory and modify the 'settings.php' file as appropriate. The
new directory name is constructed from the site's URL. The configuration for
www.example.com could be in 'sites/example.com/settings.php' (note that 'www.'
should be omitted if users can access your site at http://example.com/).

Sites do not have to have a different domain. You can also use subdomains and
subdirectories for Drupal sites. For example, example.com, sub.example.com,
and sub.example.com/site3 can all be defined as independent Drupal sites. The
setup for a configuration such as this would look like the following:

sites/default/settings.php
sites/example.com/settings.php
sites/sub.example.com/settings.php
sites/sub.example.com.site3/settings.php

When searching for a site configuration (for example www.sub.example.com/site3),
Drupal will search for configuration files in the following order, using the
first configuration it finds:

sites/www.sub.example.com.site3/settings.php
sites/sub.example.com.site3/settings.php
sites/example.com.site3/settings.php
sites/www.sub.example.com/settings.php
sites/sub.example.com/settings.php
sites/example.com/settings.php
sites/default/settings.php

If you are installing on a non-standard port, the port number is treated as the
deepest subdomain. For example: http://www.example.com:8080/ could be loaded
from sites/8080.www.example.com/. The port number will be removed according to
the pattern above if no port-specific configuration is found, just like a real
subdomain.

Each site configuration can have its own site-specific modules and themes in
addition to those installed in the standard 'modules' and 'themes' directories.
To use site-specific modules or themes, simply create a 'modules' or 'themes'
directory within the site configuration directory. For example, if
sub.example.com has a custom theme and a custom module that should not be
accessible to other sites, the setup would look like this:

sites/sub.example.com/:
settings.php
themes/custom_theme
modules/custom_module

NOTE: for more information about multiple virtual hosts or the configuration
settings, consult the Drupal handbook at drupal.org.

For more information on configuring Drupal's file system path in a multi-site
configuration, see step 6 above.

MORE INFORMATION
----------------

- For additional documentation, see the online Drupal handbook at
http://drupal.org/handbook.

- For a list of security announcements, see the "Security announcements" page
at http://drupal.org/security (available as an RSS feed). This page also
describes how to subscribe to these announcements via e-mail.

- For information about the Drupal security process, or to find out how to report
a potential security issue to the Drupal security team, see the "Security team"
page at http://drupal.org/security-team.

- For information about the wide range of available support options, see the
"Support" page at http://drupal.org/support.

+ 340
- 0
LICENSE.txt View File

@@ -0,0 +1,340 @@
// $Id: LICENSE.txt,v 1.5.4.1 2009/01/06 17:27:13 goba Exp $
GNU GENERAL PUBLIC LICENSE
Version 2, June 1991

Copyright (C) 1989, 1991 Free Software Foundation, Inc.,
51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA
Everyone is permitted to copy and distribute verbatim copies
of this license document, but changing it is not allowed.

Preamble

The licenses for most software are designed to take away your
freedom to share and change it. By contrast, the GNU General Public
License is intended to guarantee your freedom to share and change free
software--to make sure the software is free for all its users. This
General Public License applies to most of the Free Software
Foundation's software and to any other program whose authors commit to
using it. (Some other Free Software Foundation software is covered by
the GNU Lesser General Public License instead.) You can apply it to
your programs, too.

When we speak of free software, we are referring to freedom, not
price. Our General Public Licenses are designed to make sure that you
have the freedom to distribute copies of free software (and charge for
this service if you wish), that you receive source code or can get it
if you want it, that you can change the software or use pieces of it
in new free programs; and that you know you can do these things.

To protect your rights, we need to make restrictions that forbid
anyone to deny you these rights or to ask you to surrender the rights.
These restrictions translate to certain responsibilities for you if you
distribute copies of the software, or if you modify it.

For example, if you distribute copies of such a program, whether
gratis or for a fee, you must give the recipients all the rights that
you have. You must make sure that they, too, receive or can get the
source code. And you must show them these terms so they know their
rights.

We protect your rights with two steps: (1) copyright the software, and
(2) offer you this license which gives you legal permission to copy,
distribute and/or modify the software.

Also, for each author's protection and ours, we want to make certain
that everyone understands that there is no warranty for this free
software. If the software is modified by someone else and passed on, we
want its recipients to know that what they have is not the original, so
that any problems introduced by others will not reflect on the original
authors' reputations.

Finally, any free program is threatened constantly by software
patents. We wish to avoid the danger that redistributors of a free
program will individually obtain patent licenses, in effect making the
program proprietary. To prevent this, we have made it clear that any
patent must be licensed for everyone's free use or not licensed at all.

The precise terms and conditions for copying, distribution and
modification follow.

GNU GENERAL PUBLIC LICENSE
TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION

0. This License applies to any program or other work which contains
a notice placed by the copyright holder saying it may be distributed
under the terms of this General Public License. The "Program", below,
refers to any such program or work, and a "work based on the Program"
means either the Program or any derivative work under copyright law:
that is to say, a work containing the Program or a portion of it,
either verbatim or with modifications and/or translated into another
language. (Hereinafter, translation is included without limitation in
the term "modification".) Each licensee is addressed as "you".

Activities other than copying, distribution and modification are not
covered by this License; they are outside its scope. The act of
running the Program is not restricted, and the output from the Program
is covered only if its contents constitute a work based on the
Program (independent of having been made by running the Program).
Whether that is true depends on what the Program does.

1. You may copy and distribute verbatim copies of the Program's
source code as you receive it, in any medium, provided that you
conspicuously and appropriately publish on each copy an appropriate
copyright notice and disclaimer of warranty; keep intact all the
notices that refer to this License and to the absence of any warranty;
and give any other recipients of the Program a copy of this License
along with the Program.

You may charge a fee for the physical act of transferring a copy, and
you may at your option offer warranty protection in exchange for a fee.

2. You may modify your copy or copies of the Program or any portion
of it, thus forming a work based on the Program, and copy and
distribute such modifications or work under the terms of Section 1
above, provided that you also meet all of these conditions:

a) You must cause the modified files to carry prominent notices
stating that you changed the files and the date of any change.

b) You must cause any work that you distribute or publish, that in
whole or in part contains or is derived from the Program or any
part thereof, to be licensed as a whole at no charge to all third
parties under the terms of this License.

c) If the modified program normally reads commands interactively
when run, you must cause it, when started running for such
interactive use in the most ordinary way, to print or display an
announcement including an appropriate copyright notice and a
notice that there is no warranty (or else, saying that you provide
a warranty) and that users may redistribute the program under
these conditions, and telling the user how to view a copy of this
License. (Exception: if the Program itself is interactive but
does not normally print such an announcement, your work based on
the Program is not required to print an announcement.)

These requirements apply to the modified work as a whole. If
identifiable sections of that work are not derived from the Program,
and can be reasonably considered independent and separate works in
themselves, then this License, and its terms, do not apply to those
sections when you distribute them as separate works. But when you
distribute the same sections as part of a whole which is a work based
on the Program, the distribution of the whole must be on the terms of
this License, whose permissions for other licensees extend to the
entire whole, and thus to each and every part regardless of who wrote it.

Thus, it is not the intent of this section to claim rights or contest
your rights to work written entirely by you; rather, the intent is to
exercise the right to control the distribution of derivative or
collective works based on the Program.

In addition, mere aggregation of another work not based on the Program
with the Program (or with a work based on the Program) on a volume of
a storage or distribution medium does not bring the other work under
the scope of this License.

3. You may copy and distribute the Program (or a work based on it,
under Section 2) in object code or executable form under the terms of
Sections 1 and 2 above provided that you also do one of the following:

a) Accompany it with the complete corresponding machine-readable
source code, which must be distributed under the terms of Sections
1 and 2 above on a medium customarily used for software interchange; or,

b) Accompany it with a written offer, valid for at least three
years, to give any third party, for a charge no more than your
cost of physically performing source distribution, a complete
machine-readable copy of the corresponding source code, to be
distributed under the terms of Sections 1 and 2 above on a medium
customarily used for software interchange; or,

c) Accompany it with the information you received as to the offer
to distribute corresponding source code. (This alternative is
allowed only for noncommercial distribution and only if you
received the program in object code or executable form with such
an offer, in accord with Subsection b above.)

The source code for a work means the preferred form of the work for
making modifications to it. For an executable work, complete source
code means all the source code for all modules it contains, plus any
associated interface definition files, plus the scripts used to
control compilation and installation of the executable. However, as a
special exception, the source code distributed need not include
anything that is normally distributed (in either source or binary
form) with the major components (compiler, kernel, and so on) of the
operating system on which the executable runs, unless that component
itself accompanies the executable.

If distribution of executable or object code is made by offering
access to copy from a designated place, then offering equivalent
access to copy the source code from the same place counts as
distribution of the source code, even though third parties are not
compelled to copy the source along with the object code.

4. You may not copy, modify, sublicense, or distribute the Program
except as expressly provided under this License. Any attempt
otherwise to copy, modify, sublicense or distribute the Program is
void, and will automatically terminate your rights under this License.
However, parties who have received copies, or rights, from you under
this License will not have their licenses terminated so long as such
parties remain in full compliance.

5. You are not required to accept this License, since you have not
signed it. However, nothing else grants you permission to modify or
distribute the Program or its derivative works. These actions are
prohibited by law if you do not accept this License. Therefore, by
modifying or distributing the Program (or any work based on the
Program), you indicate your acceptance of this License to do so, and
all its terms and conditions for copying, distributing or modifying
the Program or works based on it.

6. Each time you redistribute the Program (or any work based on the
Program), the recipient automatically receives a license from the
original licensor to copy, distribute or modify the Program subject to
these terms and conditions. You may not impose any further
restrictions on the recipients' exercise of the rights granted herein.
You are not responsible for enforcing compliance by third parties to
this License.

7. If, as a consequence of a court judgment or allegation of patent
infringement or for any other reason (not limited to patent issues),
conditions are imposed on you (whether by court order, agreement or
otherwise) that contradict the conditions of this License, they do not
excuse you from the conditions of this License. If you cannot
distribute so as to satisfy simultaneously your obligations under this
License and any other pertinent obligations, then as a consequence you
may not distribute the Program at all. For example, if a patent
license would not permit royalty-free redistribution of the Program by
all those who receive copies directly or indirectly through you, then
the only way you could satisfy both it and this License would be to
refrain entirely from distribution of the Program.

If any portion of this section is held invalid or unenforceable under
any particular circumstance, the balance of the section is intended to
apply and the section as a whole is intended to apply in other
circumstances.

It is not the purpose of this section to induce you to infringe any
patents or other property right claims or to contest validity of any
such claims; this section has the sole purpose of protecting the
integrity of the free software distribution system, which is
implemented by public license practices. Many people have made
generous contributions to the wide range of software distributed
through that system in reliance on consistent application of that
system; it is up to the author/donor to decide if he or she is willing
to distribute software through any other system and a licensee cannot
impose that choice.

This section is intended to make thoroughly clear what is believed to
be a consequence of the rest of this License.

8. If the distribution and/or use of the Program is restricted in
certain countries either by patents or by copyrighted interfaces, the
original copyright holder who places the Program under this License
may add an explicit geographical distribution limitation excluding
those countries, so that distribution is permitted only in or among
countries not thus excluded. In such case, this License incorporates
the limitation as if written in the body of this License.

9. The Free Software Foundation may publish revised and/or new versions
of the General Public License from time to time. Such new versions will
be similar in spirit to the present version, but may differ in detail to
address new problems or concerns.

Each version is given a distinguishing version number. If the Program
specifies a version number of this License which applies to it and "any
later version", you have the option of following the terms and conditions
either of that version or of any later version published by the Free
Software Foundation. If the Program does not specify a version number of
this License, you may choose any version ever published by the Free Software
Foundation.

10. If you wish to incorporate parts of the Program into other free
programs whose distribution conditions are different, write to the author
to ask for permission. For software which is copyrighted by the Free
Software Foundation, write to the Free Software Foundation; we sometimes
make exceptions for this. Our decision will be guided by the two goals
of preserving the free status of all derivatives of our free software and
of promoting the sharing and reuse of software generally.

NO WARRANTY

11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY
FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN
OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED
OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS
TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE
PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,
REPAIR OR CORRECTION.

12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,
INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING
OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED
TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY
YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER
PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
POSSIBILITY OF SUCH DAMAGES.

END OF TERMS AND CONDITIONS

How to Apply These Terms to Your New Programs

If you develop a new program, and you want it to be of the greatest
possible use to the public, the best way to achieve this is to make it
free software which everyone can redistribute and change under these terms.

To do so, attach the following notices to the program. It is safest
to attach them to the start of each source file to most effectively
convey the exclusion of warranty; and each file should have at least
the "copyright" line and a pointer to where the full notice is found.

<one line to give the program's name and a brief idea of what it does.>
Copyright (C) <year> <name of author>

This program is free software; you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation; either version 2 of the License, or
(at your option) any later version.

This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.

You should have received a copy of the GNU General Public License along
with this program; if not, write to the Free Software Foundation, Inc.,
51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.

Also add information on how to contact you by electronic and paper mail.

If the program is interactive, make it output a short notice like this
when it starts in an interactive mode:

Gnomovision version 69, Copyright (C) year name of author
Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
This is free software, and you are welcome to redistribute it
under certain conditions; type `show c' for details.

The hypothetical commands `show w' and `show c' should show the appropriate
parts of the General Public License. Of course, the commands you use may
be called something other than `show w' and `show c'; they could even be
mouse-clicks or menu items--whatever suits your program.

You should also get your employer (if you work as a programmer) or your
school, if any, to sign a "copyright disclaimer" for the program, if
necessary. Here is a sample; alter the names:

Yoyodyne, Inc., hereby disclaims all copyright interest in the program
`Gnomovision' (which makes passes at compilers) written by James Hacker.

<signature of Ty Coon>, 1 April 1989
Ty Coon, President of Vice

This General Public License does not permit incorporating your program into
proprietary programs. If your program is a subroutine library, you may
consider it more useful to permit linking proprietary applications with the
library. If this is what you want to do, use the GNU Lesser General
Public License instead of this License.

+ 86
- 0
MAINTAINERS.txt View File

@@ -0,0 +1,86 @@
// $Id: MAINTAINERS.txt,v 1.19.2.2 2009/04/29 17:15:10 goba Exp $

List of maintainers
--------------------------------------------------------------------------------

LEGEND
======

- M: the maintainer
- S: status:
"supported" : someone is actually paid to look after this.
"maintained" : someone actually looks after it.
"fixes/patches" : it has a maintainer but they don't have time to
do much other than throw the odd patch in.
"orphan" : no current maintainer, but maybe you could take
the role as you write new code?

--------------------------------------------------------------------------------

BLOG API
M: James Walker <walkah@walkah.net>
S: maintained

DISTRIBUTED AUTHENTICATION MODULES
M: Moshe Weitzman <weitzman@tejasa.com>
S: maintained

DOCUMENTATION COORDINATOR
M: Steven Peck <speck@blkmtn.org>
S: maintained

FILTER SYSTEM
M: Steven Wittens <unconed@drupal.org>
S: maintained

FORM SYSTEM
M: Károly Négyesi <chx@mail.tvnet.hu>
S: maintained

LOCALE MODULE
M: Gabor Hojtsy <goba@php.net>
S: maintained

LOGGING
M: Khalid Baheyeldin <drupal@2bits.com>
S: maintained

MENU SYSTEM
M: Károly Négyesi <chx@mail.tvnet.hu>
S: maintained

PATH MODULE
M: Matt Westgate <drupal@asitis.org>
S: maintained

POSTGRESQL
M: Sammy Spets <sammys-drupal@synerger.com>
S: maintained

SECURITY COORDINATOR
M: Heine Deelstra <hdeelstra@gmail.com>
S: maintained

STATISTICS MODULE
M: Jeremy Andrews <jeremy@kerneltrap.com>
S: maintained

THEME SYSTEM
M: Earl Miles <merlin@logrus.com>
Joon Park <joon@dvessel.com>
S: maintained

UPDATE MODULE
M: Derek Wright <http://drupal.org/user/46549/contact>
S: maintained

XML-RPC SERVER/CLIENT
M: John VanDyk <http://drupal.org/user/2375/contact>
S: maintained

TRANSLATIONS COORDINATOR
M: Gerhard Killesreiter <gerhard@killesreiter.de>
S: maintained

THE REST:
M: Dries <dries@drupal.org>

+ 110
- 0
UPGRADE.txt View File

@@ -0,0 +1,110 @@
// $Id: UPGRADE.txt,v 1.12 2008/01/04 16:15:58 goba Exp $

UPGRADING
---------

Prior to upgrading, you should ensure that:

* Your system meets or exceeds Drupal's minimum requirements as shown at
http://drupal.org/requirements.
* You have a backup of all your relevant data (#1).
* Custom and contributed modules have been checked for compatibility (#11).
* Custom and contributed themes have been checked for compatibility (#11).
* You have read through this entire document.

Let's begin!

1. Backup your database and Drupal directory - especially your "sites"
directory which contains your configuration file and added modules and
themes, any contributed or custom modules in your "modules" directory,
and your "files" directory which contains uploaded files. If other files
have modifications, such as .htaccess or robots.txt, those should be
backed up as well.

Note: for a single site setup, the configuration file is the "settings.php"
file located at sites/default/settings.php. The default.settings.php file
contains a clean copy for restoration purposes, if required.

For multisite configurations, the configuration file is located in a
structure like the following:

sites/default/settings.php
sites/example.com/settings.php
sites/sub.example.com/settings.php
sites/sub.example.com.path/settings.php

More information on multisite configuration is located in INSTALL.txt.

2. If possible, log on as the user with user ID 1, which is the first account
created and the main administrator account. User ID 1 will be able to
automatically access update.php in step #10. There are special instructions
in step #10 if you are unable to log on as user ID 1. Do not close your
browser until the final step is complete.

3. Place the site in "Off-line" mode, to let the database updates run without
interruption and avoid displaying errors to end users of the site. This
option is at http://www.example.com/?q=admin/settings/site-maintenance
(replace www.example.com with your installation's domain name and path).