Skip to content

Instantly share code, notes, and snippets.

@and1truong

and1truong/c2ss.remove-txts.patch

Created January 29, 2012 17:50
Show Gist options
  • Save and1truong/1699819 to your computer and use it in GitHub Desktop.
Save and1truong/1699819 to your computer and use it in GitHub Desktop.
Download ZIP
Remove Drupal 7 txt files
Raw
c2ss.remove-txts.patch
diff --git a/CHANGELOG.txt b/CHANGELOG.txt
deleted file mode 100644
index d12ca6e..0000000
--- a/CHANGELOG.txt
+++ /dev/null
@@ -1,1425 +0,0 @@
-
-Drupal 7.11 xxxx-xx-xx (development version)
-----------------------
-
-
-Drupal 7.10, 2011-12-05
-----------------------
-- Fixed Content-Language HTTP header to not cause issues with Drush 5.x.
-- Reduce memory usage of theme registry (performance).
-- Fixed PECL upload progress bar for FileField
-- Fixed running update.php doesn't always clear the cache.
-- Fixed PDO exceptions on long titles.
-- Fixed Overlay redirect does not include query string.
-- Fixed D6 modules satisfy D7 module dependencies.
-- Fixed the ordering of module hooks when using module_implements_alter().
-- Fixed "floating" submit buttons during AJAX requests.
-- Fixed timezone selected on install not propogating to admin account.
-- Added msgctx context to JS translation functions, for feature parity with t().
-- Profiles' .install files now available during hook_install_tasks().
-- Added test coverage of 7.0 -> 7.x upgrade path.
-- Numerous notice fixes.
-- Numerous documentation improvements.
-- Additional automated test coverage.
-
-Drupal 7.9, 2011-10-26
-----------------------
-- Critical fixes to OpenID to spec violations that could allow for
- impersonation in certain scenarios. Existing OpenID users should see
- http://drupal.org/node/1120290#comment-5092796 for more information on
- transitioning.
-- Fixed files getting lost when adding multiple files to multiple file fields
- at the same time.
-- Improved usability of the clean URL test screens.
-- Restored height/width attributes on images run through the theme system.
-- Fixed usability bug with first password field being pre-filled by certain
- browser plugins.
-- Fixed file_usage_list() so that it can return more than one result.
-- Fixed bug preventing preview of private images on node form.
-- Fixed PDO error when inserting an aggregator title longer than 255 characters.
-- Spelled out what TRADITIONAL means in MySQL sql_mode.
-- Deprecated "!=" operator for DBTNG; should be "<>".
-- Added two new API functions (menu_tree_set_path()/menu_tree_get_path()) were
- added in order to enable setting the active menu trail for dynamically
- generated menu paths.
-- Added new "fast 404" capability in settings.php to bypass Drupal bootstrap
- when serving 404 pages for certain file types.
-- Added format_string() function which can perform string munging ala the t()
- function without the overhead of the translation system.
-- Numerous #states system fixes.
-- Numerous EntityFieldQuery, DBTNG, and SQLite fixes.
-- Numerous Shortcut module fixes.
-- Numerous language system fixes.
-- Numerous token fixes.
-- Numerous CSS fixes.
-- Numerous upgrade path fixes.
-- Numerous minor string fixes.
-- Numerous notice fixes.
-
-Drupal 7.8, 2011-08-31
-----------------------
-- Fixed critical upgrade path issue with multilingual sites, leading to lost
- content.
-- Numerous fixes to upgrade path, preventing fatal errors due to incorrect
- dependencies.
-- Fixed issue with saving files on hosts with open_basedir restrictions.
-- Fixed Update manger error when used with Overlay.
-- Fixed RTL support in Seven administration theme and Overlay.
-- Fixes to nested transaction support.
-- Introduced performance pattern to reduce Drupal core's RAM usage.
-- Added support for HTML 5 tags to filter_xss_admin().
-- Added exception handling to cron.
-- Added new hook hook_field_widget_form_alter() for contribtued modules.
-- element_validate_*() functions now available to contrib.
-- Added new maintainers for several subsystems.
-- Numerous testing system improvements.
-- Numerous markup and CSS fixes.
-- Numerous poll module fixes.
-- Numerous notice/warning fixes.
-- Numerous documentation fixes.
-- Numerous token fixes.
-
-Drupal 7.7, 2011-07-27
-----------------------
-- Fixed VERSION string.
-
-Drupal 7.6, 2011-07-27
-----------------------
-- Fixed support for remote streamwrappers.
-- AJAX now binds to 'click' instead of 'mousedown'.
-- 'Translatable' flag on fields created in UI now defaults to FALSE, to match those created via the API.
-- Performance enhancement to permissions page on large numbers of permissions.
-- More secure password generation.
-- Fix for temporary directory on Windows servers.
-- run-tests.sh now uses proc_open() instead of pcntl_fork() for better Windows support.
-- Numerous upgrade path fixes.
-- Numerous documentation fixes.
-- Numerous notice fixes.
-- Numerous fixes to improve PHP 5.4 support.
-- Numerous RTL improvements.
-
-Drupal 7.5, 2011-07-27
-----------------------
-- Fixed security issue (Access bypass), see SA-CORE-2011-003.
-
-Drupal 7.4, 2011-06-29
-----------------------
-- Rolled back patch that caused fatal errors in CTools, Feeds, and other modules using the class registry.
-- Fixed critical bug with saving default images.
-- Fixed fatal errors when uninstalling some modules.
-- Added workaround for MySQL transaction support breaking on DDL statments.
-- Improved page caching with external caching systems.
-- Fix to Batch API, which was terminating too early.
-- Numerous upgrade path fixes.
-- Performance fixes.
-- Additional test coverage.
-- Numerous documentation fixes.
-
-Drupal 7.3, 2011-06-29
-----------------------
-- Fixed security issue (Access bypass), see SA-CORE-2011-002.
-
-Drupal 7.2, 2011-05-25
-----------------------
-- Added a default .gitignore file.
-- Improved PostgreSQL and SQLite support.
-- Numerous critical performance improvements.
-- Numerous critical fixes to the upgrade path.
-- Numerous fixes to language and translation systems.
-- Numerous fixes to AJAX and #states systems.
-- Improvements to the locking system.
-- Numerous documentation fixes.
-- Numerous styling and theme system fixes.
-- Numerous fixes for schema mis-matches between Drupal 6 and 7.
-- Minor internal API clean-ups.
-
-Drupal 7.1, 2011-05-25
-----------------------
-- Fixed security issues (Cross site scripting, File access bypass), see SA-CORE-2011-001.
-
-Drupal 7.0, 2011-01-05
-----------------------
-- Database:
- * Fully rewritten database layer utilizing PHP 5's PDO abstraction layer.
- * Drupal now requires MySQL >= 5.0.15 or PostgreSQL >= 8.3.
- * Added query builders for INSERT, UPDATE, DELETE, MERGE, and SELECT queries.
- * Support for master/slave replication, transactions, multi-insert queries,
- and other features.
- * Added support for the SQLite database engine.
- * Default to InnoDB engine, rather than MyISAM, on MySQL when available.
- This offers increased scalability and data integrity.
-- Security:
- * Protected cron.php -- cron will only run if the proper key is provided.
- * Implemented a pluggable password system and much stronger password hashes
- that are compatible with the Portable PHP password hashing framework.
- * Rate limited login attempts to prevent brute-force password guessing, and
- improved the flood control API to allow variable time windows and
- identifiers for limiting user access to resources.
- * Transformed the "Update status" module into the "Update manager" which
- can securely install or update modules and themes via a web interface.
-- Usability:
- * Added contextual links (a.k.a. local tasks) to page elements, such as
- blocks, nodes, or comments, which allows to perform the most common tasks
- with a single click only.
- * Improved installer requirements check.
- * Improved support for integration of WYSIWYG editors.
- * Implemented drag-and-drop positioning for input format listings.
- * Implemented drag-and-drop positioning for language listing.
- * Implemented drag-and-drop positioning for poll options.
- * Provided descriptions and human-readable names for user permissions.
- * Removed comment controls for users.
- * Removed display order settings for comment module. Comment display
- order can now be customized using the Views module.
- * Removed the 'related terms' feature from taxonomy module since this can
- now be achieved with Field API.
- * Added additional features to the default install profile, and implemented
- a "slimmed down" install profile designed for developers.
- * Added a built-in, automated cron run feature, which is triggered by site
- visitors.
- * Added an administrator role which is assigned all permissions for
- installed modules automatically.
- * Image toolkits are now provided by modules (rather than requiring a
- manual file copy to the includes directory).
- * Added an edit tab to taxonomy term pages.
- * Redesigned password strength validator.
- * Redesigned the add content type screen.
- * Highlight duplicate URL aliases.
- * Renamed "input formats" to "text formats".
- * Moved text format permissions to the main permissions page.
- * Added configurable ability for users to cancel their own accounts.
- * Added "vertical tabs", a reusable interface component that features
- automatic summaries and increases usability.
- * Replaced fieldsets on node edit and add pages with vertical tabs.
-- Performance:
- * Improved performance on uncached page views by loading multiple core
- objects in a single database query.
- * Improved performance for logged-in users by reducing queries for path
- alias lookups.
- * Improved support for HTTP proxies (including reverse proxies), allowing
- anonymous page views to be served entirely from the proxy.
-- Documentation:
- * Hook API documentation now included in Drupal core.
-- News aggregator:
- * Added OPML import functionality for RSS feeds.
- * Optionally, RSS feeds may be configured to not automatically generate feed blocks.
-- Search:
- * Added support for language-aware searches.
-- Aggregator:
- * Introduced architecture that allows pluggable parsers and processors for
- syndicating RSS and Atom feeds.
- * Added options to suspend updating specific feeds and never discard feeds
- items.
-- Testing:
- * Added test framework and tests.
-- Improved time zone support:
- * Drupal now uses PHP's time zone database when rendering dates in local
- time. Site-wide and user-configured time zone offsets have been converted
- to time zone names, e.g. Africa/Abidjan.
- * In some cases the upgrade and install scripts do not choose the preferred
- site default time zone. The automatically-selected time zone can be
- corrected at admin/config/regional/settings.
- * If your site is being upgraded from Drupal 6 and you do not have the
- contributed date or event modules installed, user time zone settings will
- fallback to the system time zone and will have to be reconfigured by each user.
- * User-configured time zones now serve as the default time zone for PHP
- date/time functions.
-- Filter system:
- * Revamped the filter API and text format storage.
- * Added support for default text formats to be assigned on a per-role basis.
- * Refactored the HTML corrector to take advantage of PHP 5 features.
-- User system:
- * Added clean API functions for creating, loading, updating, and deleting
- user roles and permissions.
- * Refactored the "access rules" component of user module: The user module
- now provides a simple interface for blocking single IP addresses. The
- previous functionality in the user module for restricting certain e-mail
- addresses and usernames is now available as a contributed module. Further,
- IP address range blocking is no longer supported and should be implemented
- at the operating system level.
- * Removed per-user themes: Contributed modules with similar functionality
- are available.
-- OpenID:
- * Added support for Gmail and Google Apps for Domain identifiers. Users can
- now login with their user@example.com identifier when example.com is powered
- by Google.
- * Made the OpenID module more pluggable.
-- Added code registry:
- * Using the registry, modules declare their includable files via their .info file,
- allowing Drupal to lazy-load classes and interfaces as needed.
-- Theme system:
- * Removed the Bluemarine, Chameleon and Pushbutton themes. These themes live
- on as contributed themes (http://drupal.org/project/bluemarine,
- http://drupal.org/project/chameleon and http://drupal.org/project/pushbutton).
- * Added Stark theme to make analyzing Drupal's default HTML and CSS easier.
- * Added Seven as the default administration theme.
- * Variable preprocessing of theme hooks prior to template rendering now goes
- through two phases: a 'preprocess' phase and a new 'process' phase. See
- http://api.drupal.org/api/function/theme/7 for details.
- * Theme hooks implemented as functions (rather than as templates) can now
- also have preprocess (and process) functions. See
- http://api.drupal.org/api/function/theme/7 for details.
- * Added Bartik as the default theme.
-- File handling:
- * Files are now first class Drupal objects with file_load(), file_save(),
- and file_validate() functions and corresponding hooks.
- * The file_move(), file_copy() and file_delete() functions now operate on
- file objects and invoke file hooks so that modules are notified and can
- respond to changes.
- * For the occasions when only basic file manipulation are needed--such as
- uploading a site logo--that don't require the overhead of databases and
- hooks, the current unmanaged copy, move and delete operations have been
- preserved but renamed to file_unmanaged_*().
- * Rewrote file handling to use PHP stream wrappers to enable support for
- both public and private files and to support pluggable storage mechanisms
- and access to remote resources (e.g. S3 storage or Flickr photos).
- * The mime_extension_mapping variable has been removed. Modules that need to
- alter the default MIME type extension mappings should implement
- hook_file_mimetype_mapping_alter().
- * Added the hook_file_url_alter() hook, which makes it possible to serve
- files from a CDN.
- * Added a field specifically for uploading files, previously provided by
- the contributed module FileField.
-- Image handling:
- * Improved image handling, including better support for add-on image
- libraries.
- * Added API and interface for creating advanced image thumbnails.
- * Inclusion of additional effects such as rotate and desaturate.
- * Added a field specifically for uploading images, previously provided by
- the contributed module ImageField.
-- Added aliased multi-site support:
- * Added support for mapping domain names to sites directories.
-- Added RDF support:
- * Modules can declare RDF namespaces which are serialized in the <html> tag
- for RDFa support.
- * Modules can specify how their data structure maps to RDF.
- * Added support for RDFa export of nodes, comments, terms, users, etc. and
- their fields.
-- Search engine optimization and web linking:
- * Added a rel="canonical" link on node and comment pages to prevent
- duplicate content indexing by search engines.
- * Added a default rel="shortlink" link on node and comment pages that
- advertises a short link as an alternative URL to third-party services.
- * Meta information is now alterable by all modules before rendering.
-- Field API:
- * Custom data fields may be attached to nodes, users, comments and taxonomy
- terms.
- * Node bodies and teasers are now Field API fields instead of
- being a hard-coded property of node objects.
- * In addition, any other object type may register with Field API
- and allow custom data fields to be attached to itself.
- * Provides most of the features of the former Content Construction
- Kit (CCK) module.
- * Taxonomy terms are now Field API fields that can be added to any fieldable
- object.
-- Installer:
- * Refactored the installer into an API that allows Drupal to be installed
- via a command line script.
-- Page organization
- * Made the help text area a full featured region with blocks.
- * Site mission is replaced with the highlighted content block region and
- separate RSS feed description settings.
- * The footer message setting was removed in favor of custom blocks.
- * Made the main page content a block which can be moved and ordered
- with other blocks in the same region.
- * Blocks can now return structured arrays for later rendering just
- like page callbacks.
-- Translation system
- * The translation system now supports message context (msgctxt).
- * Added support for translatable fields to Field API.
-- JavaScript changes
- * Upgraded the core JavaScript library to jQuery version 1.4.4.
- * Upgraded the jQuery Forms library to 2.52.
- * Added jQuery UI 1.8.7, which allows improvements to Drupal's user
- experience.
-- Better module version support
- * Modules now can specify which version of another module they depend on.
-- Removed modules from core
- * The following modules have been removed from core, because contributed
- modules with similar functionality are available:
- * Blog API module
- * Ping module
- * Throttle module
-- Improved node access control system.
- * All modules may now influence the access to a node at runtime, not just
- the module that defined a node.
- * Users may now be allowed to bypass node access restrictions without giving
- them complete access to the site.
- * Access control affects both published and unpublished nodes.
- * Numerous other improvements to the node access system.
-- Actions system
- * Simplified definitions of actions and triggers.
- * Removed dependency on the combination of hooks and operations. Triggers
- now directly map to module hooks.
-- Task handling
- * Added a queue API to process many or long-running tasks.
- * Added queue API support to cron API.
- * Added a locking framework to coordinate long-running operations across
- requests.
-
-Drupal 6.23-dev, xxxx-xx-xx (development release)
------------------------
-
-Drupal 6.22, 2011-05-25
------------------------
-- Made Drupal 6 work better with IIS and Internet Explorer.
-- Fixed .po file imports to work better with custom textgroups.
-- Improved code documentation at various places.
-- Fixed a variety of other bugs.
-
-Drupal 6.21, 2011-05-25
-----------------------
-- Fixed security issues (Cross site scripting), see SA-CORE-2011-001.
-
-Drupal 6.20, 2010-12-15
-----------------------
-- Fixed a variety of small bugs, improved code documentation.
-
-Drupal 6.19, 2010-08-11
-----------------------
-- Fixed a variety of small bugs, improved code documentation.
-
-Drupal 6.18, 2010-08-11
-----------------------
-- Fixed security issues (OpenID authentication bypass, File download access
- bypass, Comment unpublishing bypass, Actions cross site scripting),
- see SA-CORE-2010-002.
-
-Drupal 6.17, 2010-06-02
-----------------------
-- Improved PostgreSQL compatibility
-- Better PHP 5.3 and PHP 4 compatibility
-- Better browser compatibility of CSS and JS aggregation
-- Improved logging for login failures
-- Fixed an incompatibility with some contributed modules and the locking system
-- Fixed a variety of other bugs.
-
-Drupal 6.16, 2010-03-03
-----------------------
-- Fixed security issues (Installation cross site scripting, Open redirection,
- Locale module cross site scripting, Blocked user session regeneration),
- see SA-CORE-2010-001.
-- Better support for updated jQuery versions.
-- Reduced resource usage of update.module.
-- Fixed several issues relating to support of install profiles and
- distributions.
-- Added a locking framework to avoid data corruption on long operations.
-- Fixed a variety of other bugs.
-
-Drupal 6.15, 2009-12-16
-----------------------
-- Fixed security issues (Cross site scripting), see SA-CORE-2009-009.
-- Fixed a variety of other bugs.
-
-Drupal 6.14, 2009-09-16
-----------------------
-- Fixed security issues (OpenID association cross site request forgeries,
- OpenID impersonation and File upload), see SA-CORE-2009-008.
-- Changed the system modules page to not run all cache rebuilds; use the
- button on the performance settings page to achieve the same effect.
-- Added support for PHP 5.3.0 out of the box.
-- Fixed a variety of small bugs.
-
-Drupal 6.13, 2009-07-01
-----------------------
-- Fixed security issues (Cross site scripting, Input format access bypass and
- Password leakage in URL), see SA-CORE-2009-007.
-- Fixed a variety of small bugs.
-
-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.23, 2010-08-11
------------------------
-- Fixed security issues (File download access bypass, Comment unpublishing
- bypass), see SA-CORE-2010-002.
-
-Drupal 5.22, 2010-03-03
------------------------
-- Fixed security issues (Open redirection, Locale module cross site scripting,
- Blocked user session regeneration), see SA-CORE-2010-001.
-
-Drupal 5.21, 2009-12-16
------------------------
-- Fixed a security issue (Cross site scripting), see SA-CORE-2009-009.
-- Fixed a variety of small bugs.
-
-Drupal 5.20, 2009-09-16
------------------------
-- Avoid security problems resulting from writing Drupal 6-style menu
- declarations.
-- Fixed security issues (session fixation), see SA-CORE-2009-008.
-- Fixed a variety of small bugs.
-
-Drupal 5.19, 2009-07-01
------------------------
-- Fixed security issues (Cross site scripting and Password leakage in URL), see
- SA-CORE-2009-007.
-- Fixed a variety of small bugs.
-
-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-dependent 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
diff --git a/COPYRIGHT.txt b/COPYRIGHT.txt
deleted file mode 100644
index e983474..0000000
--- a/COPYRIGHT.txt
+++ /dev/null
@@ -1,25 +0,0 @@
-
-All Drupal code is Copyright 2001 - 2010 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; 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 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 - 2009 John Resig
-
diff --git a/INSTALL.mysql.txt b/INSTALL.mysql.txt
deleted file mode 100644
index bee5811..0000000
--- a/INSTALL.mysql.txt
+++ /dev/null
@@ -1,42 +0,0 @@
-
-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 log in 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 the 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
-
-If the InnoDB storage engine is available, it will be used for all database
-tables. InnoDB provides features over MyISAM such as transaction support,
-row-level locks, and consistent non-locking reads.
diff --git a/INSTALL.pgsql.txt b/INSTALL.pgsql.txt
deleted file mode 100644
index 8fe8043..0000000
--- a/INSTALL.pgsql.txt
+++ /dev/null
@@ -1,44 +0,0 @@
-
-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 want to create a 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-createrole --no-createdb username
-
- If there are no errors, then the command was successful.
-
-2. CREATE DRUPAL DATABASE
-
- This step is only necessary if you don't already have a database set up
- (e.g., by your host) or want to create a new database for use with Drupal
- only. The following command creates a new database named 'databasename',
- which is owned by the previously created 'username':
-
- createdb --encoding=UTF8 --owner=username databasename
-
- If there are no errors, then the command was successful.
-
-3. CREATE SCHEMA OR SCHEMAS (Optional advanced step)
-
- Drupal will run across different schemas within your database if you so wish.
- By default, Drupal runs inside the 'public' schema but you can use $db_prefix
- inside settings.php to define a schema for Drupal to run inside of, or
- specify tables that are shared inside of a separate schema. Drupal will not
- create schemas for you. In fact, the user that Drupal runs as should not be
- allowed to do this. You'll need to execute the SQL below as a superuser,
- replace 'username' with the username that Drupal uses to connect to
- PostgreSQL, and replace 'schema_name' with a schema name you wish to use,
- such as 'shared':
-
- CREATE SCHEMA schema_name AUTHORIZATION username;
-
- Do this for as many schemas as you need. See default.settings.php for
- instructions on how to set which tables use which schemas.
diff --git a/INSTALL.sqlite.txt b/INSTALL.sqlite.txt
deleted file mode 100644
index 8e57d60..0000000
--- a/INSTALL.sqlite.txt
+++ /dev/null
@@ -1,31 +0,0 @@
-
-SQLITE REQUIREMENTS
--------------------
-
-To use SQLite with your Drupal installation, the following requirements must be
-met: Server has PHP 5.2 or later with PDO, and the PDO SQLite driver must be
-enabled.
-
-SQLITE DATABASE CREATION
-------------------------
-
-The Drupal installer will create the SQLite database for you. The only
-requirement is that the installer must have write permissions to the directory
-where the database file resides. This directory (not just the database file) also
-has to remain writeable by the web server going forward for SQLite to continue to
-be able to operate.
-
-On the "Database configuration" form in the "Database file" field, you must
-supply the exact path to where you wish your database file to reside. It is
-strongly suggested that you choose a path that is outside of the webroot, yet
-ensure that the directory is writeable by the web server.
-
-If you must place your database file in your webroot, you could try using the
-following in your "Database file" field:
-
- sites/default/files/.ht.sqlite
-
-Note: The .ht in the name will tell Apache to prevent the database from being
-downloaded. Please check that the file is, indeed, protected by your webserver.
-If not, please consult the documentation of your webserver on how to protect a
-file from downloading.
diff --git a/INSTALL.txt b/INSTALL.txt
deleted file mode 100644
index 7b526e3..0000000
--- a/INSTALL.txt
+++ /dev/null
@@ -1,398 +0,0 @@
-
-CONTENTS OF THIS FILE
----------------------
-
- * Requirements and notes
- * Optional server requirements
- * Installation
- * Building and customizing your site
- * Multisite configuration
- * More information
-
-REQUIREMENTS AND NOTES
-----------------------
-
-Drupal requires:
-
-- A web server. Apache (version 2.0 or greater) is recommended.
-- PHP 5.2.4 (or greater) (http://www.php.net/).
-- One of the following databases:
- - MySQL 5.0.15 (or greater) (http://www.mysql.com/).
- - MariaDB 5.1.44 (or greater) (http://mariadb.org/). MariaDB is a fully
- compatible drop-in replacement for MySQL.
- - PostgreSQL 8.3 (or greater) (http://www.postgresql.org/).
- - SQLite 3.4.2 (or greater) (http://www.sqlite.org/).
-
-For more detailed information about Drupal requirements, including a list of
-PHP extensions and configurations that are required, see "System requirements"
-(http://drupal.org/requirements) in the Drupal.org online documentation.
-
-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.org online documentation.
-
-Note that all directories mentioned in this document are always relative to the
-directory of your Drupal installation, and commands are meant to be run from
-this directory (except for the initial commands that create that directory).
-
-OPTIONAL SERVER REQUIREMENTS
-----------------------------
-
-- If you want 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 "Clean URLs with IIS"
- (http://drupal.org/node/3854) in the Drupal.org online documentation.
-
-- If you plan to use XML-based services such as RSS aggregation, you will need
- PHP's XML extension. This extension is enabled by default on most PHP
- installations.
-
-- To serve gzip compressed CSS and JS files on an Apache web server, you will
- need the mod_headers module and the ability to use local .htaccess files.
-
-- Some Drupal functionality (e.g., checking whether Drupal and contributed
- modules need updates, RSS aggregation, etc.) require that the web server be
- able to go out to the web and download information. If you want to use this
- functionality, you need to verify that your hosting provider or server
- configuration allows the web server to initiate outbound connections. Most web
- hosting setups allow this.
-
-INSTALLATION
-------------
-
-1. Download and extract Drupal.
-
- You can obtain the latest Drupal release from http://drupal.org -- the files
- are available in .tar.gz and .zip formats and can be extracted using most
- compression tools.
-
- To download and extract the files, on a typical Unix/Linux command line, use
- the following commands (assuming you want version x.y of Drupal in .tar.gz
- format):
-
- wget http://drupal.org/files/projects/drupal-x.y.tar.gz
- tar -zxvf drupal-x.y.tar.gz
-
- This will create a new directory drupal-x.y/ containing all Drupal files and
- directories. Then, to move the contents of that directory into a directory
- within your web server's document root or your public HTML directory,
- continue with this command:
-
- mv drupal-x.y/* drupal-x.y/.htaccess /path/to/your/installation
-
-2. Optionally, download a translation.
-
- By default, Drupal is installed in English, and further languages may be
- installed later. If you prefer to install Drupal in another language
- initially:
-
- - Download a translation file for the correct Drupal version and language
- from the translation server: http://localize.drupal.org/translate/downloads
-
- - Place the file into your installation profile's translations
- directory. For instance, if you are using the Standard install profile,
- move the .po file into the directory:
-
- profiles/standard/translations/
-
- For detailed instructions, visit http://drupal.org/localize
-
-3. Create the Drupal database.
-
- Because Drupal stores all site information in a database, you must create
- this database in order to install Drupal, and grant Drupal certain database
- privileges (such as the ability to create tables). For details, consult
- INSTALL.mysql.txt, INSTALL.pgsql.txt, or INSTALL.sqlite.txt. You may also
- need to consult your web hosting provider for instructions specific to your
- web host.
-
- Take note of the username, password, database name, and hostname as you
- create the database. You will enter this information during the install.
-
-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, add the
- site maintenance account (the first user, also known as user/1), and provide
- basic web site settings.
-
- During installation, several files and directories need to be created, which
- the install script will try to do automatically. However, on some hosting
- environments, manual steps are required, and the install script will tell
- you that it cannot proceed until you fix certain issues. This is normal and
- does not indicate a problem with your server.
-
- The most common steps you may need to perform are:
-
- a. Missing files directory.
-
- The install script will attempt to create a file storage directory in
- the default location at sites/default/files (the location of the files
- directory may be changed after Drupal is installed).
-
- If auto-creation fails, you can make it work by changing permissions on
- the sites/default directory so that the web server can create the files
- directory within it for you. (If you are creating a multisite
- installation, substitute the correct sites directory for sites/default;
- see the Multisite Configuration section of this file, below.)
-
- For example, on a Unix/Linux command line, you can grant everyone
- (including the web server) permission to write to the sites/default
- directory with this command:
-
- chmod a+w sites/default
-
- Be sure to set the permissions back after the installation is finished!
- Sample command:
-
- chmod go-w sites/default
-
- Alternatively, instead of allowing the web server to create the files
- directory for you as described above, you can create it yourself. Sample
- commands from a Unix/Linux command line:
-
- mkdir sites/default/files
- chmod a+w sites/default/files
-
- b. Missing settings file.
-
- Drupal will try to automatically create a settings.php configuration file,
- which is normally in the directory sites/default (to avoid problems when
- upgrading, Drupal is not packaged with this file). If auto-creation fails,
- you will need to create this file yourself, using the file
- sites/default/default.settings.php as a template.
-
- For example, on a Unix/Linux command line, you can make a copy of the
- default.settings.php file with the command:
-
- cp sites/default/default.settings.php sites/default/settings.php
-
- Next, grant write privileges to the file to everyone (including the web
- server) with the command:
-
- chmod a+w sites/default/settings.php
-
- Be sure to set the permissions back after the installation is finished!
- Sample command:
-
- chmod go-w sites/default/settings.php
-
- c. Write permissions after install.
-
- The install script will attempt to write-protect the settings.php file and
- the sites/default directory after saving your configuration. If this
- fails, you will be notified, and you can do it manually. Sample commands
- from a Unix/Linux command line:
-
- chmod go-w sites/default/settings.php
- chmod go-w sites/default
-
-5. Verify that the site is working.
-
- When the install script finishes, you will be logged in with the site
- maintenance account on a "Welcome" page. If the default Drupal theme is not
- displaying properly and links on the page result in "Page Not Found" errors,
- you may be experiencing problems with clean URLs. Visit
- http://drupal.org/getting-started/clean-urls to troubleshoot.
-
-6. Change file system storage settings (optional).
-
- 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, you can modify the file system path 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).
-
- - Your site runs on a number of web servers behind a load balancer or reverse
- proxy (modify the file system path on each server to point to a shared file
- repository).
-
- - You want to restrict access to uploaded files.
-
- To modify the file system path:
-
- a. Ensure that the new location for the path exists and is writable by the
- web server. For example, to create a new directory named uploads and grant
- write permissions, use the following commands on a Unix/Linux command
- line:
-
- mkdir uploads
- chmod a+w uploads
-
- b. Navigate to Administration > Configuration > Media > File system, and
- enter the desired path. Note that if you want to use private file storage,
- you need to first enter the path for private files and save the
- configuration, and then change the "Default download method" setting and
- save again.
-
- 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.
-
-7. Revoke documentation file permissions (optional).
-
- 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, from a Unix/Linux command line you can use
- the following command:
-
- 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
- Drupal.org online documentation.
-
-8. Set up independent "cron" maintenance jobs.
-
- Many Drupal modules have tasks that must be run periodically, including the
- Search module (building and updating the index used for keyword searching),
- the Aggregator module (retrieving feeds from other sites), and the System
- module (performing routine maintenance and pruning of database tables). These
- tasks are known as "cron maintenance tasks", named after the Unix/Linux
- "cron" utility.
-
- When you install Drupal, its built-in cron feature is enabled, which
- automatically runs the cron tasks periodically, triggered by people visiting
- pages of your site. You can configure the built-in cron feature by navigating
- to Administration > Configuration > System > Cron.
-
- It is also possible to run the cron tasks independent of site visits; this is
- recommended for most sites. To do this, you will need to set up an automated
- process to visit the page cron.php on your site, which executes the cron
- tasks.
-
- The URL of the cron.php page requires a "cron key" to protect against
- unauthorized access. Your site's cron key is automatically generated during
- installation and is specific to your site. The full URL of the page, with the
- cron key, is available in the "Cron maintenance tasks" section of the Status
- report page at Administration > Reports > Status report.
-
- As an example for how to set up this automated process, you can use the
- crontab utility on Unix/Linux systems. The following crontab line uses the
- wget command to visit the cron.php page, and runs each hour, on the hour:
-
- 0 * * * * wget -O - -q -t 1 http://example.com/cron.php?cron_key=YOURKEY
-
- Replace the text "http://example.com/cron.php?cron_key=YOURKEY" in the
- example with the full URL displayed under "Cron maintenance tasks" on the
- "Status report" page.
-
- More information about cron maintenance tasks is available at
- http://drupal.org/cron, and sample cron shell scripts can be found in the
- scripts/ directory. (Note that these scripts must be customized like the
- above example, to add your site-specific cron key and domain name.)
-
-BUILDING AND CUSTOMIZING YOUR SITE
-----------------------------------
-
-A new installation of Drupal defaults to a very basic configuration. To extend
-your site, you use "modules" and "themes". A module is a plugin that adds
-functionality to Drupal, while a theme changes the look of your site. The core
-of Drupal provides several optional modules and themes, and you can download
-more at http://drupal.org/project/modules and http://drupal.org/project/themes
-
-Do not mix downloaded or custom modules and themes with Drupal's core modules
-and themes. Drupal's modules and themes are located in the top-level modules and
-themes directories, while the modules and themes you add to Drupal are normally
-placed in the sites/all/modules and sites/all/themes directories. If you run a
-multisite installation, you can also place modules and themes in the
-site-specific directories -- see the Multisite Configuration section, below.
-
-Never edit Drupal's core modules and themes; instead, use the hooks available in
-the Drupal API. To modify the behavior of Drupal, develop a module as described
-at http://drupal.org/developing/modules. To modify the look of Drupal, create a
-subtheme as described at http://drupal.org/node/225125, or a completely new
-theme as described at http://drupal.org/documentation/theme
-
-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 http://drupal.org/getting-started/6/install/multi-site
-
-For more information on configuring Drupal's file system path in a multisite
-configuration, see step 6 above.
-
-MORE INFORMATION
-----------------
-
-- See the Drupal.org online documentation:
- http://drupal.org/documentation
-
-- For a list of security announcements, see the "Security advisories" 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, visit
- http://drupal.org and click on Community and Support in the top or bottom
- navigation.
diff --git a/LICENSE.txt b/LICENSE.txt
deleted file mode 100644
index 94fb846..0000000
--- a/LICENSE.txt
+++ /dev/null
@@ -1,339 +0,0 @@
- 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.
diff --git a/MAINTAINERS.txt b/MAINTAINERS.txt
deleted file mode 100644
index 35eecf8..0000000
--- a/MAINTAINERS.txt
+++ /dev/null
@@ -1,297 +0,0 @@
-
-Drupal core is built and maintained by the Drupal project community. Everyone is
-encouraged to submit issues and changes (patches) to improve Drupal, and to
-contribute in other ways -- see http://drupal.org/contribute to find out how.
-
-Branch maintainers
-------------------
-
-The Drupal Core branch maintainers oversee the development of Drupal as a whole.
-The branch maintainers for Drupal 7 are:
-
-- Dries Buytaert 'dries' <http://drupal.org/user/1>
-- Angela Byron 'webchick' <http://drupal.org/user/24967>
-
-
-Component maintainers
----------------------
-
-The Drupal Core component maintainers oversee the development of Drupal
-subsystems. See http://drupal.org/contribute/core-maintainers for more
-information on their responsibilities, and to find out how to become a component
-maintainer. Current component maintainers for Drupal 7:
-
-Ajax system
-- Alex Bronstein 'effulgentsia' <http://drupal.org/user/78040>
-- Randy Fay 'rfay' <http://drupal.org/user/30906>
-- Earl Miles 'merlinofchaos' <http://drupal.org/user/26979>
-
-Base system
-- Károly Négyesi 'chx' <http://drupal.org/user/9446>
-- Damien Tournoud 'DamZ' <http://drupal.org/user/22211>
-- Moshe Weitzman 'moshe weitzman' <http://drupal.org/user/23>
-
-Batch system
-- Yves Chedemois 'yched' <http://drupal.org/user/39567>
-
-Cache system
-- Damien Tournoud 'DamZ' <http://drupal.org/user/22211>
-- Nathaniel Catchpole 'catch' <http://drupal.org/user/35733>
-
-Cron system
-- Károly Négyesi 'chx' <http://drupal.org/user/9446>
-- Derek Wright 'dww' <http://drupal.org/user/46549>
-
-Database system
-- Larry Garfield 'Crell' <http://drupal.org/user/26398>
-
- - MySQL driver
- - Larry Garfield 'Crell' <http://drupal.org/user/26398>
- - David Strauss 'David Strauss' <http://drupal.org/user/93254>
-
- - PostgreSQL driver
- - Damien Tournoud 'DamZ' <http://drupal.org/user/22211>
- - Josh Waihi 'fiasco' <http://drupal.org/user/188162>
-
- - Sqlite driver
- - Damien Tournoud 'DamZ' <http://drupal.org/user/22211>
- - Károly Négyesi 'chx' <http://drupal.org/user/9446>
-
-Database update system
-- Károly Négyesi 'chx' <http://drupal.org/user/9446>
-
-Entity system
-- Nathaniel Catchpole 'catch' <http://drupal.org/user/35733>
-- Franz Heinzmann 'Frando' <http://drupal.org/user/21850>
-
-File system
-- Andrew Morton 'drewish' <http://drupal.org/user/34869>
-- Aaron Winborn 'aaron' <http://drupal.org/user/33420>
-
-Form system
-- Károly Négyesi 'chx' <http://drupal.org/user/9446>
-- Alex Bronstein 'effulgentsia' <http://drupal.org/user/78040>
-- Wolfgang Ziegler 'fago' <http://drupal.org/user/16747>
-- Daniel F. Kudwien 'sun' <http://drupal.org/user/54136>
-- Franz Heinzmann 'Frando' <http://drupal.org/user/21850>
-
-Image system
-- Andrew Morton 'drewish' <http://drupal.org/user/34869>
-- Nathan Haug 'quicksketch' <http://drupal.org/user/35821>
-
-Install system
-- David Rothstein 'David_Rothstein' <http://drupal.org/user/124982>
-
-JavaScript
-- ?
-
-Language system
-- Francesco Placella 'plach' <http://drupal.org/user/183211>
-- Daniel F. Kudwien 'sun' <http://drupal.org/user/54136>
-
-Lock system
-- Damien Tournoud 'DamZ' <http://drupal.org/user/22211>
-
-Mail system
-- ?
-
-Markup
-- Jacine Luisi 'Jacine' <http://drupal.org/user/88931>
-- Daniel F. Kudwien 'sun' <http://drupal.org/user/54136>
-
-Menu system
-- Peter Wolanin 'pwolanin' <http://drupal.org/user/49851>
-- Károly Négyesi 'chx' <http://drupal.org/user/9446>
-
-Path system
-- Dave Reid 'davereid' <http://drupal.org/user/53892>
-- Nathaniel Catchpole 'catch' <http://drupal.org/user/35733>
-
-Render system
-- Moshe Weitzman 'moshe weitzman' <http://drupal.org/user/23>
-- Alex Bronstein 'effulgentsia' <http://drupal.org/user/78040>
-- Franz Heinzmann 'Frando' <http://drupal.org/user/21850>
-
-Theme system
-- Earl Miles 'merlinofchaos' <http://drupal.org/user/26979>
-- Alex Bronstein 'effulgentsia' <http://drupal.org/user/78040>
-- Joon Park 'dvessel' <http://drupal.org/user/56782>
-- John Albin Wilkins 'JohnAlbin' <http://drupal.org/user/32095>
-
-Token system
-- Dave Reid 'davereid' <http://drupal.org/user/53892>
-
-XML-RPC system
-- Frederic G. Marand 'fgm' <http://drupal.org/user/27985>
-
-
-Topic coordinators
-------------------
-
-Accessibility
-- Everett Zufelt 'Everett Zufelt' <http://drupal.org/user/406552>
-- Brandon Bowersox 'brandonojc' <http://drupal.org/user/186415>
-
-Documentation
-- Jennifer Hodgdon 'jhodgdon' <http://drupal.org/user/155601>
-
-Security
-- Heine Deelstra 'Heine' <http://drupal.org/user/17943>
-
-Translations
-- Gerhard Killesreiter 'killes' <http://drupal.org/user/83>
-
-User experience and usability
-- Roy Scholten 'yoroy' <http://drupal.org/user/41502>
-- Bojhan Somers 'Bojhan' <http://drupal.org/user/87969>
-
-
-Module maintainers
-------------------
-
-Aggregator module
-- ?
-
-Block module
-- John Albin Wilkins 'JohnAlbin' <http://drupal.org/user/32095>
-
-Blog module
-- ?
-
-Book module
-- Peter Wolanin 'pwolanin' <http://drupal.org/user/49851>
-
-Color module
-- ?
-
-Comment module
-- Nathaniel Catchpole 'catch' <http://drupal.org/user/35733>
-
-Contact module
-- Dave Reid 'davereid' <http://drupal.org/user/53892>
-
-Contextual module
-- Daniel F. Kudwien 'sun' <http://drupal.org/user/54136>
-
-Dashboard module
-- ?
-
-Database logging module
-- Khalid Baheyeldin 'kbahey' <http://drupal.org/user/4063>
-
-Field module
-- Yves Chedemois 'yched' <http://drupal.org/user/39567>
-- Barry Jaspan 'bjaspan' <http://drupal.org/user/46413>
-
-Field UI module
-- Yves Chedemois 'yched' <http://drupal.org/user/39567>
-
-File module
-- Aaron Winborn 'aaron' <http://drupal.org/user/33420>
-
-Filter module
-- Daniel F. Kudwien 'sun' <http://drupal.org/user/54136>
-
-Forum module
-- Lee Rowlands 'larowlan' <http://drupal.org/user/395439>
-
-Help module
-- ?
-
-Image module
-- Nathan Haug 'quicksketch' <http://drupal.org/user/35821>
-
-Locale module
-- Gábor Hojtsy 'Gábor Hojtsy' <http://drupal.org/user/4166>
-
-Menu module
-- ?
-
-Node module
-- Moshe Weitzman 'moshe weitzman' <http://drupal.org/user/23>
-- David Strauss 'David Strauss' <http://drupal.org/user/93254>
-
-OpenID module
-- Vojtech Kusy 'wojtha' <http://drupal.org/user/56154>
-- Heine Deelstra 'Heine' <http://drupal.org/user/17943>
-- Christian Schmidt 'c960657' <http://drupal.org/user/216078>
-- Damien Tournoud 'DamZ' <http://drupal.org/user/22211>
-
-Overlay module
-- Katherine Senzee 'ksenzee' <http://drupal.org/user/139855>
-
-Path module
-- Dave Reid 'davereid' <http://drupal.org/user/53892>
-
-PHP module
-- ?
-
-Poll module
-- ?
-
-Profile module
-- ?
-
-RDF module
-- Stéphane Corlosquet 'scor' <http://drupal.org/user/52142>
-
-Search module
-- Doug Green 'douggreen' <http://drupal.org/user/29191>
-
-Shortcut module
-- David Rothstein 'David_Rothstein' <http://drupal.org/user/124982>
-- Kristof De Jaeger 'swentel' <http://drupal.org/user/107403>
-
-Simpletest module
-- Jimmy Berry 'boombatower' <http://drupal.org/user/214218>
-- Károly Négyesi 'chx' <http://drupal.org/user/9446>
-
-Statistics module
-- Dave Reid 'davereid' <http://drupal.org/user/53892>
-
-Syslog module
-- Khalid Baheyeldin 'kbahey' <http://drupal.org/user/4063>
-
-System module
-- ?
-
-Taxonomy module
-- Jess Myrbo 'xjm' <http://drupal.org/user/65776>
-- Nathaniel Catchpole 'catch' <http://drupal.org/user/35733>
-- Benjamin Doherty 'bangpound' <http://drupal.org/user/100456>
-
-Toolbar module
-- ?
-
-Tracker module
-- David Strauss 'David Strauss' <http://drupal.org/user/93254>
-
-Translation module
-- Francesco Placella 'plach' <http://drupal.org/user/183211>
-
-Trigger module
-- ?
-
-Update module
-- Derek Wright 'dww' <http://drupal.org/user/46549>
-
-User module
-- Moshe Weitzman 'moshe weitzman' <http://drupal.org/user/23>
-- David Strauss 'David Strauss' <http://drupal.org/user/93254>
-
-
-Theme maintainers
------------------
-
-Bartik theme
-- Jen Simmons 'jensimmons' <http://drupal.org/user/140882>
-- Jeff Burns 'Jeff Burnz' <http://drupal.org/user/61393>
-
-Garland theme
-- John Albin Wilkins 'JohnAlbin' <http://drupal.org/user/32095>
-
-Seven theme
-- Jeff Burns 'Jeff Burnz' <http://drupal.org/user/61393>
-
-Stark theme
-- John Albin Wilkins 'JohnAlbin' <http://drupal.org/user/32095>
diff --git a/README.txt b/README.txt
deleted file mode 100644
index 921f99c..0000000
--- a/README.txt
+++ /dev/null
@@ -1,88 +0,0 @@
-
-CONTENTS OF THIS FILE
----------------------
-
- * About Drupal
- * Configuration and features
- * Appearance
- * Developing for Drupal
-
-ABOUT 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 http://drupal.org/, and join the
-Drupal community at http://drupal.org/community.
-
-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:
- http://drupal.com/trademark
-
-CONFIGURATION AND FEATURES
---------------------------
-
-Drupal core (what you get when you download and extract a drupal-x.y.tar.gz or
-drupal-x.y.zip file from http://drupal.org/project/drupal) 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:
- http://drupal.org/documentation
- * Download contributed modules to sites/all/modules to extend Drupal's
- functionality:
- http://drupal.org/project/modules
- * See also: "Developing for Drupal" for writing your own modules, below.
-
-APPEARANCE
-----------
-
-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
- appearance:
- http://drupal.org/project/themes
- * Develop your own theme:
- http://drupal.org/documentation/theme
-
-DEVELOPING FOR DRUPAL
----------------------
-
-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:
- http://drupal.org/project/modules
- * Contribute a patch:
- http://drupal.org/patch/submit
- * Develop your own module:
- http://drupal.org/developing/modules
- * Follow best practices:
- http://drupal.org/best-practices
- * Refer to the API documentation:
- http://api.drupal.org/api/drupal/7
diff --git a/UPGRADE.txt b/UPGRADE.txt
deleted file mode 100644
index c993df7..0000000
--- a/UPGRADE.txt
+++ /dev/null
@@ -1,236 +0,0 @@
-INTRODUCTION
-------------
-This document describes how to:
-
- * Update your Drupal site from one minor 7.x version to another minor 7.x
- version; for example, from 7.8 to 7.9, or from 7.6 to 7.10.
-
- * Upgrade your Drupal site's major version from 6.x to 7.x.
-
-First steps and definitions:
-
- * If you are upgrading to Drupal version x.y, then x is known as the major
- version number, and y is known as the minor version number. The download
- file will be named drupal-x.y.tar.gz (or drupal-x.y.zip).
-
- * All directories mentioned in this document are relative to the directory of
- your Drupal installation.
-
- * Make a full backup of all files, directories, and your database(s) before
- starting, and save it outside your Drupal installation directory.
- Instructions may be found at http://drupal.org/upgrade/backing-up-the-db
-
- * It is wise to try an update or upgrade on a test copy of your site before
- applying it to your live site. Even minor updates can cause your site's
- behavior to change.
-
- * Each new release of Drupal has release notes, which explain the changes made
- since the previous version and any special instructions needed to update or
- upgrade to the new version. You can find a link to the release notes for the
- version you are upgrading or updating to on the Drupal project page
- (http://drupal.org/project/drupal).
-
-UPGRADE PROBLEMS
-----------------
-If you encounter errors during this process,
-
- * Note any error messages you see.
-
- * Restore your site to its previous state, using the file and database backups
- you created before you started the upgrade process. Do not attempt to do
- further upgrades on a site that had update problems.
-
- * Consult one of the support options listed on http://drupal.org/support
-
-More in-depth information on upgrading can be found at http://drupal.org/upgrade
-
-MINOR VERSION UPDATES
----------------------
-To update from one minor 7.x version of Drupal to any later 7.x version, after
-following the instructions in the INTRODUCTION section at the top of this file:
-
-1. Log in as a user with the permission "Administer software updates".
-
-2. Go to Administration > Configuration > Development > Maintenance mode.
- Enable the "Put site into maintenance mode" checkbox and save the
- configuration.
-
-3. Remove all old core files and directories, except for the 'sites' directory
- and any custom files you added elsewhere.
-
- If you made modifications to files like .htaccess or robots.txt, you will
- need to re-apply them from your backup, after the new files are in place.
-
- Sometimes an update includes changes to default.settings.php (this will be
- noted in the release notes). If that's the case, follow these steps:
-
- - Make a backup copy of your settings.php file, with a different file name.
-
- - Make a copy of the new default.settings.php file, and name the copy
- settings.php (overwriting your previous settings.php file).
-
- - Copy the custom and site-specific entries from the backup you made into the
- new settings.php file. You will definitely need the lines giving the
- database information, and you will also want to copy in any other
- customizations you have added.
-
-4. Download the latest Drupal 7.x release from http://drupal.org to a
- directory outside of your web root. Extract the archive and copy the files
- into your Drupal directory.
-
- On a typical Unix/Linux command line, use the following commands to download
- and extract:
-
- wget http://drupal.org/files/projects/drupal-x.y.tar.gz
- tar -zxvf drupal-x.y.tar.gz
-
- This creates a new directory drupal-x.y/ containing all Drupal files and
- directories. Copy the files into your Drupal installation directory:
-
- cp -R drupal-x.y/* drupal-x.y/.htaccess /path/to/your/installation
-
- If you do not have command line access to your server, download the archive
- from http://drupal.org using your web browser, extract it, and then use an
- FTP client to upload the files to your web root.
-
-5. Re-apply any modifications to files such as .htaccess or robots.txt.
-
-6. Run update.php by visiting http://www.example.com/update.php (replace
- www.example.com with your domain name). This will update the core database
- tables.
-
- If you are unable to access update.php do the following:
-
- - Open settings.php with a text editor.
-
- - Find the line that says:
- $update_free_access = FALSE;
-
- - Change it into:
- $update_free_access = TRUE;
-
- - Once the upgrade is done, $update_free_access must be reverted to FALSE.
-
-7. Go to Administration > Reports > Status report. Verify that everything is
- working as expected.
-
-8. Ensure that $update_free_access is FALSE in settings.php.
-
-9. Go to Administration > Configuration > Development > Maintenance mode.
- Disable the "Put site into maintenance mode" checkbox and save the
- configuration.
-
-MAJOR VERSION UPGRADE
----------------------
-To upgrade from a previous major version of Drupal to Drupal 7.x, after
-following the instructions in the INTRODUCTION section at the top of this file:
-
-1. Check on the Drupal 7 status of your contributed and custom modules and
- themes. See http://drupal.org/node/948216 for information on upgrading
- contributed modules and themes. See http://drupal.org/node/895314 for a list
- of modules that have been moved into core for Drupal 7, and instructions on
- how to update them. See http://drupal.org/update/modules for information on
- how to update your custom modules, and http://drupal.org/update/theme for
- custom themes.
-
- You may decide at this point that you cannot upgrade your site, because
- needed modules or themes are not ready for Drupal 7.
-
-2. Update to the latest available version of Drupal 6.x (if your current version
- is Drupal 5.x, you have to upgrade to 6.x first). If you need to update,
- download Drupal 6.x and follow the instructions in its UPGRADE.txt. This
- document only applies for upgrades from 6.x to 7.x.
-
-3. In addition to updating to the latest available version of Drupal 7.x core,
- you must also upgrade all of your contributed modules for Drupal to their
- latest Drupal 6.x versions.
-
-4. Log in as user ID 1 (the site maintenance user).
-
-5. Go to Administer > Site configuration > Site maintenance. Select
- "Off-line" and save the configuration.
-
-6. Go to Administer > Site building > Themes. Enable "Garland" and select it as
- the default theme.
-
-7. Go to Administer > Site building > Modules. Disable all modules that are not
- listed under "Core - required" or "Core - optional". It is possible that some
- modules cannot be disabled, because others depend on them. Repeat this step
- until all non-core modules are disabled.
-
- If you know that you will not re-enable some modules for Drupal 7.x and you
- no longer need their data, then you can uninstall them under the Uninstall
- tab after disabling them.
-
-8. On the command line or in your FTP client, remove the file
-
- sites/default/default.settings.php
-
-9. Remove all old core files and directories, except for the 'sites' directory
- and any custom files you added elsewhere.
-
- If you made modifications to files like .htaccess or robots.txt, you will
- need to re-apply them from your backup, after the new files are in place.
-
-10. If you uninstalled any modules, remove them from the sites/all/modules and
- other sites/*/modules directories. Leave other modules in place, even though
- they are incompatible with Drupal 7.x.
-
-11. Download the latest Drupal 7.x release from http://drupal.org to a
- directory outside of your web root. Extract the archive and copy the files
- into your Drupal directory.
-
- On a typical Unix/Linux command line, use the following commands to download
- and extract:
-
- wget http://drupal.org/files/projects/drupal-x.y.tar.gz
- tar -zxvf drupal-x.y.tar.gz
-
- This creates a new directory drupal-x.y/ containing all Drupal files and
- directories. Copy the files into your Drupal installation directory:
-
- cp -R drupal-x.y/* drupal-x.y/.htaccess /path/to/your/installation
-
- If you do not have command line access to your server, download the archive
- from http://drupal.org using your web browser, extract it, and then use an
- FTP client to upload the files to your web root.
-
-12. Re-apply any modifications to files such as .htaccess or robots.txt.
-
-13. Make your settings.php file writeable, so that the update process can
- convert it to the format of Drupal 7.x. settings.php is usually located in
-
- sites/default/settings.php
-
-14. Run update.php by visiting http://www.example.com/update.php (replace
- www.example.com with your domain name). This will update the core database
- tables.
-
- If you are unable to access update.php do the following:
-
- - Open settings.php with a text editor.
-
- - Find the line that says:
- $update_free_access = FALSE;
-
- - Change it into:
- $update_free_access = TRUE;
-
- - Once the upgrade is done, $update_free_access must be reverted to FALSE.
-
-15. Backup your database after the core upgrade has run.
-
-16. Replace and update your non-core modules and themes, following the
- procedures at http://drupal.org/node/948216
-
-17. Go to Administration > Reports > Status report. Verify that everything is
- working as expected.
-
-18. Ensure that $update_free_access is FALSE in settings.php.
-
-19. Go to Administration > Configuration > Development > Maintenance mode.
- Disable the "Put site into maintenance mode" checkbox and save the
- configuration.
-
-To get started with Drupal 7 administration, visit
-http://drupal.org/getting-started/7/admin
diff --git a/web.config b/web.config
deleted file mode 100644
index 34afd0a..0000000
--- a/web.config
+++ /dev/null
@@ -1,43 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<configuration>
- <system.webServer>
- <!-- Don't show directory listings for URLs which map to a directory. -->
- <directoryBrowse enabled="false" />
- <rewrite>
- <rules>
- <rule name="Protect files and directories from prying eyes" stopProcessing="true">
- <match url="\.(engine|inc|info|install|make|module|profile|test|po|sh|.*sql|theme|tpl(\.php)?|xtmpl)$|^(\..*|Entries.*|Repository|Root|Tag|Template)$" />
- <action type="CustomResponse" statusCode="403" subStatusCode="0" statusReason="Forbidden" statusDescription="Access is forbidden." />
- </rule>
- <rule name="Force simple error message for requests for non-existent favicon.ico" stopProcessing="true">
- <match url="favicon\.ico" />
- <action type="CustomResponse" statusCode="404" subStatusCode="1" statusReason="File Not Found" statusDescription="The requested file favicon.ico was not found" />
- </rule>
- <!-- Rewrite URLs of the form 'x' to the form 'index.php?q=x'. -->
- <rule name="Short URLs" stopProcessing="true">
- <match url="^(.*)$" ignoreCase="false" />
- <conditions>
- <add input="{REQUEST_FILENAME}" matchType="IsFile" ignoreCase="false" negate="true" />
- <add input="{REQUEST_FILENAME}" matchType="IsDirectory" ignoreCase="false" negate="true" />
- <add input="{URL}" pattern="^/favicon.ico$" ignoreCase="false" negate="true" />
- </conditions>
- <action type="Rewrite" url="index.php?q={R:1}" appendQueryString="true" />
- </rule>
- </rules>
- </rewrite>
-
- <httpErrors>
- <remove statusCode="404" subStatusCode="-1" />
- <error statusCode="404" prefixLanguageFilePath="" path="/index.php" responseMode="ExecuteURL" />
- </httpErrors>
-
- <defaultDocument>
- <!-- Set the default document -->
- <files>
- <remove value="index.php" />
- <add value="index.php" />
- </files>
- </defaultDocument>
- </system.webServer>
-</configuration>
-
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment