All necessary changes to %dir and %file have been made, so you should now remove write permissions to them. Failure to remove write permissions to them is a security risk.

All necessary changes to %dir and %file have been made. They have been set to read-only for security.

The @drupal installer requires write permissions to %file during the installation process.

Drupal database setup

Database configuration

Your web server does not appear to support any common database types. Check with your hosting provider to see if they offer any databases that Drupal supports.

Basic options

To set up your @drupal database, enter the following information.

Database type

The type of database your @drupal data will be stored in.

The name of the database your @drupal data will be stored in. It must exist on your server before @drupal can be installed.

The name of the %db_type database your @drupal data will be stored in. It must exist on your server before @drupal can be installed.

Database name

Database username

Database password

Advanced options

These options are only necessary for some sites. If you're not sure what you should enter here, leave the default settings or check with your hosting provider.

Database host

If your database is located on a different server, change this.

Database port

If your database server is listening to a non-standard port, enter its number.

Table prefix

If more than one @drupal website will be sharing this database, enter a table prefix for your @drupal site here.

Save configuration

The database table prefix you have entered, %db_prefix, is invalid. The table prefix can only contain alphanumeric characters, underscores or dots.

Database port must be a number.

In your %settings_file file you have configured @drupal to use a %db_type server, however your PHP installation currently does not support this database type.

In order for Drupal to work and to proceed with the installation process you must resolve all permission issues reported above. We were able to verify that we have permission for the following commands: %commands. For more help with configuring your database server, see the Installation and upgrading handbook. If you are unsure what any of this means you should probably contact your hosting provider.

Select an installation profile

Choose language

With the addition of an appropriate language pack, this installer is capable of proceeding in another language of your choice. To install and use Drupal in a language other than English:

Determine if a translation of this Drupal version is available in your language of choice. A translation is provided via a translation pack; each translation pack enables the display of a specific version of Drupal in a specific language. Not all languages are available for every version of Drupal.

If an alternative language pack of your choice is available, download and extract its contents to your Drupal root directory.

Return to choose language using the second link below and select your desired language from the displayed list. Reloading the page allows the list to automatically adjust to the presence of new language packs.

Alternatively, to install and use Drupal in English, or to defer the selection of an alternative language until after installation, select the first link below.

How should the installation continue?

Continue installation in English

Return to choose a language

Install Drupal in English

Learn how to install Drupal in other languages

(@language)

(built-in)

Select language

No profiles available

We were unable to find any installer profiles. Installer profiles tell us what modules to enable and what schema to install in the database. A profile is necessary to continue with the installation process.

Drupal already installed

To start over, you must empty your existing database.To install to a different database, edit the appropriate settings.php file in the sites folder.To upgrade an existing installation, proceed to the update script.View your existing site.

Modules missing

One or more required modules are missing. Please check the error messages and try again.

Configure site

@drupal installation complete

Congratulations, @drupal has been successfully installed.

Please review the messages above before continuing on to your new site.

You may now visit your new site.

Currently using !item !version

Incompatible environment

Choose profile

Verify requirements

Setup database

Import translations

Finished

To configure your web site, please provide the following information.

Site information

Site name

Site e-mail address

A valid e-mail address to be used as the "From" address by the auto-mailer during registration, new password requests, notifications, etc.  To lessen the likelihood of e-mail being marked as spam, this e-mail address should use the same domain as the website.

Administrator account

The administrator account has complete access to the site; it will automatically be granted all permissions and can perform any administrative activity. This will be the only account that can perform certain activities, so keep its credentials safe.

Username

Spaces are allowed; punctuation is not allowed except for periods, hyphens, and underscores.

E-mail address

All e-mails from the system will be sent to this address. The e-mail address is not made public and will only be used if you wish to receive a new password or wish to receive certain news or notifications by e-mail.

Server settings

Default time zone

By default, dates in this site will be displayed in the chosen time zone.

Your server has been successfully tested to support this feature.

Your system configuration does not currently support this feature. The handbook page on Clean URLs has additional troubleshooting information.

Testing clean URLs...

Clean URLs

Disabled

Enabled

This option makes Drupal emit "clean" URLs (i.e. without ?q= in the URL).

Save

MySQL database

Your MySQL Server is too old. Drupal requires at least MySQL %version.

PostgreSQL database

Your PostgreSQL Server is too old. Drupal requires at least PostgreSQL %version.

Your PostgreSQL database is set up with the wrong character encoding (%encoding). It is possible it will not work as expected. It is advised to recreate it with UTF-8/Unicode encoding. More information can be found in the PostgreSQL documentation.

Processing

Initializing.

Remaining @remaining of @total.

An error has occurred.

Please continue to the error page

Failed to modify %settings, please verify the file permissions.

Failed to open %settings, please verify the file permissions.

The %module module is required but was not found. Please move it into the modules subdirectory.

PHP MySQL support not enabled.

Failure to connect to your MySQL database server. MySQL reports the following message: %error.Are you sure you have the correct username and password?Are you sure that you have typed the correct database hostname?Are you sure that the database server is running?For more help, see the Installation and upgrading handbook. If you are unsure what these terms mean you should probably contact your hosting provider.

We were able to connect to the MySQL database server (which means your username and password are valid) but not able to select your database. MySQL reports the following message: %error.Are you sure you have the correct database name?Are you sure the database exists?Are you sure the username has permission to access the database?For more help, see the Installation and upgrading handbook. If you are unsure what these terms mean you should probably contact your hosting provider.

We were unable to create a test table on your MySQL database server with the command %query. MySQL reports the following message: %error.Are you sure the configured username has the necessary MySQL permissions to create tables in the database?For more help, see the Installation and upgrading handbook. If you are unsure what these terms mean you should probably contact your hosting provider.

We were unable to insert a value into a test table on your MySQL database server. We tried inserting a value with the command %query and MySQL reported the following error: %error.

We were unable to update a value in a test table on your MySQL database server. We tried updating a value with the command %query and MySQL reported the following error: %error.

We were unable to lock a test table on your MySQL database server. We tried locking a table with the command %query and MySQL reported the following error: %error.

We were unable to unlock a test table on your MySQL database server. We tried unlocking a table with the command %query and MySQL reported the following error: %error.

We were unable to delete a value from a test table on your MySQL database server. We tried deleting a value with the command %query and MySQL reported the following error: %error.

We were unable to drop a test table from your MySQL database server. We tried dropping a table with the command %query and MySQL reported the following error %error.

PHP MySQLi support not enabled.

PHP PostgreSQL support not enabled.

Failure to connect to your PostgreSQL database server. PostgreSQL reports the following message: %error.Are you sure you have the correct username and password?Are you sure that you have typed the correct database hostname?Are you sure that the database server is running?Are you sure you typed the correct database name?For more help, see the Installation and upgrading handbook. If you are unsure what these terms mean you should probably contact your hosting provider.

We were unable to create a test table on your PostgreSQL database server with the command %query. PostgreSQL reports the following message: %error.Are you sure the configured username has the necessary PostgreSQL permissions to create tables in the database?For more help, see the Installation and upgrading handbook. If you are unsure what these terms mean you should probably contact your hosting provider.

We were unable to insert a value into a test table on your PostgreSQL database server. We tried inserting a value with the command %query and PostgreSQL reported the following error: %error.

We were unable to update a value in a test table on your PostgreSQL database server. We tried updating a value with the command %query and PostgreSQL reported the following error: %error.

We were unable to lock a test table on your PostgreSQL database server. We tried locking a table with the command %query and PostgreSQL reported the following error: %error.

We were unable to unlock a test table on your PostgreSQL database server. We tried unlocking a table with the command %query and PostgreSQL reported the following error: %error.

We were unable to delete a value from a test table on your PostgreSQL database server. We tried deleting a value with the command %query and PostgreSQL reported the following error: %error.

We were unable to drop a test table from your PostgreSQL database server. We tried dropping a table with the command %query and PostgreSQL reported the following error %error.

The translation import failed, because the file %filename could not be read.

The translation file %filename contains an error: "msgstr" was expected but not found on line %line.

The translation file %filename contains an error: "msgid_plural" was expected but not found on line %line.

The translation file %filename contains a syntax error on line %line.

The translation file %filename contains an error: "msgid" is unexpected on line %line.

The translation file %filename contains an error: "msgstr[]" is unexpected on line %line.

The translation file %filename contains an error: "msgstr" is unexpected on line %line.

The translation file %filename contains an error: there is an unexpected string on line %line.

The translation file %filename ended unexpectedly at line %line.

Importing interface translations

Starting import

Error importing interface translations

Drupal Installation

The following errors must be resolved before you can continue the installation process

The following error must be resolved before you can continue the installation process

The following installation warnings should be carefully reviewed, but in most cases may be safely ignored

The following installation warning should be carefully reviewed, but in most cases may be safely ignored

The PCRE library in your PHP installation is outdated. This will cause problems when handling Unicode text. If you are running PHP 4.3.3 or higher, make sure you are using the PCRE library supplied by PHP. Please refer to the PHP PCRE documentation for more information.

Operations on Unicode strings are emulated on a best-effort basis. Install the PHP mbstring extension for improved Unicode support.

Multibyte string function overloading in PHP is active and must be disabled. Check the php.ini mbstring.func_overload setting. Please refer to the PHP mbstring documentation for more information.

Multibyte string input conversion in PHP is active and must be disabled. Check the php.ini mbstring.encoding_translation setting. Please refer to the PHP mbstring documentation for more information.

Multibyte string input conversion in PHP is active and must be disabled. Check the php.ini mbstring.http_input setting. Please refer to the PHP mbstring documentation for more information.

Multibyte string output conversion in PHP is active and must be disabled. Check the php.ini mbstring.http_output setting. Please refer to the PHP mbstring documentation for more information.

Standard PHP

PHP Mbstring Extension

Error

Unicode library

Drupal

Web server

Your Apache server is too old. Drupal requires at least Apache %version.

The web server you're using has not been tested with Drupal and might not work properly.

Unknown

Unable to determine your web server type and version. Drupal might not work properly.

PHP

Your PHP installation is too old. Drupal requires at least PHP %version.

Not protected

The directory %file is not protected from modifications and poses a security risk. You must change the directory's permissions to be non-writable. 

The file %file is not protected from modifications and poses a security risk. You must change the file's permissions to be non-writable.

Protected

Configuration file

Last run !time ago

Cron has not run. It appears cron jobs have not been setup on your system. Please check the help pages for configuring cron jobs.

Never run

You can run cron manually.

Cron maintenance tasks

The directory %directory does not exist.

The directory %directory is not writable.

Not writable

You may need to set the correct directory at the file system settings page or change the current directory's permissions so that it is writable.

Writable (public download method)

Writable (private download method)

File system

Database updates

Up to date

Out of date

Some modules have database schema updates to install. You should run the database update script immediately.

The update.php script is accessible to everyone without authentication check, which is a security risk. You must change the $update_free_access value in your settings.php back to FALSE.

Access to update.php

Page

If you want to add a static page, like a contact page or an about page, use a page.

Story

Stories are articles in their simplest form: they have a title, a teaser and a body, but can be extended by other modules. The teaser is part of the body too. Stories may be used as a personal blog or for news articles.

Updating @module module

Remove orphaned actions

actions

Stack overflow: too many calls to actions_do(). Aborting to prevent infinite recursion.

Action '%action' added.

Removed orphaned action '%action' from database.

Action %action saved.

Action %action created.

One orphaned action (%orphans) exists in the actions table. !link

@count orphaned actions (%orphans) exist in the actions table. !link

HTTP POST is required.

Site off-line

@site is currently under maintenance. We should be back shortly. Thank you for your patience.

Page not found

Access denied

You are not authorized to access this page.

KB

MB

@size @suffix

0 sec

emergency

alert

critical

error

warning

notice

info

debug

php

%message in %file on line %line.

cron

Cron has been running for more than an hour and is most likely stuck.

Attempting to re-run cron while it is already running.

Cron run completed.

Cron run exceeded the time limit and was aborted.

1 byte

@count bytes

1 year

@count years

1 week

@count weeks

1 day

@count days

1 hour

@count hours

1 min

@count min

1 sec

@count sec

The directory %directory has been created.

The permissions of directory %directory have been changed to make it writable.

The directory %directory is not writable

Security warning: Couldn't write .htaccess file. Please create a .htaccess file in your %directory directory which contains the following lines: !htaccess

The selected file %file could not be uploaded, because the destination %directory is not properly configured.

The selected file %file could not be copied, because no file by that name exists. Please check that you supplied the correct filename.

The selected file %file could not be copied, because a file by that name already exists in the destination.

The selected file %file could not be copied.

The removal of the original file %file has failed.

For security reasons, your upload has been renamed to %filename.

The file %file could not be saved, because it exceeds %maxsize, the maximum allowed size for uploads.

The file %file could not be saved, because the upload did not complete.

The file %file could not be saved. An unknown error has occurred.

The selected file %name could not be uploaded. 

File upload error. Could not move uploaded file.

Its name exceeds the 255 characters limit. Please rename the file and try again.

Only files with the following extensions are allowed: %files-allowed.

The file is %filesize exceeding the maximum file size of %maxsize.

The file is %filesize which would exceed your disk quota of %quota.

Only JPEG, PNG and GIF images are allowed.

The image was resized to fit within the maximum allowed dimensions of %dimensions pixels.

The image is too large; the maximum dimensions are %dimensions pixels.

The image is too small; the minimum dimensions are %dimensions pixels.

The file could not be created.

file system

The directory %directory is not writable, because it does not have the correct permissions set.

security

The selected file %file could not be uploaded, because the destination %directory could not be found, or because its permissions do not allow the file to be written.

file

Upload error. Could not move uploaded file %file to destination %destination.

Validation error, please try again. If this error persists, please contact the site administrator.

!name field is required.

!name cannot be longer than %max characters but is currently %length characters long.

An illegal choice has been detected. Please contact the site administrator.

Password

Confirm password

The specified passwords do not match.

Password field is required.

The specified date is invalid.

This field is required.

!title: !required

form

Illegal choice %choice in !name element.

Illegal choice %choice in %name element.

GD2 image manipulation toolkit

The GD toolkit is installed and working properly.

JPEG quality

Define the image quality for JPEG manipulations. Ranges from 0 to 100. Higher values mean better image quality but bigger files.

%

The GD image toolkit requires that the GD module for PHP be installed and configured properly. For more information see PHP's image documentation.

The selected image handling toolkit %toolkit can not correctly process %function.

edit

delete

Code

English name

Native name

Direction

Default

Weight

Operations

Configuration saved.

Predefined language

Language name

Select the desired language here, or add it below, if you are unable to find it in the list.

Add language

Custom language

Add custom language

Save language

Language code

This should be an RFC 4646 compliant language identifier. Basic tags use a country code with an optional script or regional variant name, like "en", "en-US" and "zh-Hant".

Language name in English

Name of the language. Will be available for translation in all languages.

Native language name

Name of the language in the language being added.

Path prefix

Optional path prefix, for example "deutsch" for the German version. This value is not used in the "None" and "Domain" negotiation schemes. You can leave this empty if you use "Path only" negotiation and this is the default language. Changing this will break existing URLs.

Language domain

Optional custom domain with protocol (eg. "http://example.de" or "http://de.example.com" for the German version). This value is only used in the "Domain" negotiation mode. If left empty and in "Domain" mode, this language will not be accessible.

Direction of the text being written in this language.

Left to right

Right to left

The language %language (%code) already exists.

Invalid language code.

The language %language has been created and can now be used. More information is available on the help screen.

Domain and path prefix values should not be set at the same time.

The domain (%domain) is already tied to a language (%language).

Only the default language can have both the domain and prefix empty.

The prefix (%prefix) is already tied to a language (%language).

The English language cannot be deleted.

The default language cannot be deleted.

Are you sure you want to delete the language %name?

Deleting a language will remove all interface translations associated with it, and posts in this language will be set to be language neutral. This action cannot be undone.

Delete

Cancel

The language %locale has been removed.

Language negotiation

None. Language will be independent of visitor preferences and language prefixes or domains.

Path prefix only. If a suitable path prefix is not identified, the default language is used.

Path prefix with language fallback. If a suitable  path prefix is not identified, language is based on user preferences and browser language settings.

Domain name only. If a suitable domain name is not identified, the default language is used.

The used language detection mode. Changing this also changes how paths are constructed, so setting a different value breaks all incoming links. Do not change on a live site without thinking twice!

Save settings

Language negotiation configuration saved.

Language

English (built-in)

n/a

Search

String contains

Leave blank to show all strings. The search is case sensitive.

All languages

English (provided by Drupal)

Search in

Both translated and untranslated strings

Only translated strings

Only untranslated strings

Limit search to

All text groups

Already added languages

Languages not yet added

Import translation

Language file

A gettext Portable Object (.po) file.

Import into

Choose the language you want to add strings into. If you choose a language which is not yet set up, it will be added.

Text group

Imported translations will be added to this text group.

Mode

Strings in the uploaded file replace existing ones, new ones are added

Existing strings are kept, only new strings are added

Import

The language %language has been created.

The translation import of %filename failed.

File to import not found.

Export translation

Select the language you would like to export in gettext Portable Object (.po) format.

Export

Export template

Generate a gettext Portable Object Template (.pot) file with all strings from the Drupal locale database.

String not found.

Original text

Save translations

The string has been saved.

The string has been removed.

The language selected for import is not supported.

The translation file %filename appears to have a missing or malformed header.

The translation was successfully imported. There are %number newly created translated strings, %update strings were updated and %delete strings were removed.

The translation file %filename contains an error: the plural formula could not be parsed.

String

Languages

No strings found for your search.

locale

The %language language (%code) has been created.

Imported %file into %locale: %number new strings added, %update updated and %delete removed.

Parsed JavaScript file %file.

Exported %locale translation file: %filename.

Exported translation file: %filename.

Updated JavaScript translation file for the language %language.

Created JavaScript translation file for the language %language.

An error occurred during creation of the JavaScript translation file for the language %language.

Deleted JavaScript translation file for the locale %language.

One translation file imported for the newly installed modules.

@count translation files imported for the newly installed modules.

One translation file imported for the enabled modules.

@count translation files imported for the enabled modules.

Afar

Abkhazian

Avestan

Afrikaans

Akan

Amharic

Arabic

Assamese

Avar

Aymara

Azerbaijani

Bashkir

Belarusian

Bulgarian

Bihari

Bislama

Bambara

Bengali

Tibetan

Breton

Bosnian

Catalan

Chechen

Chamorro

Corsican

Cree

Czech

Old Slavonic

Chuvash

Welsh

Danish

German

Maldivian

Bhutani

Ewe

Greek

English

Esperanto

Spanish

Estonian

Basque

Persian

Fulah

Finnish

Fiji

Faeroese

French

Frisian

Irish

Scots Gaelic

Galician

Guarani

Gujarati

Manx

Hausa

Hebrew

Hindi

Hiri Motu

Croatian

Hungarian

Armenian

Herero

Interlingua

Indonesian

Interlingue

Igbo

Inupiak

Icelandic

Italian

Inuktitut

Japanese

Javanese

Georgian

Kongo

Kikuyu

Kwanyama

Kazakh

Greenlandic

Cambodian

Kannada

Korean

Kanuri

Kashmiri

Kurdish

Komi

Cornish

Kirghiz

Latin

Luxembourgish

Luganda

Lingala

Laothian

Lithuanian

Latvian

Malagasy

Marshallese

Maori

Macedonian

Malayalam

Mongolian

Moldavian

Marathi

Malay

Maltese

Burmese

Nauru

North Ndebele

Nepali

Ndonga

Dutch

Norwegian Bokmål

Norwegian Nynorsk

South Ndebele

Navajo

Chichewa

Occitan

Oromo

Oriya

Ossetian

Punjabi

Pali

Polish

Pashto

Portuguese, Portugal

Portuguese, Brazil

Quechua

Rhaeto-Romance

Kirundi

Romanian

Russian

Kinyarwanda

Sanskrit

Sardinian

Sindhi

Northern Sami

Sango

Serbo-Croatian

Singhalese

Slovak

Slovenian

Samoan

Shona

Somali

Albanian

Serbian

Siswati

Sesotho

Sudanese

Swedish

Swahili

Tamil

Telugu

Tajik

Thai

Tigrinya

Turkmen

Tagalog

Setswana

Tonga

Turkish

Tsonga

Tatar

Twi

Tahitian

Uighur

Ukrainian

Urdu

Uzbek

Venda

Vietnamese

Wolof

Xhosa

Yiddish

Yoruba

Zhuang

Chinese, Simplified

Chinese, Traditional

Zulu

Unable to send e-mail. Please contact the site admin, if the problem persists.

mail

Error sending e-mail (from %from to %to).

Home

Operating in off-line mode.

« first

‹ previous

next ›

last »

Go to first page

Go to previous page

Go to next page

Go to last page

Go to page @number

sort by @s

sort icon

sort ascending

sort descending

new

updated

[more help...]

XML feed

Syndicate content

View user profile.

not verified

Anonymous

Could not convert XML encoding %s to UTF-8.

Unsupported encoding %s. Please install iconv, GNU recode or mbstring for PHP.

Parse error. Not well formed

Parse error. Request not well formed.

Server error. Invalid XML-RPC. Request must be a methodCall.

Server error. Requested method %methodname not specified.

Server error. Wrong number of method parameters.

Server error. Invalid method parameters.

Server error. Requested function %method does not exist.

Invalid syntax for system.multicall.

Recursive calls to system.multicall are forbidden.

Server error. Requested method %methodname signature not specified.

An error occurred:\n\n@error

An HTTP error @status occured. 
@uri

Unspecified error

Select all rows in this table

Deselect all rows in this table

Split summary at cursor

Join summary

URL:

Updated:

Categories

More

Feed overview

Title

Items

Last update

Next update

@time ago

never

%time left

remove items

update items

Category overview

The name of the feed; typically the name of the website you syndicate content from.

URL

The fully-qualified URL of the feed.

Update interval

The refresh interval indicating how often you want to update this feed. Requires crontab.

Categorize news items

New items in this feed will be automatically filed in the checked categories as they are received.

The URL %url is invalid. Please enter a fully-qualified URL, such as http://www.example.com/feed.xml.

A feed named %feed already exists. Please enter a unique title.

A feed with this URL %url already exists. Please enter a unique URL.

The feed %feed has been updated.

The feed %feed has been deleted.

view

The feed %feed has been added.

none

Allowed HTML tags

The list of tags which are allowed in feeds, i.e., which will not be removed by Drupal.

Items shown in sources and categories pages

The number of items which will be shown with each feed or category in the feed and category summary pages.

Discard news items older than

Older news items will be automatically discarded. Requires crontab.

Category selection type

checkboxes

multiple selector

The type of category selection widget which is shown on categorization pages. Checkboxes are easier to use; a multiple selector is good for working with large numbers of categories.

Description

A category named %category already exists. Please enter a unique title.

The category %category has been updated.

The category %category has been deleted.

The category %category has been added.

aggregator

Feed %feed deleted.

Feed %feed added.

Category %category deleted.

Category %category added.

1 item

@count items

aggregator - @title

Save categories

You are not allowed to categorize this feed item.

The categories have been saved.

Categorize

%ago ago

OPML feed

in category

read more

aggregated feeds

%age old

!title feed

The news aggregator is a powerful on-site RSS syndicator/news reader that can gather fresh content from news sites and weblogs around the web.

Users can view the latest news chronologically in the main news aggregator display or by source. Administrators can add, edit and delete feeds and choose how often to check for newly updated news for each individual feed. Administrators can also tag individual feeds with categories, offering selective grouping of some feeds into separate displays. Listings of the latest news for individual sources or categorized sources can be enabled as blocks for display in the sidebar through the block administration page. The news aggregator requires cron to check for the latest news from the sites to which you have subscribed. Drupal also provides a machine-readable OPML file of all of your subscribed feeds.

For more information please read the configuration and customization handbook Aggregator page.

Thousands of sites (particularly news sites and weblogs) publish their latest headlines and/or stories in a machine-readable format so that other sites can easily link to them. This content is usually in the form of an RSS feed (which is an XML-based syndication standard). To display the feed or category in a block you must decide how many items to show by editing the feed or block and turning on the feed's block.

Add a site that has an RSS/RDF/Atom feed. The URL is the full path to the feed file. For the feed to update automatically you must run "cron.php" on a regular basis. If you already have a feed with the URL you are planning to use, the system will not accept another feed with the same URL.

Categories provide a way to group items from different news feeds together. Each news category has its own feed page and block. For example, you could tag various sport-related feeds as belonging to a category called Sports. News items can be added to a category automatically by setting a feed to automatically place its item into that category, or by using the categorize items link in any listing of news items.

!title category latest items

!title feed latest items

Number of news items in block

more

View this feed's recent news.

View this category's recent news.

The news items from %site have been removed.

There is no new syndicated content from %site.

There is new syndicated content from %site.

The feed from %site seems to be broken, because of error "%error".

The feed from %site seems to be broken, because of error "%error" on line %line.

blog it

Comment on this news item in your personal blog.

Updated URL for feed %title to %url.

The feed from %site seems to be broken, due to "%error".

The feed from %site seems to be broken, due to an error "%error" on line %line.

administer news feeds

access news feeds

News aggregator

Configure which content your site aggregates from other sites, how often it polls them, and how they're categorized.

Add feed

Add category

Remove items

Update items

List

Settings

Sources

RSS feed

View

Configure

Edit feed

Edit category

Stores categories for aggregator feeds and feed items.

Primary Key: Unique aggregator category ID.

Title of the category.

Description of the category

The number of recent items to show within the category block.

Bridge table; maps feeds to categories.

The feed's {aggregator_feed}.fid.

The {aggregator_category}.cid to which the feed is being assigned.

Bridge table; maps feed items to categories.

The feed item's {aggregator_feed_item}.iid.

The {aggregator_category}.cid to which the feed item is being assigned.

Stores feeds to be parsed by the aggregator.

Primary Key: Unique feed ID.

Title of the feed.

URL to the feed.

How often to check for new feed items, in seconds.

Last time feed was checked for new items, as Unix timestamp.

The parent website of the feed; comes from the  element in the feed.

The parent website's description; comes from the  element in the feed.

An image representing the feed.

Entity tag HTTP response header, used for validating cache.

When the feed was last modified, as a Unix timestamp.

Number of items to display in the feed's block.

Stores the individual items imported from feeds.

Primary Key: Unique ID for feed item.

The {aggregator_feed}.fid to which this item belongs.

Title of the feed item.

Link to the feed item.

Author of the feed item.

Body of the feed item.

Post date of feed item, as a Unix timestamp.

Unique identifier for the feed item.

Aggregator

Aggregates syndicated content (RSS, RDF, and Atom feeds).

Core - optional

Block

Region

Throttle

configure

Save blocks

The block settings have been updated.

Your settings will not be saved until you click the Save blocks button.

Block specific settings

Block title

The title of the block as shown to the user.

Override the default title for the block. Use <none> to display no title, or leave blank to use the default block title.

'%name' block

User specific visibility settings

Custom visibility settings

Users cannot control whether or not they see this block.

Show this block by default, but let individual users hide it.

Hide this block by default but let individual users show it.

Allow individual users to customize the visibility of this block in their account settings.

Role specific visibility settings

Show block for specific roles

Show this block only for the selected role(s). If you select no roles, the block will be visible to all users.

Page specific visibility settings

Show on every page except the listed pages.

Show on only the listed pages.

Enter one page per line as Drupal paths. The '*' character is a wildcard. Example paths are %blog for the blog page and %blog-wildcard for every personal blog. %front is the front page.

Show if the following PHP code returns TRUE (PHP-mode, experts only).

If the PHP-mode is chosen, enter PHP code between %php. Note that executing incorrect PHP-code can break your Drupal site.

Show block on specific pages

Pages

Save block

Please ensure that each block description is unique.

The block configuration has been saved.

The block has been created.

Are you sure you want to delete the block %name?

The block %name has been removed.

Blocks are boxes of content that may be rendered into certain regions of your web pages, for example, into sidebars. Blocks are usually generated automatically by modules (e.g., Recent Forum Topics), but administrators can also define custom blocks.

The region each block appears in depends on both which theme you are using (some themes allow greater control over block placement than others), and on the settings in the block administration section.

The block administration screen lets you specify the vertical placement of the blocks within a region. You do this by assigning a weight to each block. Lighter blocks (those having a smaller weight) "float up" towards the top of the region; heavier ones "sink".

A block's visibility depends on:

Its region placement. Blocks with no region assigned to them are never shown.
Its throttle checkbox when throttle module is enabled. Throttled blocks are hidden during high server loads.
Its page visibility settings. Blocks can be configured to be visible/hidden on certain pages.
Its custom visibility settings. Blocks can be configured to be visible only when specific conditions are true.
Its user visibility settings. Administrators can choose to let users decide whether to show/hide certain blocks.
Its user-role visibility settings. Administrators can choose to let blocks be visible only for certain user roles.
Its function. Some dynamic blocks, such as those generated by modules, will be displayed only on certain pages.



Module blocks

Some modules generate blocks that become available when the modules are enabled. These blocks can be administered via the blocks administration page.

Administrator defined blocks

Administrators can also define custom blocks. These blocks consist of a title, a description, and a body which can be as long as you wish. Block content can be in any of the input formats supported for other content.

For more information please read the configuration and customization handbook Block page.

Blocks are boxes of content that may be rendered into certain regions of your web pages, for example, into sidebars. They are usually generated automatically by modules, but administrators can create blocks manually.
Only enabled blocks are shown. You can position blocks by specifying which area of the page they should appear in (e.g., a sidebar).  Highlighted labels on this page show the regions into which blocks can be rendered. You can specify where within a region a block will appear by adjusting its weight.
If you want certain blocks to disable themselves temporarily during high server loads, check the "Throttle" box. You can configure the auto-throttle on the throttle configuration page after having enabled the throttle module.
You can configure the behaviour of each block (for example, specifying on which pages and for what users it will appear) by clicking the "configure" link for each block.

Here you can create a new block. Once you have created this block you must make it active and give it a place on the page using blocks. The description is used in the "block" column on the blocks page.

Block description

A brief description of your block. Used on the block overview page.

Block body

The content of the block as shown to the user.

Block configuration

administer blocks

use PHP for block visibility

Blocks

Configure what block content appears in your site's sidebars and other regions.

Javascript List Form

Configure block

Delete block

Add block

block

Stores block settings, such as region and visibility settings.

Primary Key: Unique block ID.

The module from which the block originates; for example, 'user' for the Who's Online block, and 'block' for any custom blocks.

Unique ID for block within a module.

The theme under which the block settings apply.

Block enabled status. (1 = enabled, 0 = disabled)

Block weight within region.

Theme region within which the block is set.

Flag to indicate how users may control visibility of the block. (0 = Users cannot control, 1 = On by default, but can be hidden, 2 = Hidden by default, but can be shown)

Flag to indicate whether or not to remove block when website traffic is high. (1 = throttle, 0 = do not throttle)

Flag to indicate how to show blocks on pages. (0 = Show on all pages except listed pages, 1 = Show only on listed pages, 2 = Use custom PHP code to determine visibility)

Contents of the "Pages" block; contain either a list of paths on which to include/exlclude the block or PHP code, depending on "visibility" setting.

Custom title for the block. (Empty string will use block default title,  will remove the title, text will cause block to use specified title.)

Binary flag to indicate block cache mode. (-1: Do not cache, 1: Cache per role, 2: Cache per user, 4: Cache per page, 8: Block cache global) See BLOCK_CACHE_* constants in block.module for more detailed information.

Sets up access permissions for blocks based on user roles

The block's origin module, from {blocks}.module.

The block's unique delta within module, from {blocks}.delta.

The user's role ID from {user_roles}.rid.

Stores contents of custom-made blocks.

The block's {block}.bid.

Block contents.

Block description.

Block body's {filter_formats}.format; for example, 1 = Filtered HTML.

Cache table for the Block module to store already built blocks, identified by module, delta, and various contexts which may change the block, such as theme, locale, and caching mode defined for the block.

Controls the boxes that are displayed around the main content.

Core - required

@name's blog

Post new blog entry.

You are not allowed to post a new blog entry.

RSS - !title

RSS - blogs

Blog entry

A blog is a regularly updated journal or diary made up of individual posts shown in reversed chronological order. Each member of the site may create and maintain a blog.

Blog

View recent blog entries

Read @username's latest blog entries.

The blog module allows registered users to maintain an online weblog (commonly known as a blog), often referred to as an online journal or diary. Blogs are made up of individual posts that are time stamped and are typically viewed by date as you would a diary. Blogs often contain links to web pages users have read and/or agree/disagree with.

The blog module adds a user blogs navigation link to the site, which takes any visitor to a page that displays the most recent blog entries from all the users on the site. The navigation menu has a create a blog entry link (which takes you to a submission form) and a view personal blog link (which displays your blog entries as other people will see them). The blog module also creates a recent blog posts block that can be enabled.

If a user has the ability to post blogs, then the import module (news aggregator) will display a blog-it link next to each news item in its lists. Clicking on this takes the user to the blog submission form, with the title, a link to the item, and a link to the source into the body text already in the text box, ready for the user to add a comment or explanation. This actively encourages people to add blog entries about things they see and hear elsewhere in the website and from your syndicated partner sites.

For more information please read the configuration and customization handbook Blog page.

Blogs

@username's blog

Recent blog posts

Read the latest blog entries.

edit own blog

My blog

blog

Enables keeping easily and regularly updated user web pages or blogs.

The blog API module enables a post to be posted to a site via external GUI applications. Many users prefer to use external tools to improve their ability to read and post responses in a customized way. The blog api provides users the freedom to use the blogging tools they want but still have the blogging server of choice.

When this module is enabled and configured you can use programs like Ecto to create and publish posts from your desktop. Blog API module supports several XML-RPC based blogging APIs such as the Blogger API, MetaWeblog API, and most of the Movable Type API. Any desktop blogging tools or other services (e.g. Flickr's "post to blog") that support these APIs should work with this site.

This module also allows site administrators to configure which content types can be posted via the external applications. So, for instance, users can post forum topics as well as blog posts. Where supported, the external applications will display each content type as a separate "blog".

For more information please read the configuration and customization handbook BlogApi page.

Returns a list of weblogs to which an author has posting privileges.

Returns information about an author in the system.

Creates a new post, and optionally publishes it.

Updates the information about an existing post.

Returns information about a specific post.

Deletes a post.

Returns a list of the most recent posts in the system.

Updates information about an existing post.

Uploads a file to your webserver.

Returns a list of all categories to which the post is assigned.

Returns a bandwidth-friendly list of the most recent posts in the system.

Returns a list of all categories defined in the weblog.

Sets the categories for a post.

Retrieve information about the XML-RPC methods supported by the server.

Retrieve information about the text formatting plugins supported by the server.

Publish (rebuild) all of the static files related to an entry from your weblog. Equivalent to saving an entry in the system (but without the ping).

You do not have permission to create the type of post you wanted to create.

Error storing post.

You do not have permission to update this post.

No file sent.

Error storing file.

Invalid post.

You either tried to edit somebody else's blog or you don't have permission to edit your own blog.

Wrong username or password.

Blog types

Select the content types for which you wish to enable posting via blogapi. Each type will appear as a different "blog" in the client application (if supported).

RSD

content

@type: added %title using blog API.

@type: updated %title using blog API.

Blog APIs

Configure which content types and engines external blog clients can use.

blogapi

Blog API

Allows users to post content using applications that support XML-RPC blog APIs.

edit order and titles

Book

Allowed book outline types

Select content types which users with the %add-perm permission will be allowed to add to the book hierarchy. Users with the %outline-perm permission can add all content types.

add content to books

administer book outlines

Default child page type

The content type for the %add-child link must be one of those selected as an allowed book outline type.

Add child page

Save book pages

Title changed from %original to %current.

Weight changed from %original to %current.

Updated book %title.

Your changes will not be saved until you click the Save book pages button.

book: updated %title.

Unknown export format.

Update book outline

Add to book outline

Remove from book outline

No changes were made

The post has been added to the selected book. You may now position it relative to other pages.

The book outline has been updated.

There was an error adding the post to the book.

%title has associated child pages, which will be relocated automatically to maintain their connection to the book. To recreate the hierarchy (as it was before removing this page), %title may be added again using the Outline tab, and each of its former child pages will need to be relocated manually.

%title may be added to hierarchy again using the Outline tab.

Are you sure you want to remove %title from the book hierarchy?

Remove

The post has been removed from the book.

Printer-friendly version

Show a printer-friendly version of this book page and its sub-pages.

Book navigation

Show block on all pages

Show block only on book pages

Book navigation block display

If Show block on all pages is selected, the block will contain the automatically generated menus for all of the site's books. If Show block only on book pages is selected, the block will contain only the one menu corresponding to the current page's book. In this case, if the current page is not in a book, no block will be displayed.  The Page specific visibility settings or other visibility settings can be used in addition to selectively display this block.

Change book (update list of parents)

This is the top-level page in this book.

This will be the top-level page in this book.

No book selected.

Parent item

The parent page in the book. The maximum depth for a book and all child pages is !maxdepth.  Some pages in the selected book may not be available as parents if selecting them would exceed this limit.

Book outline

Pages at a given level are ordered first by weight and then by title.

create a new book

Your page will be a part of the selected book.

%title is part of a book outline, and has associated child pages. If you proceed with deletion, the child pages will be relocated automatically.

‹ 

up

Go to parent page

 ›

The book module is suited for creating structured, multi-page hypertexts such as site resource guides, manuals, and Frequently Asked Questions (FAQs). It permits a document to have chapters, sections, subsections, etc. Authors with suitable permissions can add pages to a collaborative book,  placing them into the existing document by adding them to a table of contents menu.

Pages in the book hierarchy have navigation elements at the bottom of the page for moving through the text.  These link to the previous and next pages in the book, as well as a link labeled up, leading to the level above in the structure.  More comprehensive navigation may be provided by enabling the book navigation block on the block administration page.

Users can select the printer-friendly version link visible at the bottom of a book page to generate a printer-friendly display of the page and all of its subsections. 

Users with the administer book outlines permission can add content of any type to a book, placing it into the existing book structure through the edit form or through the interface that's available by clicking on the outline tab while viewing that post.

Administrators can view a list of all books on the book administration page.  In this list there is a link to an outline page for each book, from which is it possible to change the titles of sections, or to change their weight, thus reordering sections.

For more information please read the configuration and customization handbook Book page.

The book module offers a means to organize content, authored by many users, in an online manual, outline or FAQ.

The outline feature allows you to include posts in the book hierarchy, as well as move them within the hierarchy or to reorder an entire book.

create new books

access printer-friendly version

Books

Manage your site's book outlines.

Re-order book pages and change titles

Outline

Remove from outline

book

Book page

A static page. These posts (as well as other types) may be added to a book outline to create a hierarchical structure for your site.

Relocated orphan book pages.

Relocated existing book pages.

Stores book outline information. Uniquely connects each node in the outline to a link in {menu_links}

The book page's {menu_links}.mlid.

The book page's {node}.nid.

The book ID is the {book}.nid of the top-level page.

Allows users to structure site pages in a hierarchy or outline.

Updating parents...

Color module allows a site administrator to quickly and easily change the color scheme of the entire site. In order for color module to work however, a theme must be specifically designed to use the color changing features. The default theme, Garland, (as well as its fixed width counterpart, Minnelli) was designed to take advantage of these features. With color module, you can easily change the color of links, backgrounds, text, and more depending on which color module enabled theme you are using. Color module requires your file download method to be set to public.

It is important to remember that color module saves a modified copy of the theme's style.css file in the files directory, and includes it after the theme's original style.css. This means that if you make any manual changes to your theme's style.css file, you must save your color settings again, even if they haven't changed. This causes the color module generated version of style.css in the files directory to be recreated using the new version of the original file.

Color scheme

Custom

Color set

Base color

Link color

Header top

Header bottom

Text color

Preview

There is not enough memory available to PHP to change this theme's color scheme. You need at least %size more. Check the PHP documentation for more information.

Reset to defaults

color

The GD library for PHP is enabled, but was compiled without PNG support. Please check the PHP image documentation for information on how to correct this.

Not installed

The GD library for PHP is missing or outdated. Please check the PHP image documentation for information on how to correct this.

GD library

Color

Allows the user to change the color scheme of certain themes.

by

The comment module creates a discussion board for each post. Users can post comments to discuss a forum topic, weblog post, story, collaborative book page, etc. The ability to comment is an important part of involving members in a community dialogue.

An administrator can give comment permissions to user groups, and users can (optionally) edit their last comment, assuming no others have been posted since. Attached to each comment board is a control panel for customizing the way that comments are displayed. Users can control the chronological ordering of posts (newest or oldest first) and the number of posts to display on each page. Comments behave like other user submissions. Filters, smileys and HTML that work in nodes will also work with comments. The comment module provides specific features to inform site members when new comments have been posted.

For more information please read the configuration and customization handbook Comment page.

Below is a list of the latest comments posted to your site. Click on a subject to see the comment, the author's name to edit the author's user information , 'edit' to modify the text, and 'delete' to remove their submission.

Below is a list of the comments posted to your site that need approval. To approve a comment, click on 'edit' and then change its 'moderation status' to Approved. Click on a subject to see the comment, the author's name to edit the author's user information, 'edit' to modify the text, and 'delete' to remove their submission.

Recent comments

Jump to the first comment of this posting.

Jump to the first new comment of this posting.

Add new comment

Add a new comment to this page.

Share your thoughts and opinions related to this posting.

Comment settings

Default comment setting

Read only

Read/Write

Users with the administer comments permission will be able to override this setting.

Default display mode

The default view for comments. Expanded views display the body of the comment. Threaded views keep replies together.

Default display order

The default sorting for new users and anonymous users while viewing comments. These users may change their view using the comment control panel. For registered users, this change is remembered as a persistent user preference.

Default comments per page

Default number of comments for each page: more comments are distributed in several pages.

Comment controls

Display above the comments

Display below the comments

Display above and below the comments

Do not display

Position of the comment controls box. The comment controls let the user change the default display mode and display order of comments.

Anonymous commenting

Anonymous posters may not enter their contact information

Anonymous posters may leave their contact information

Anonymous posters must leave their contact information

This option is enabled when anonymous users have permission to post comments on the permissions page.

Comment subject field

Can users provide a unique subject for their comments?

Preview comment

Optional

Required

Forces a user to look at their comment by clicking on a 'Preview' button before they can actually add the comment

Location of comment submission form

Display on separate page

Display below post or comments

You are not authorized to post comments.

The comment you are replying to does not exist.

This discussion is closed: you can't post new comments.

Reply

You are not authorized to view comments.

Your comment has been queued for moderation by site administrators and will be published after approval.

Comment: unauthorized comment submitted or comment submitted to a closed node %subject.

parent

reply

Post new comment

The comment no longer exists.

Are you sure you want to delete the comment %title?

Any replies to this comment will be lost. This action cannot be undone.

The comment and all its replies have been deleted.

Publish the selected comments

Delete the selected comments

Unpublish the selected comments

Update options

Update

Subject

Author

Time

Please select one or more comments to perform the update on.

The update has been performed.

No comments available.

There do not appear to be any comments to delete or your selected comment was deleted by another administrator.

Are you sure you want to delete these comments and all their children?

This action cannot be undone.

Delete comments

The comments have been deleted.

You have to specify a valid date.

You have to specify a valid author.

The name you used belongs to a registered user.

You have to leave your name.

The e-mail address you specified is not valid.

You have to leave an e-mail address.

The URL of your homepage is not valid. Remember that it must be fully qualified, i.e. of the form http://example.com/directory.

Administration

Authored by

E-mail

The content of this field is kept private and will not be shown publicly.

Homepage

Authored on

Status

Published

Not published

Your name

Comment

Post comment

(No subject)

!a comments per page

Select your preferred way to display the comments and click "Save settings" to activate your changes.

Comment viewing options

you can't post comments

Login or register to post comments

Login to post comments

Submitted by !username on @datetime.

Flat list - collapsed

Flat list - expanded

Threaded list - collapsed

Threaded list - expanded

Date - newest first

Date - oldest first

After saving a new comment

After saving an updated comment

After deleting a comment

When a comment is being viewed by an authenticated user

Unpublish comment

Unpublish comment containing keyword(s)

Keywords

The comment will be unpublished if it contains any of the character sequences above. Use a comma-separated list of character sequences. Example: funny, bungee jumping, "Company, Inc.". Character sequences are case-sensitive.

Comment: updated %subject.

Comment: added %subject.

Can not delete non-existent comment.

Comment: deleted %subject.

action

Unpublished comment %subject.

1 comment

@count comments

1 new comment

@count new comments

access comments

post comments

administer comments

post comments without approval

Comments

List and edit site comments and the comment moderation queue.

Published comments

Approval queue

Delete comment

Edit comment

Reply to comment

comment

Stores comments and associated data.

Primary Key: Unique comment ID.

The {comment}.cid to which this comment is a reply. If set to 0, this comment is not a reply to an existing comment.

The {node}.nid to which this comment is a reply.

The {user}.uid who authored the comment. If set to 0, this comment was created by an anonymous user.

The comment title.

The comment body.

The author's host name.

The time that the comment was created, or last edited by its author, as a Unix timestamp.

The published status of a comment. (0 = Published, 1 = Not Published)

The {filter_formats}.format of the comment body.

The vancode representation of the comment's place in a thread.

The comment author's name. Uses {user}.name if the user is logged in, otherwise uses the value typed into the comment form.

The comment author's e-mail address from the comment form, if user is anonymous, and the 'Anonymous users may/must leave their contact information' setting is turned on.

The comment author's home page address from the comment form, if user is anonymous, and the 'Anonymous users may/must leave their contact information' setting is turned on.

Maintains statistics of node and comments posts to show "new" and "updated" flags.

The {node}.nid for which the statistics are compiled.

The Unix timestamp of the last comment that was posted within this node, from {comment}.timestamp.

The name of the latest author to post a comment on this node, from {comment}.author.

The user ID of the latest author to post a comment on this node, from {comment}.uid.

The total number of comments on this node.

Allows users to comment on and discuss published content.

Yes

No

Category

Recipients

Selected

Example: 'website feedback' or 'product information'.

Example: 'webmaster@example.com' or 'sales@example.com,support@example.com'. To specify multiple recipients, separate each e-mail address with a comma.

Auto-reply

Optional auto-reply. Leave empty if you do not want to send the user an auto-reply message.

When listing categories, those with lighter (smaller) weights get listed before categories with heavier (larger) weights. Categories with equal weights are sorted alphabetically.

Set this to Yes if you would like this category to be selected by default.

You must enter a category.

You must enter one or more recipients.

%recipient is an invalid e-mail address.

Category %category has been added.

Category %category has been updated.

Are you sure you want to delete %category?

Category %category has been deleted.

Additional information

You can leave a message using the contact form below.

Information to show on the contact page. Can be anything from submission guidelines to your postal address or telephone number.

Hourly threshold

The maximum number of contact form submissions a user can perform per hour.

Enable personal contact form by default

Default status of the personal contact form for new users.

Contact form: category %category added.

Contact form: category %category updated.

Contact form: category %category deleted.

You cannot send more than %number messages per hour. Please try again later.

Your e-mail address

--

Message

Send yourself a copy.

Send e-mail

The contact form has not been configured. Add one or more categories to the form.

You must select a valid category.

You must enter a valid e-mail address.

Your message has been sent.

You need to provide a valid e-mail address to contact other users. Please update your user information and try again.

You cannot contact more than %number users per hour. Please try again later.

From

To

The message has been sent.

%name-from sent an e-mail regarding %category.

%name-from sent %name-to an e-mail.

The contact module enables the use of both personal and site-wide contact forms, thereby facilitating easy communication within the community. While personal contact forms allow users to contact each other by e-mail, site-wide forms allow community members to contact the site administration from a central location. Users can specify a subject and message in the contact form, and also request that a copy of the e-mail be sent to their own address.

Users can activate/deactivate their personal contact forms in their account settings. Upon activation, a contact tab will appear in their user profiles. Privileged users such as site administrators are able to contact users even if they have chosen not to enable this feature.

Note that the contact tab will not appear when a user views his or her own profile; only when viewing another user's profile, if that user's contact form is enabled.

If the menu module is enabled, a menu item linking to the site-wide contact page is added to the navigation block. It is disabled by default, but can be enabled via the menu management page. Links to the contact page may also be added to the primary and secondary links using the same page.

For more information, please read the configuration and customization handbook page for the contact module.

This page lets you setup your site-wide contact form. To do so, add one or more categories. You can associate different recipients with each category to route e-mails to different people. For example, you can route website feedback to the webmaster and direct product information requests to the sales department. On the settings page, you can customize the information shown above the contact form. This can be useful to provide additional contact information such as your postal address and telephone number.

The menu item can be customized and configured only once the menu module has been enabled.

The contact module also adds a menu item (disabled by default) to the navigation block.

Contact settings

Personal contact form

Allow other users to contact you by e-mail via your personal contact form. Note that while your e-mail address is not made public to other members of the community, privileged users such as site administrators are able to contact you even if you choose not to enable this feature.

[!category] !subject

!name sent a message using the contact form at !form.

!name (!name-url) has sent you a message via your contact form (!form-url) at !site.

If you don't want to receive such e-mails, you can change your settings at !url.

Message:

access site-wide contact form

Contact form

Create a system contact form and set up categories for the form to use.

Edit contact category

Delete contact

Contact

contact

Contact form category settings.

Primary Key: Unique category ID.

Category name.

Comma-separated list of recipient e-mail addresses.

Text of the auto-reply message.

The category's weight.

Flag to indicate whether or not category is selected by default. (1 = Yes, 0 = No)

Enables the use of both personal and site-wide contact forms.

Discard log entries above the following row limit

The maximum number of rows to keep in the database log. Older entries will be automatically discarded. Requires crontab.

Type

Date

User

No log messages available.

Count

Location

Referrer

Severity

Hostname

Filter log messages

Filter

Reset

You must select something to filter by.

The dblog module monitors your system, capturing system events in a log to be reviewed by an authorized individual at a later time. This is useful for site administrators who want a quick overview of activities on their site. The logs also record the sequence of events, so it can be useful for debugging site errors.

The dblog log is simply a list of recorded events containing usage data, performance data, errors, warnings and operational information. Administrators should check the dblog report on a regular basis to ensure their site is working properly.

For more information please read the configuration and customization handbook Dblog page.

The dblog module monitors your website, capturing system events in a log to be reviewed by an authorized individual at a later time. The dblog log is simply a list of recorded events containing usage data, performance data, errors, warnings and operational information. It is vital to check the dblog report on a regular basis as it is often the only way to tell what is going on.

Database logging

Settings for logging to the Drupal database logs. This is the most common method for small to medium sites on shared hosting. The logs are viewable from the admin pages.

Recent log entries

View events that have recently been logged.

Top 'page not found' errors

View 'page not found' errors (404s).

Top 'access denied' errors

View 'access denied' errors (403s).

Details

dblog

Table that contains logs of all system events.

Primary Key: Unique watchdog event ID.

The {user}.uid of the user who triggered the event.

Type of log message, for example "user" or "page not found."

Text of log message to be passed into the t() function.

Serialized array of variables that match the message string and that is passed into the t() function.

The severity level of the event; ranges from 0 (Emergency) to 7 (Debug)

Link to view the result of the event.

URL of the origin of the event.

URL of referring page.

Hostname of the user who triggered the event.

Unix timestamp of when event occurred.

Logs and records system events to the database.

All roles may use default format

No roles may use this format

Set default format

Default format updated.

Name

Roles

Add input format

%format input format

All roles for the default format must be enabled and cannot be changed.

Specify a unique name for this filter format.

Choose which roles may use this filter format. Note that roles with the "administer filters" permission can always use all the filter formats.

Filters

Choose the filters that will be used in this filter format.

More information about formatting options

No guidelines available.

These are the guidelines that users will see for posting in this input format. They are automatically generated from the filter settings.

Formatting guidelines

Filter format names need to be unique. A format named %name already exists.

Added input format %format.

The input format settings have been updated.

Are you sure you want to delete the input format %format?

If you have any content left in this input format, it will be switched to the default input format. This action cannot be undone.

The default format cannot be deleted.

Deleted input format %format.

Configure %format

No settings are available.

Rearrange %format

The filter ordering has been saved.

input formats

The filter module allows administrators to configure  text input formats for the site. For example, an administrator may want a filter to strip out malicious HTML from user's comments. Administrators may also want to make URLs linkable even if they are only entered in an unlinked format.

Users can choose between the available input formats when creating or editing content. Administrators can configure which input formats are available to which user roles, as well as choose a default input format. Administrators can also create new input formats. Each input format can be configured to use a selection of filters.

For more information please read the configuration and customization handbook Filter page.


Input formats define a way of processing user-supplied text in Drupal. Every input format has its own settings of which filters to apply. Possible filters include stripping out malicious HTML and making URLs clickable.
Users can choose between the available input formats when submitting content.
Below you can configure which input formats are available to which roles, as well as choose a default input format (used for imported content, for example).
Note that (1) the default format is always available to all roles, and (2) all filter formats can always be used by roles with the "administer filters" permission even if they are not explicitly listed in the Roles column of this table.


Every filter performs one particular change on the user input, for example stripping out malicious HTML or making URLs clickable. Choose which filters you want to apply to text in this input format.
If you notice some filters are causing conflicts in the output, you can rearrange them.

If you cannot find the settings for a certain filter, make sure you have enabled it on the view tab first.


Because of the flexible filtering system, you might encounter a situation where one filter prevents another from doing its job. For example: a word in an URL gets converted into a glossary term, before the URL can be converted in a clickable link. When this happens, you will need to rearrange the order in which filters get executed.
Filters are executed from top-to-bottom. You can use the weight column to rearrange them: heavier filters "sink" to the bottom.

Allowed HTML tags: @tags


This site allows HTML content. While learning all of HTML may feel intimidating, learning how to use a very small number of the most basic HTML "tags" is very easy. This table provides examples for each tag that is enabled on this site.
For more information see W3C's HTML Specifications or use your favorite search engine to find other sites that explain HTML.

Anchors are used to make links to other pages.

By default line break tags are automatically added, so use this tag to add additional ones. Use of this tag is different because it is not used with an open/close pair like all the others. Use the extra " /" inside the tag to maintain XHTML 1.0 compatibility

Text with line break

By default paragraph tags are automatically added, so use this tag to add additional ones.

Paragraph one.

Paragraph two.

Strong

Emphasized

Cited

Coded text used to show programming source code

Coded

Bolded

Underlined

Italicized

Superscripted

Superscripted

Subscripted

Subscripted

Preformatted

Abbreviation

Abbrev.

Acronym

TLA

Block quoted

Quoted inline

Table

Table header

Table cell

Deleted

Inserted

Ordered list - use the <li> to begin each list item

First item

Second item

Unordered list - use the <li> to begin each list item

Definition lists are similar to other HTML lists. <dl> begins the definition list, <dt> begins the definition term and <dd> begins the definition description.

First term

First definition

Second term

Second definition

Header

Subtitle

Subtitle three

Subtitle four

Subtitle five

Subtitle six

Tag Description

You Type

You Get

No help provided for tag %tag.


Most unusual characters can be directly entered without any problems.
If you do encounter problems, try using HTML character entities. A common example looks like & for an ampersand & character. For a full list of entities see HTML's entities page. Some of the available characters include:

Ampersand

Greater than

Less than

Quotation mark

Character Description

No HTML tags allowed

Lines and paragraphs break automatically.

Lines and paragraphs are automatically recognized. The <br /> line break, <p> paragraph and </p> close paragraph tags are inserted automatically. If paragraphs are not recognized simply add a couple blank lines.

Web page addresses and e-mail addresses turn into links automatically.

Input format

HTML filter

Line break converter

URL filter

HTML corrector

Allows you to restrict whether users can post HTML and which tags to filter out. It will also remove harmful content such as JavaScript events, JavaScript URLs and CSS styles from those tags that are not removed.

Converts line breaks into HTML (i.e. <br> and <p> tags).

Turns web and e-mail addresses into clickable links.

Corrects faulty and chopped off HTML in postings.

Filter HTML tags

Strip disallowed tags

Escape all tags

How to deal with HTML tags in user-contributed content. If set to "Strip disallowed tags", dangerous tags are removed (see below). If set to "Escape tags", all HTML is escaped and presented as it was typed.

If "Strip disallowed tags" is selected, optionally specify tags which should not be stripped. JavaScript event attributes are always stripped.

Display HTML help

If enabled, Drupal will display some basic HTML help in the long filter tips.

Spam link deterrent

If enabled, Drupal will add rel="nofollow" to all links, as a measure to reduce the effectiveness of spam links. Note: this will also prevent valid links from being followed by search engines, therefore it is likely most effective when enabled for anonymous users.

Maximum link text length

URLs longer than this number of characters will be truncated to prevent long strings that break formatting. The link itself will be retained; just the text portion of the link will be truncated.

administer filters

Input formats

Configure how content input by users is filtered, including allowed HTML tags. Also allows enabling of module-provided filters.

Delete input format

Compose tips

Edit

Rearrange

filter

Table that maps filters (HTML corrector) to input formats (Filtered HTML).

Primary Key: Auto-incrementing filter ID.

Foreign Key: The {filter_formats}.fid to which this filter is assigned.

The origin module of the filter.

ID to identify which filter within module is being referenced.

Weight of filter within format.

Stores input formats: custom groupings of filters, such as Filtered HTML.

Primary Key: Unique ID for format.

Name of the input format (Filtered HTML).

A comma-separated string of roles; references {role}.rid.

Flag to indicate whether format is cachable. (1 = cachable, 0 = not cachable)

Cache table for the Filter module to store already filtered pieces of text, identified by input format and md5 hash of the text.

Handles the filtering of content in preparation for display.

Forum

Topics

Posts

Last post

@time agoby !author

Go to previous forum topic

Go to next forum topic

Forum name

The forum name is used to identify related discussions.

The forum description can give users more information about the discussion topics it contains.

Parent

When listing forums, those with lighter (smaller) weights get listed before containers with heavier (larger) weights. Forums with equal weights are sorted alphabetically.

forum container

forum

Created new @type %term.

The @type %term has been updated.

Container name

The container name is used to identify related forums.

The container description can give users more information about the forums it contains.

When listing containers, those with with light (small) weights get listed before containers with heavier (larger) weights. Containers with equal weights are sorted alphabetically.

Are you sure you want to delete the forum %name?

Deleting a forum or container will delete all sub-forums and associated posts as well. This action cannot be undone.

The forum %term and all sub-forums and associated posts have been deleted.

Hot topic threshold

The number of posts a topic must have to be considered hot.

Topics per page

The default number of topics displayed per page; links to browse older messages are automatically being displayed.

Posts - most active first

Posts - least active first

Default order

The default display order for topics.

edit container

edit forum

There are no existing containers or forums. You may add some on the add container or add forum pages.

root

Containers are usually placed at the top (root) level of your forum but you can also place a container inside a parent container or forum.

You may place your forum inside a parent container or forum, or at the top (root) level of your forum.

forum: deleted %term and all its sub-forums and associated posts.

The forum module lets you create threaded discussion forums for a particular topic on your site. This is similar to a message board system such as phpBB. Forums are very useful because they allow community members to discuss topics with one another, and they are archived for future reference.

Forums can be organized under what are called containers. Containers hold forums and, in turn, forums hold threaded discussions. Both containers and forums can be placed inside other containers and forums. By planning the structure of your containers and forums well, you make it easier for users to find a topic area of interest to them. Forum topics can be moved by selecting a different forum and can be left in the existing forum by selecting leave a shadow copy. Forum topics can also have their own URL.

Forums module requires Taxonomy and Comments module be enabled.

For more information please read the configuration and customization handbook Forum page.

This is a list of existing containers and forums that you can edit. Containers hold forums and, in turn, forums hold threaded discussions. Both containers and forums can be placed inside other containers and forums. By planning the structure of your containers and forums well, you make it easier for users to find a topic area of interest to them.

Containers help you organize your forums. The job of a container is to hold, or contain, other forums that are related. For example, a container named "Food" might hold two forums named "Fruit" and "Vegetables".

A forum holds discussion topics that are related. For example, a forum named "Fruit" might contain topics titled "Apples" and "Bananas".

These settings provide the ability to fine tune the display of your forum topics. Choose the content types to use in the forums by editing the options for the forum vocabulary.

The item %forum is only a container for forums. Please select one of the forums below it.

Forum topic

Create a new topic for discussion in the forums.

This is the designated forum vocabulary. Some of the normal vocabulary options have been removed.

Active forum topics

New forum topics

Number of topics

Read the latest forum topics.

Leave shadow copy

If you move this topic, you can leave a link in the old forum to the new forum.

Topic

Replies

Created

Last reply

Post new @node_type

You are not allowed to post new content in forum.

Login to post new content in forum.

No forums defined

!count new

This topic has been moved

create forum topics

edit own forum topics

administer forums

Forums

Control forums and their hierarchy and change forum settings.

Add container

Add forum

Edit container

Edit forum

Stores the relationship of nodes to forum terms.

The {node}.nid of the node.

Primary Key: The {node}.vid of the node.

The {term_data}.tid of the forum term assigned to the node.

Enables threaded discussions about general topics.


  Help topics
  Help is available on the following items:
  !help_pages
  Glossary of Drupal terminology
  
   BlockA small box containing information or content placed in a region of a web page (e.g. in a sidebar, below or above the content, or in any other region the current theme allows).
   CommentText attached to a post intended to clarify, explain, criticize, or express an opinion on the original post.
   NodeThe basic unit of content in Drupal, often referred to as a "post". All content that can be created using the "create content" menu is a node. Keep in mind that comments, blocks, and users are not nodes.
   PublishedA post that is viewable by every visitor of the site, regardless of whether he is logged in (see also "Unpublished").
   RoleA classification users are placed into for the purpose of setting users' permissions. A user receives the combined permissions of all roles to which he or she is subscribed.
   TaxonomyA categorization system that allows the building of complex hierarchical or relational structures and tagging of content (see taxonomy help).
   UnpublishedA post that is only viewable by administrators and moderators.
   UserA person who has an account at your Drupal site, and is currently logged in with that account.
   VisitorA person who does not have an account at your Drupal site or a person who has an account at your Drupal site but is not currently logged in with that account. A visitor is also called an "anonymous user".
  

No help is available for module %module.

@module administration pages

This guide explains what the various modules in Drupal do and how to configure them. Additionally, you will find a glossary of basic Drupal terminology to help get you started.
It is not a substitute for the Drupal handbook available online and should be used in conjunction with it. The online reference handbook might be more up-to-date and has helpful user-contributed comments. It is your definitive reference point for all Drupal documentation.


The help module displays context sensitive help information. Users can learn how to use modules and accomplish tasks quicker with less errors by clicking on links in provided by the help module.

Modules can make documentation available to other modules with this module. All user help should be presented using this module. Some examples of help: 

The module's help text, displayed on the help page and through the module's individual help link.
More elaborate help text on sites a module defines.
The help for a distributed authorization module (if applicable).



For more information please read the configuration and customization handbook Help page.

Help

help

Manages the display of online help.

The locale module allows you to present your Drupal site in a language other than the default English. You can use it to set up a multi-lingual website or replace given built-in text with text which has been customized for your site. Whenever the locale module encounters text which needs to be displayed, it tries to translate it into the currently selected language. If a translation is not available, then the string is remembered, so you can look up untranslated strings easily.

The locale module provides two options for providing translations. The first is the integrated web interface, via which you can search for untranslated strings, and specify their translations. An easier and less time-consuming method is to import existing translations for your language. These translations are available as GNU gettext Portable Object files (.po files for short). Translations for many languages are available for download from the translation page.

If an existing translation does not meet your needs, the .po files are easily edited with special editing tools. The locale module's import feature allows you to add strings from such files into your site's database. The export functionality enables you to share your translations with others, generating Portable Object files from your site strings.

For more information please read the configuration and customization handbook Locale page.

Drupal provides support for the translation of its interface text into different languages. This page provides an overview of the installed languages. You can add a language on the add language page, or directly by importing a translation. If multiple languages are enabled, registered users will be able to set their preferred language. The site default will be used for anonymous visitors and for users without their own settings.Drupal interface translations may be added or extended by several courses: by importing an existing translation, by translating everything from scratch, or by a combination of these approaches.

You need to add all languages in which you would like to display the site interface. If you can't find the desired language in the quick-add dropdown, then you will need to provide the proper language code yourself. The language code may be used to negotiate with browsers and to present flags, etc., so it is important to pick a code that is standardised for the desired language. You can also add a language by importing a translation.

The language used to display a web page is determined with a negotiation algorithm. You can choose how this algorithm should work. By default, there is no negotiation and the default language is used. You can use path prefixes (like "de" and "it" for German and Italian content) with different fallback options, so you can have web addresses like /de/contact and /it/contact. Alternatively you can use custom domains like de.example.com and it.example.com. Customize path prefixes and set domain names on the language editing pages.

This page provides an overview of interface translation on the site. Drupal groups all translatable strings in so called 'text groups'. Modules may provide more text groups additionaly to the 'built-in interface' default, to separate strings used for other purposes, allowing you to focus your translation efforts on the groups of text you care most about. For example, a translation team could choose not to fully translate a text group that includes less important data, being still able to ensure that built-in interface is always fully translated.

This page allows you to import a translation provided in the gettext Portable Object (.po) format. The easiest way to get your site translated is to obtain an existing Drupal translation and to import it. You can find existing translations on the Drupal translation page. Note that importing a translation file might take a while.

This page allows you to export Drupal strings. The first option is to export a translation so it can be shared. The second option generates a translation template, which contains all Drupal strings, but without their translations. You can use this template to start a new translation using various software packages designed for this task.

It is often convenient to get the strings from your setup on the export page, and use a desktop Gettext translation editor to edit the translations. On this page you can search in the translated and untranslated strings, and the default English texts provided by Drupal.

This block is only shown if you have at least two languages enabled and you have a language negotiation setting different from 'none', so you have different web addresses for different language versions.

Built-in interface

Language settings

Sets the default site interface and e-mail language for this account.

Path aliases added for languages take precedence over path aliases added for all languages for the same Drupal path.

Multilingual support

Enable multilingual support for this content type. If enabled, a language selection field will be added to the editing form, allowing you to select from one of the enabled languages. If disabled, new posts are saved with the default language. Existing content will not be affected by changing this option.

Language neutral

All

Language switcher

administer languages

translate interface

Configure languages for content and the user interface.

Edit language

Confirm

Translate interface

Translate the built in interface as well as menu items and taxonomies.

Overview

Edit string

Delete string

!long-month-name January

Jan

!long-month-name February

Feb

!long-month-name March

Mar

!long-month-name April

Apr

!long-month-name May

May

!long-month-name June

Jun

!long-month-name July

Jul

!long-month-name August

Aug

!long-month-name September

Sep

!long-month-name October

Oct

!long-month-name November

Nov

!long-month-name December

Dec

Thu

Thursday

Fri

Friday

Sat

Saturday

Sun

Sunday

Mon

Monday

Tue

Tuesday

Wed

Wednesday

am

pm

AM

PM

List of all available languages in the system.

Language code, eg 'de' or 'en-US'.

Language name in English.

Native language name.

Direction of language (Left-to-Right = 0, Right-to-Left = 1).

Enabled flag (1 = Enabled, 0 = Disabled).

Number of plural indexes in this language.

Plural formula in PHP code to evaluate to get plural indexes.

Domain to use for this language.

Path prefix to use for this language.

Weight, used in lists of languages.

Location of JavaScript translation file.

List of English source strings.

Unique identifier of this string.

Drupal path in case of online discovered translations or file path in case of imported strings.

A module defined group of translations, see hook_locale().

The original string in English.

Version of Drupal, where the string was last used (for locales optimization).

Stores translated versions of strings.

Source string ID. References {locales_source}.lid.

Translation string value in this language.

Language code. References {languages}.language.

Parent lid (lid of the previous string in the plural chain) in case of plural strings. References {locales_source}.lid.

Plural index number in case of plural strings.

Locale

Add language handling functionality and enables the translation of the user interface to languages other than English.

Menu item

Expanded

disabled

enable

disable

reset

The menu item has been disabled.

The menu item has been enabled.

Menu settings

Path

The path this menu item links to. This can be an internal Drupal path such as %add-node or an external URL such as %drupal. Enter %front to link to the front page.

Menu link title

The link text corresponding to this item that should appear in the menu.

The description displayed when hovering over a menu item.

If selected and this menu item has children, the menu will always appear expanded.

The maximum depth for an item and all its children is fixed at !maxdepth.  Some menu items may not be available as parents if selecting them would exceed this limit.

Optional. In the menu, the heavier items will sink and the lighter items will be positioned nearer the top.

The path '@link_path' is either invalid or you do not have access to it.

There was an error saving the menu link.

Menu name

The machine-readable name of this menu. This text will be used for constructing the URL of the menu overview page for this menu. This name may consist of only of lowercase letters, numbers, and hyphens, and must be unique.

Are you sure you want to delete the custom menu %title?

The custom menu %title has been deleted.

The menu name may only consist of lowercase letters, numbers, and hyphens.

The menu already exists.

Are you sure you want to delete the custom menu item %item?

The menu item %title has been deleted.

Are you sure you want to reset the item %item to its default values?

Any customizations will be lost. This action cannot be undone.

The menu item was reset to its default settings.

The menu module allows on-the-fly creation of menu links in the content authoring forms. The following option sets the default menu in which a new link will be added.

Default menu for content

Choose the menu to be the default in the menu options in the content authoring form.

Source for the secondary links

Select what should be displayed as the secondary links . If %primary is choosen the children of the active primary menu link (if any) will be shown instead of the links in the %secondary menu.

menu

Deleted custom menu %title and all its menu items.

Deleted menu item %title.

Warning: There is currently 1 menu item in %title. It will be deleted (system-defined items will be reset).

Warning: There are currently @count menu items in %title. They will be deleted (system-defined items will be reset).

The menu name can't be longer than 1 character.

The menu name can't be longer than @count characters.

Menus are a collection of links (menu items) used to navigate a website. The menu module provides an interface to control and customize the powerful menu system that comes with Drupal. Menus are primarily displayed as a hierarchical list of links using Drupal's highly flexible blocks feature. Each menu automatically creates a block of the same name. By default, new menu items are placed inside a built-in menu labelled %navigation, but administrators can also create custom menus.
Drupal themes generally provide out-of-the-box support for two menus commonly labelled %primary-links and %secondary-links. These are sets of links which are usually displayed in the header or footer of each page (depending on the currently active theme).
Menu administration tabs:

  On the administer menu page, administrators can "edit" to change the title, description, parent or weight of a menu item. Under the "operations" column, click on "enable/disable" to toggle a menu item on or off. Only menu items which are enabled are displayed in the corresponding menu block. Note that the default menu items generated by the menu module cannot be deleted, only disabled.
  Use the "add menu" tab to submit a title for a new custom menu. Once submitted, the menu will appear in a list toward the bottom of the administer menu page underneath the main navigation menu. Under the menu name there will be links to edit or delete the menu, and a link to add new items to the menu.
  Use the "add menu item" tab to create new links in either the navigation or a custom menu (such as a primary/secondary links menu). Select the parent item to place the new link within an existing menu structure. For top level menu items, choose the name of the menu in which the link is to be added.


For more information please read the configuration and customization handbook Menu page.

Menus are a collection of links (menu items) used to navigate a website. The list(s) below display the currently available menus along with their menu items. Select an operation from the list to manage each menu or menu item.

Enter the name for your new menu. Remember to enable the newly created block in the blocks administration page.

Enter the title, path, position and the weight for your new menu item.

Delete this menu item.

The link text corresponding to this item that should appear in the menu. Leave blank if you do not wish to add this post to the menu.

administer menu

Menus

Control your site's navigation menu, primary links and secondary links. as well as rename and reorganize menu items.

List menus

Add menu

Customize menu

List items

Add item

Edit menu

Delete menu

Disable menu item

Enable menu item

Edit menu item

Reset menu item

Delete menu item

Holds definitions for top-level custom menus (for example, Primary Links).

Primary Key: Unique key for menu. This is used as a block delta so length is 32.

Menu title; displayed at top of block.

Menu description.

Menu

Allows administrators to customize the site navigation menu.

No content types available.

Body

Identification

The human-readable name of this content type. This text will be displayed as part of the list on the create content page. It is recommended that this name begins with a capital letter and consists only of letters, numbers, and spaces. This name must be unique to this content type.

The machine-readable name of this content type. This text will be used for constructing the URL of the create content page for this content type. This name may consist of only of lowercase letters, numbers, and underscores. Hyphens are not allowed. Underscores will be converted into hyphens when constructing the URL of the create content page. This name must be unique to this content type.

The machine-readable name of this content type. This field cannot be modified for system-defined content types.

A brief description of this content type. This text will be displayed as part of the list on the create content page.

Submission form settings

Title field label

This content type does not have a title field.

Body field label

To omit the body field for this content type, remove any text and leave this field blank.

Minimum number of words

The minimum number of words for the body field to be considered valid for this content type. This can be useful to rule out submissions that do not meet the site's standards, such as short test posts.

Explanation or submission guidelines

This text will be displayed at the top of the submission form for this content type. It is useful for helping or instructing your users.

Workflow settings

Default options

Promoted to front page

Sticky at top of lists

Create new revision

Users with the administer nodes permission will be able to override these options.

Save content type

Delete content type

The machine-readable name %type is already taken.

The machine-readable name can only consist of lowercase letters, underscores, and numbers.

Invalid type. Please enter a type name other than '0' (the character zero).

The human-readable name %name is already taken.

The content type %name has been reset to its default values.

The content type %name has been updated.

The content type %name has been added.

Are you sure you want to delete the content type %type?

The content type %name has been deleted.

node

Added content type %name.

Deleted content type %name.

Changed the content type of 1 post from %old-type to %type.

Changed the content type of @count posts from %old-type to %type.

Warning: there is currently 1 %type post on your site. It may not be able to be displayed or edited correctly, once you have removed this content type.

Warning: there are currently @count %type posts on your site. They may not be able to be displayed or edited correctly, once you have removed this content type.

If the site is experiencing problems with permissions to content, you may have to rebuild the permissions cache. Possible causes for permission problems are disabling modules or configuration changes to permissions. Rebuilding will remove all privileges to posts, and replace them with permissions based on the current modules and settings.

Rebuilding may take some time if there is a lot of content or complex permission settings. After rebuilding has completed posts will automatically use the new permissions.

Node access status

Rebuild permissions

Number of posts on main page

The default maximum number of posts to display per page on overview pages such as the main page.

Length of trimmed posts

Unlimited

200 characters

400 characters

600 characters

800 characters

1000 characters

1200 characters

1400 characters

1600 characters

1800 characters

2000 characters

The maximum number of characters used in the trimmed version of a post. Drupal will use this setting to determine at which offset long posts should be trimmed. The trimmed version of a post is typically used as a teaser when displaying the post on the main page, in XML feeds, etc. To disable teasers, set to 'Unlimited'. Note that this setting will only affect new or updated content and will not affect existing teasers.

Preview post

Must users preview posts before submitting?

Are you sure you want to rebuild node permissions on the site?

This will wipe all current node permissions and rebuild them based on current settings. Rebuilding the permissions may take a while so please be patient. This action cannot be undone.

Publish

Unpublish

Promote to front page

Demote from front page

Make sticky

Remove stickiness

status

published

not published

promoted

not promoted

sticky

not sticky

up to date translation

outdated translation

type

category

language

Show only items where

and where %a is %b

%a is %b

Refine

Undo

and

where

is

No items selected.

No posts available.

Are you sure you want to delete these items?

Delete all

The items have been deleted.

Edit %title

Create @name

Revision information

Log message

An explanation of the additions or updates being made to help other authors understand your motivations.

Authoring information

Leave blank for %anonymous.

Format: %time. Leave blank to use the time of form submission.

Publishing options

Show summary in full view

Create content

Submit @name

The trimmed version of your post shows what your post looks like when promoted to the main page or when exported for syndication. You can insert the delimiter "<!--break-->" (without the quotes) to fine-tune where your post gets split.

Preview trimmed version

Preview full version

Your %post has been created.

The %post has been updated.

The node could not be saved.

Are you sure you want to delete %title?

Revision of %title from %date

Revisions for %title

Revision

!date by !username

current revision

revert

Copy of the revision from %date.

%title has been reverted back to the revision from %revision-date

You tried to revert to an invalid revision.

Deleted %title revision %revision.

Deletion failed. You tried to delete the current revision.

@type: added %title.

@type: updated %title.

@type: reverted %title revision %revision.

@type: deleted %title revision %revision.

The content access permissions need to be rebuilt.

The content access permissions need to be rebuilt. Please visit this page.

All content in a website is stored and treated as nodes. Therefore nodes are any postings such as blogs, stories, polls and forums. The node module manages these content types and is one of the strengths of Drupal over other content management systems.

Treating all content as nodes allows the flexibility of creating new types of content. It also allows you to painlessly apply new features or changes to all content. Comments are not stored as nodes but are always associated with a node.

Node module features

The list tab provides an interface to search and sort all content on your site.
The configure settings tab has basic settings for content on your site.
The configure content types tab lists all content types for your site and lets you configure their default workflow.
The search tab lets you search all content on your site



For more information please read the configuration and customization handbook Node page.

Enter a simple pattern to search for a post. Words are matched exactly. Phrases can be surrounded by quotes to do an exact search.

Below is a list of all the content types on your site. All posts that exist on your site are instances of one of these content types.

To create a new content type, enter the human-readable name, the machine-readable name, and all other relevant fields that are on this page. Once created, users of your site will be able to create posts that are instances of this content type.

The revisions let you track differences between multiple versions of a post.

The body of your @type is too short. You need at least %words words.

This content has been modified by another user, changes cannot be saved.

The username %name does not exist.

%title has been deleted.

Log

Content

Content ranking

The following numbers control which properties the content search should favor when ordering the results. Higher numbers mean more influence, zero means the property is ignored. Changing these numbers does not require the search index to be rebuilt. Changes take effect immediately.

Keyword relevance

Recently posted

Number of comments

Number of views

Factor

Read more

Read the rest of !title.

Syndicate

RSS

Welcome to your new Drupal website!Please follow these steps to set up and start using your website:

Configure your website Once logged in, visit the administration section, where you can customize and configure all aspects of your website.

Enable additional functionality Next, visit the module list and enable features which suit your specific needs. You can find additional modules in the Drupal modules download section.

Customize your website design To change the "look and feel" of your website, visit the themes section. You may choose from one of the included themes or download additional themes from the Drupal themes download section.

Start posting content Finally, you can create content for your website. This message will disappear once you have promoted a post to the front page.

For more information, please refer to the help section, or the online Drupal handbooks. You may also post at the Drupal forum, or view the wide range of other support options available.

Advanced search

Containing any of the words

Containing the phrase

Containing none of the words

Only in the category(s)

Only of the type(s)

Rebuilding content access permissions

The node access table has been rebuilt.

The content access permissions have been rebuilt.

The content access permissions have not been properly rebuilt.

Submitted by !username on @datetime

When either saving a new post or updating an existing post

After saving a new post

After saving an updated post

After deleting a post

When content is viewed by an authenticated user

Publish post

Unpublish post

Make post sticky

Make post unsticky

Promote post to front page

Remove post from front page

Change the author of a post

Save post

Unpublish post containing keyword(s)

The username of the user to which you would like to assign ownership.

Please enter a valid username.

The node will be unpublished if it contains any of the character sequences above. Use a comma-separated list of character sequences. Example: funny, bungee jumping, "Company, Inc.". Character sequences are case-sensitive.

The update has encountered an error.

Processing %title

An error occurred and processing did not complete.

@type: deleted %title.

Set @type %title to published.

Set @type %title to unpublished.

Set @type %title to sticky.

Set @type %title to unsticky.

Promoted @type %title to front page.

Removed @type %title from front page.

Saved @type %title

Changed owner of @type %title to uid %name.

1 item successfully processed:

@count items successfully processed:

administer content types

administer nodes

access content

view revisions

revert revisions

View, edit, and delete your site's content.

Search content

Search content by keyword.

Post settings

Control posting behavior, such as teaser length, requiring previews before posting, and the number of posts on the front page.

Content types

Manage posts by content type, including default status, front page promotion, etc.

Add content type

Revisions

The base table for nodes.

The primary identifier for a node.

The current {node_revisions}.vid version identifier.

The {node_type} of this node.

The {languages}.language of this node.

The title of this node, always treated a non-markup plain text.

The {users}.uid that owns this node; initially, this is the user that created it.

Boolean indicating whether the node is published (visible to non-administrators).

The Unix timestamp when the node was created.

The Unix timestamp when the node was most recently saved.

Whether comments are allowed on this node: 0 = no, 1 = read only, 2 = read/write.

Boolean indicating whether the node should displayed on the front page.

Previously, a boolean indicating whether the node was "in moderation"; mostly no longer used.

Boolean indicating whether the node should be displayed at the top of lists in which it appears.

The translation set id for this node, which equals the node id of the source post in each set.

A boolean indicating whether this translation page needs to be updated.

Identifies which realm/grant pairs a user must possess in order to view, update, or delete specific nodes.

The {node}.nid this record affects.

The grant ID a user must possess in the specified realm to gain this row's privileges on the node.

The realm in which the user must possess the grant ID. Each node access node can define one or more realms.

Boolean indicating whether a user with the realm/grant pair can view this node.

Boolean indicating whether a user with the realm/grant pair can edit this node.

Boolean indicating whether a user with the realm/grant pair can delete this node.

Access statistics for {node}s.

The {node}.nid for these statistics.

The total number of times the {node} has been viewed.

The total number of times the {node} has been viewed today.

The most recent time the {node} has been viewed.

Stores information about each saved version of a {node}.

The {node} this version belongs to.

The primary identifier for this version.

The {users}.uid that created this version.

The title of this version.

The body of this version.

The teaser of this version.

The log entry explaining the changes in this version.

A Unix timestamp indicating when this version was created.

The input format used by this version's body.

Stores information about all defined {node} types.

The machine-readable name of this type.

The human-readable name of this type.

The module that implements this type.

A brief description of this type.

Help information shown to the user when creating a {node} of this type.

Boolean indicating whether this type uses the {node}.title field.

The label displayed for the title field on the edit form.

Boolean indicating whether this type uses the {node}.body field.

The label displayed for the body field on the edit form.

The minimum number of words the body must contain.

A boolean indicating whether this type is defined by a module (FALSE) or by a user via a module like the Content Construction Kit (TRUE).

A boolean indicating whether this type has been modified by an administrator; currently not used in any way.

A boolean indicating whether the administrator can change the machine name of this type.

The original machine-readable name of this node type. This may be different from the current type name if the locked field is 0.

Node

Allows content to be submitted to the site and displayed on pages.

OpenID redirect

Send

OpenID login failed.

OpenID login cancelled.

Successfully added %identity

OpenID

Add an OpenID

That OpenID is already in use on this site.

OpenID deleted.

This site supports OpenID, a secure way to log into many websites using a single username and password. OpenID can reduce the necessity of managing many usernames and passwords for many websites.

To use OpenID you must first establish an identity on a public or private OpenID server. If you do not have an OpenID and would like one, look into one of the free public providers. You can find out more about OpenID at this website.

If you already have an OpenID, enter the URL to your OpenID server below (e.g. myusername.openidprovider.com). Next time you login, you will be able to use this URL instead of a regular username and password. You can have multiple OpenID servers if you like; just keep adding them here.

OpenID is a secure method for logging into many websites with a single username and password. It does not require special software, and it does not share passwords with any site to which it is associated; including your site.

Users can create accounts using their OpenID, assign one or more OpenIDs to an existing account, and log in using an OpenID. This lowers the barrier to registration, which is good for the site, and offers convenience and security to the users. OpenID is not a trust system, so email verification is still necessary. The benefit stems from the fact that users can have a single password that they can use on many websites. This means they can easily update their single password from a centralized location, rather than having to change dozens of passwords individually.

The basic concept is as follows: A user has an account on an OpenID server. This account provides them with a unique URL (such as myusername.openidprovider.com). When the user comes to your site, they are presented with the option of entering this URL. Your site then communicates with the OpenID server, asking it to verify the identity of the user.  If the user is logged into their OpenID server, the server communicates back to your site, verifying the user. If they are not logged in, the OpenID server will ask the user for their password. At no point does your site record, or need to record the user's password.

More information on OpenID is available at OpenID.net.

Once you have verified your email address, you may log in via OpenID.

Log in using OpenID

Cancel OpenID login

What is OpenID?

Sorry, that is not a valid OpenID. Please ensure you have spelled your ID correctly.

You must validate your email address for this account before logging in via OpenID

OpenID registration failed for the reasons listed. You may register now, or if you already have an account you can log in now and add your OpenID under "My Account"

Only site administrators can create new user accounts.

OpenID Login

OpenID identities

Delete OpenID

openid

Stores temporary shared key association information for OpenID authentication.

URI of the OpenID Provider endpoint.

Primary Key: Used to refer to this association in subsequent messages.

The signature algorithm used: one of HMAC-SHA1 or HMAC-SHA256.

Valid association session types: "no-encryption", "DH-SHA1", and "DH-SHA256".

The MAC key (shared secret) for this association.

UNIX timestamp for when the association was created.

The lifetime, in seconds, of this association.

Allows users to log into your site using OpenID.

Alias

System

No URL aliases found.

No URL aliases available.

Existing system path

Specify the existing path you wish to alias. For example: node/28, forum/1, taxonomy/term/1+2.

Path alias

Specify an alternative path by which this data can be accessed. For example, type "about" when writing an about page. Use a relative path and don't add a trailing slash or the URL alias won't work.

Update alias

Create new alias

The alias %alias is already in use in this language.

The alias has been saved.

Are you sure you want to delete path alias %title?

Filter aliases

The path module allows you to specify aliases for Drupal URLs. Such aliases improve readability of URLs for your users and may help internet search engines to index your content more effectively. More than one alias may be created for a given page.

Some examples of URL aliases are:

user/login => login
image/tid/16 => store
taxonomy/term/7+19+20+21 => store/products/whirlygigs
node/3 => contact



The path module enables an extra field for aliases in all node input and editing forms (when users have the appropriate permissions). It also provides an interface to view and edit all URL aliases. The two permissions related to URL aliasing are "administer url aliases" and "create url aliases". 

This module also comes with user-defined mass URL aliasing capabilities, which is useful if you wish to uniformly use URLs different from the default. For example, you may want to have your URLs presented in a different language. Access to the Drupal source code on the web server is required to set up these kinds of aliases. 

For more information please read the configuration and customization handbook Path page.

Drupal provides users complete control over URLs through aliasing. This feature is typically used to make URLs human-readable or easy to remember. For example, one could map the relative URL 'node/1' onto 'about'. Each system path can have multiple aliases.

Enter the path you wish to create the alias for, followed by the name of the new alias.

The alias has been deleted.

The path is already in use.

URL path settings

Optionally specify an alternative URL by which this node can be accessed. For example, type "about" when writing an about page. Use a relative path and don't add a trailing slash or the URL alias won't work.

create url aliases

administer url aliases

URL aliases

Change your site's URL paths by aliasing them.

Edit alias

Delete alias

Add alias

path

Allows users to rename URLs.

Adds a filter option to include PHP in content.

You may post PHP code. You should include <?php ?> tags.


Using custom PHP code
If you know how to script in PHP, Drupal gives you the power to embed any script you like. It will be executed when the page is viewed and dynamically embedded into the page. This gives you amazing flexibility and power, but of course with that comes danger and insecurity if you don't write good code. If you are not familiar with PHP, SQL or with the site engine, avoid experimenting with PHP because you can corrupt your database or render your site insecure or even unusable! If you don't plan to do fancy stuff with your content then you're probably better off with straight HTML.
Remember that the code within each PHP item must be valid PHP code - including things like correctly terminating statements with a semicolon. It is highly recommended that you develop your code separately using a simple test script on top of a test database before migrating to your production environment.
Notes:You can use global variables, such as configuration parameters, within the scope of your PHP code but remember that global variables which have been given values in your code will retain these values in the engine afterwards.register_globals is now set to off by default. If you need form information you need to get it from the "superglobals" $_POST, $_GET, etc.You can either use the print or return statement to output the actual content for your item.
A basic example:
You want to have a box with the title "Welcome" that you use to greet your visitors. The content for this box could be created by going:

print t("Welcome visitor, ... welcome message goes here ...");

If we are however dealing with a registered user, we can customize the message by using:

global $user;
if ($user->uid) {
  print t("Welcome $user->name, ... welcome message goes here ...");
}
else {
  print t("Welcome visitor, ... welcome message goes here ...");
}

For more in-depth examples, we recommend that you check the existing Drupal code and use it as a starting point, especially for sidebar boxes.

PHP evaluator

Executes a piece of PHP code. The usage of this filter should be restricted to administrators only!

A !php-code input format has been created.

The PHP module has been disabled. Please note that any existing content that was using the PHP filter will now be visible in plain text. This might pose a security risk by exposing sensitive information, if any, used in the PHP code.

PHP filter

Allows embedded PHP code/snippets to be evaluated.

The ping module is useful for notifying interested sites that your site has changed. It automatically sends notifications (called "pings") to the pingomatic service to tell it that your site has changed. In turn pingomatic will ping other services such as weblogs.com, Technorati, blo.gs, BlogRolling, Feedster.com, Moreover, etc.

The ping module requires cron or a similar periodic job scheduler to be enabled.

For more information please read the configuration and customization handbook Ping page.

directory ping

Failed to notify pingomatic.com (site).

ping

Ping

Alerts other sites when your site has been updated.

1 vote

@count votes

Total votes: @votes

open

closed

This table lists all the recorded votes for this poll.  If anonymous users are allowed to vote, they will be identified by the IP address of the computer they used when they voted.

Visitor

Vote

The poll module can be used to create simple polls for site users. A poll is a simple multiple choice questionnaire which displays the cumulative results of the answers to the poll. Having polls on the site is a good way to get instant feedback from community members.

Users can create a poll. The title of the poll should be the question, then enter the answers and the "base" vote counts. You can also choose the time period over which the vote will run.The poll item in the navigation menu will take you to a page where you can see all the current polls, vote on them (if you haven't already) and view the results.

For more information please read the configuration and customization handbook Poll page.

Most recent poll

Poll

A poll is a multiple-choice question which visitors can vote on.

Question

More choices

If the amount of boxes above isn't enough, click here to add more choices.

Add another choice

Closed

Active

Poll settings

Poll status

When a poll is closed, visitors can no longer vote for it.

Poll duration

After this period, the poll will be closed automatically.

Choice @n

Votes for choice @n

Negative values are not allowed.

You must fill in at least two choices.

Older polls

View the list of polls on this site.

Results

View the current poll results.

Your vote was recorded.

Choice

Vote count

Cancel your vote

create polls

vote on polls

cancel own vote

inspect all votes

Polls

Votes

Javascript Choice Form

poll

Stores poll-specific information for poll nodes.

The poll's {node}.nid.

The number of seconds past {node}.created during which the poll is open.

Boolean indicating whether or not the poll is open.

Stores information about all choices for all {poll}s.

Unique identifer for a poll choice.

The {node}.nid this choice belongs to.

The text for this choice.

The total number of votes this choice has received by all users.

The sort order of this choice among all choices for the same node.

Stores per-{users} votes for each {poll}.

The {poll} node this vote is for.

The {users}.uid this vote is from unless the voter was anonymous.

The {users}'s vote for this poll.

The IP address this vote is from unless the voter was logged in.

Allows your site to capture votes on different topics in the form of multiple choice questions.

The profile module allows you to define custom fields (such as country, real name, age, ...) in the user profile. This permits users of a site to share more information about themselves, and can help community-based sites to organize users around profile fields.

The following types of fields can be added to the user profile:

single-line textfield
multi-line textfield
checkbox
list selection
freeform list
URL
date



For more information please read the configuration and customization handbook Profile page.

Here you can define custom fields that users can fill in as part of their user profile (such as country, real name, age, ...).

Author information

Link to full user profile

Profile fields to display

Select which profile fields you wish to display in the block. Only fields designated as public in the profile field configuration are available.

View full user profile

About %name

edit %title

add new %type

Field settings

The category the new field should be part of. Categories are used to group fields logically. An example category is "Personal information".

The title of the new field. The title will be shown to the user. An example title is "Favorite color".

Form name

The name of the field. The form name is not shown to the user but used internally in the HTML code and URLs.
Unless you know what you are doing, it is highly recommended that you prefix the form name with profile_ to avoid name clashes with other fields. Spaces or any other special characters except dash (-) and underscore (_) are not allowed. An example name is "profile_favorite_color" or perhaps just "profile_color".

Explanation

An optional explanation to go with the new field. The explanation will be shown to the user.

Selection options

A list of all options. Put each option on a separate line. Example options are "red", "blue", "green", etc.

The weights define the order in which the form fields are shown. Lighter fields "float up" towards the top of the category.

Visibility

Hidden profile field, only accessible by administrators, modules and themes.

Private field, content only available to privileged users.

Public field, content shown on profile page but not used on member list pages.

Public field, content shown on profile page and on member list pages.

Page title

To enable browsing this field by value, enter a title for the resulting page. The word %value will be substituted with the corresponding value. An example page title is "People whose favorite color is %value". This is only applicable for a public field.

To enable browsing this field by value, enter a title for the resulting page. An example page title is "People who are employed". This is only applicable for a public field.

Form will auto-complete while user is typing.

The user must enter a value.

Visible in user registration form.

Save field

The specified form name contains one or more illegal characters. Spaces or any other special characters except dash (-) and underscore (_) are not allowed.

The specified form name is reserved for use by Drupal.

The specified category name is reserved for use by Drupal.

The specified title is already in use.

The specified name is already in use.

A hidden field cannot be required.

A hidden field cannot be set to visible on the user registration form.

The field has been created.

The field has been updated.

Are you sure you want to delete the field %field?

This action cannot be undone. If users have entered values into this field in their profile, these entries will also be deleted. If you want to keep the user-entered data, instead of deleting the field you may wish to edit this field and change it to a hidden profile field so that it may only be accessed by administrators.

The field %field has been deleted.

No fields defined.

Add new field

User list

Put each item on a separate line or separate them by commas. No HTML allowed.

The value provided for %field is not a valid URL.

The field %field is required.

single-line textfield

multi-line textfield

checkbox

list selection

freeform list

date

profile

Profile field %field added under category %category.

Profile field %field deleted.

Profiles

Create customizable fields for your users.

Add field

Profile category autocomplete

Edit field

Delete field

Profile autocomplete

Stores profile field information.

Primary Key: Unique profile field ID.

Title of the field shown to the end user.

Internal name of the field used in the form HTML and URLs.

Explanation of the field to end users.

Profile category that the field will be grouped under.

Title of page used for browsing by the field's value

Type of form field.

Weight of field in relation to other profile fields.

Whether the user is required to enter a value. (0 = no, 1 = yes)

Whether the field is visible in the user registration form. (1 = yes, 0 = no)

The level of visibility for the field. (0 = hidden, 1 = private, 2 = public on profile but not member list pages, 3 = public on profile and list pages)

Whether form auto-completion is enabled. (0 = disabled, 1 = enabled)

List of options to be used in a list selection field.

Stores values for profile fields.

The {profile_fields}.fid of the field.

The {users}.uid of the profile user.

The value for the field.

Profile

Supports configurable user profiles.

Are you sure you want to re-index the site?

 The search index is not cleared but systematically updated to reflect the new settings. Searching will continue to work but new content won't be indexed until all existing content has been re-indexed. This action cannot be undone.

Re-index site

The index will be rebuilt.

%percentage of the site has been indexed.