From accd5f0c31a68450bb091b18338933e212553b4d Mon Sep 17 00:00:00 2001 From: Dries Buytaert Date: Sat, 10 Mar 2001 11:07:52 +0000 Subject: - applied David Norman's patch to turn all - project architect Jeroen Bensch - - themes and images + - themes and documentation Steven Wittens - themes and images @@ -13,4 +13,7 @@ Kjartan Mannes - hosting, hardware, bandwidth Michael O'Henly - - documentation revisions + - documentation improvements + +David Norman + - code improvements diff --git a/account.php b/account.php index dd9e5f1a0..a2668074b 100644 --- a/account.php +++ b/account.php @@ -1,4 +1,4 @@ - - <? echo $site_name; ?> administration + <?php echo $site_name; ?> administration

Administration

- -
home
- home
+ - 0x01, "profanity" => 0x02, diff --git a/includes/comment.inc b/includes/comment.inc index 744ab0f9b..c4587b124 100644 --- a/includes/comment.inc +++ b/includes/comment.inc @@ -1,4 +1,4 @@ -na"; diff --git a/includes/hostname.conf b/includes/hostname.conf index 19cd94b0f..57d5f574c 100644 --- a/includes/hostname.conf +++ b/includes/hostname.conf @@ -1,4 +1,4 @@ - array("0", $submission_rate["comment"]), "diary" => array("1", $submission_rate["diary"]), diff --git a/index.php b/index.php index b6e8efc43..bd1d6e22c 100644 --- a/index.php +++ b/index.php @@ -1,4 +1,4 @@ - "account_help", "find" => "account_find", @@ -9,7 +9,7 @@ function account_help() {

The account-module is responsible for maintaining the user database. It automatically handles tasks like registration, authentication, access rights, password retrieval, user settings and much more.

The required administration can be accomplished through the "account" interface of the administration section. From here administrators can get a quick overview of all registered users and view/edit specific accounts using the links provided. Some useful operations include blocking specific accounts (e.g. a troublesome user) and giving/taking administration permissions. Note that you should only give these permissions to people you trust!

Check the documentation page for detailed information about user management.

- "affiliate_help", "block" => "affiliate_block", @@ -7,7 +7,7 @@ $module = array("help" => "affiliate_help", function affiliate_help() { ?>

This is a small module to manage related and/or affiliate sites. The module exports two different blocks with links to the affiliate sites.

- id'"); // Strip all 'junk': - $data = ereg_replace("", "", $data); + $data = ereg_replace("", "", $data); $data = ereg_replace(" "ban_help", "admin" => "ban_admin"); @@ -25,7 +25,7 @@ function ban_help() {
  • Email address bans %@hotmail.com, %@altavista.%, %@usa.net, etc. Used to prevent users from using free email accounts, which might be used to cause trouble.
  • Username bans root, webmaster, admin%, etc. Used to prevent administrator impersonators.
    • - "block_page", "help" => "block_help", @@ -10,7 +10,7 @@ function block_help() {

    The placement of blocks is delegated to the administrator. In most cases (i.e., the "custom" blocks), the user has complete control -- using preferences -- over whether or not they are enabled.

    An administrator can lay out and arrange the available blocks to fit in two regions: "left" and "right". Regions simply contain blocks. In addition, an administrator can assign each block (within a region) a weight to sort them vertically. The heavier blocks will sink and the lighter blocks will be positioned nearer the top.

    As mentioned, blocks may be arranged to fit in two regions: left and right. For theme builders, each region is identified by a corresponding constant: "left" and "right".

    - "block_page", "help" => "block_help", @@ -10,7 +10,7 @@ function block_help() {

    The placement of blocks is delegated to the administrator. In most cases (i.e., the "custom" blocks), the user has complete control -- using preferences -- over whether or not they are enabled.

    An administrator can lay out and arrange the available blocks to fit in two regions: "left" and "right". Regions simply contain blocks. In addition, an administrator can assign each block (within a region) a weight to sort them vertically. The heavier blocks will sink and the lighter blocks will be positioned nearer the top.

    As mentioned, blocks may be arranged to fit in two regions: left and right. For theme builders, each region is identified by a corresponding constant: "left" and "right".

    - "box_help", "block" => "box_block", @@ -31,7 +31,7 @@ function box_help() { }

    For more in-depth examples, we recommend that you check the existing boxes and use them as a starting point.

    - "calendar_block"); diff --git a/modules/comment.module b/modules/comment.module index 83a62df9e..cb86997b4 100644 --- a/modules/comment.module +++ b/modules/comment.module @@ -1,4 +1,4 @@ - "comment_find", "admin" => "comment_admin"); diff --git a/modules/comment/comment.module b/modules/comment/comment.module index 83a62df9e..cb86997b4 100644 --- a/modules/comment/comment.module +++ b/modules/comment/comment.module @@ -1,4 +1,4 @@ - "comment_find", "admin" => "comment_admin"); diff --git a/modules/cron.module b/modules/cron.module index 05dbdb0eb..d316b0b39 100644 --- a/modules/cron.module +++ b/modules/cron.module @@ -1,4 +1,4 @@ - "cron_help", "admin" => "cron_admin"); @@ -8,7 +8,7 @@ function cron_help() {

    Cron (which stands for chronograph) is a periodic command scheduler: it executes commands at intervals specified in seconds. It can be used to control the execution of daily, weekly and monthly jobs (or anything with a period of n seconds). Automating tasks is one of the best ways to keep a system running smoothly, and if most of your administration does not require your direct involvement, cron is an ideal solution.

    Note that cron does not guarantee the commands will be executed at the specified interval. However, the engine will make sure that the commands are run as close to the specified intervals as possible.

    Check the documentation page for more information about cron and how to setup it correctly.

    - "diary_find", "help" => "diary_help", @@ -217,7 +217,7 @@ function diary_page() { function diary_help() { ?>

    Drupal's diary module allows registered users to maintain an online diary. It provides easy-to-write and easy-to-read online diaries or journals that can be filled with daily thoughts, poetry, boneless blabber, spiritual theories, intimate details, valuable experiences, cynical rants, semi-coherent comments, writing experiments, artistic babblings, critics on current facts, fresh insights, diverse dreams, chronicles and mumbling madness available for public consumption.

    - "documentation", "admin" => "documentation"); @@ -269,7 +269,7 @@ function documentation() {

    Chapter 4: modules

    - @@ -342,6 +342,6 @@ function documentation() {

    3. Describe your changes:
    Describe the technical detail of the change(s) your patch includes and try to be as specific as possible. Note that we prefer technical reasoning above marketing: give us clear reasons why "this way" is good. Justify your changes and try to carry enough weight. It is important to note the version to which this patch applies.

    4. Separate your changes:
    Separate each logical change into its own patch. For example, if your changes include both bug fixes and performance enhancements, separate those changes into two or more patches. If your changes include an API update, and a new module which uses that new API, separate those into two patches.

    5. Mail or submit the patch:
    Remember: no MIME, no HTML mail, no links, no compression, no attachments. Just plain text.

    - diff --git a/modules/drupal-site.module b/modules/drupal-site.module index ba751935c..d4742b681 100644 --- a/modules/drupal-site.module +++ b/modules/drupal-site.module @@ -1,4 +1,4 @@ - "drupal_block", "admin" => "drupal_admin"); diff --git a/modules/drupal.module b/modules/drupal.module index dce787314..35d785247 100644 --- a/modules/drupal.module +++ b/modules/drupal.module @@ -1,4 +1,4 @@ - "drupal_page"); diff --git a/modules/drupal/drupal.module b/modules/drupal/drupal.module index dce787314..35d785247 100644 --- a/modules/drupal/drupal.module +++ b/modules/drupal/drupal.module @@ -1,4 +1,4 @@ - "drupal_page"); diff --git a/modules/faq.module b/modules/faq.module index 283b8e563..88e59ed6e 100644 --- a/modules/faq.module +++ b/modules/faq.module @@ -1,4 +1,4 @@ - "faq_page", "admin" => "faq_admin"); diff --git a/modules/headline.module b/modules/headline.module index da9f71e45..f6b09fcae 100644 --- a/modules/headline.module +++ b/modules/headline.module @@ -1,4 +1,4 @@ - "headline_page", "cron" => "headline_cron", @@ -73,7 +73,7 @@ function headline_help() {

    A lot of news-oriented websites are now publishing news (headlines) and making their content available through XML, RSS and RDF backend files. They syndicate free content and allow retrieval and further transmission, aggregation, and online publication. In its current state, drupal's headline module supports RDF and RSS backends.

    RSS was originally developed by Netscape to allow adding news channels to "My Netscape" sites, but it has since become adopted as the de facto net standard for distributing headlines and brief dynamic texts.

    The headline module goes out to a list of configured news sites once an hour or so (driven by cron), downloads new RSS/RDF data and makes it available to your visitors. In addition, your headlines are exported as well and can be retrieved by other sites from http://yourdomain.com/export/headlines.rdf.

    - \n"; + print "\n"; print "\n"; diff --git a/modules/locale.module b/modules/locale.module index c96d9a0dc..da09f8fd6 100644 --- a/modules/locale.module +++ b/modules/locale.module @@ -1,4 +1,4 @@ - "locale_help", "admin" => "locale_admin", @@ -25,7 +25,7 @@ function locale_help() { mysql> ALTER TABLE locales ADD nl TEXT DEFAULT '' NOT NULL; mysql> ALTER TABLE locales ADD fr TEXT DEFAULT '' NOT NULL; - "locale_help", "admin" => "locale_admin", @@ -25,7 +25,7 @@ function locale_help() { mysql> ALTER TABLE locales ADD nl TEXT DEFAULT '' NOT NULL; mysql> ALTER TABLE locales ADD fr TEXT DEFAULT '' NOT NULL; - "module_help", "admin" => "module_admin"); @@ -6,7 +6,7 @@ $module = array("help" => "module_help", function module_help() { ?> The module administration page provide you a list of all available modules. Moreover, it allows you to "rehash" modules. Whenever you install a new module or when an existing module has been changed or updated, it requires "rehasing": when you rehash a module, the module is registered to the engine and properly initialized. - "rating_cron", "help" => "rating_help", @@ -46,7 +46,7 @@ function rating_help() {

    The idea of (1) is that it favors comments that more people voted on, and thus whose rating is more likely to be accurate or justified.

    The latter (2) makes the user rating that comes out of the calulations temporary, based on users' most recent activity and responsive to their current state. This is accomplished by taking each user's last 30 comments, or however many he or she posted in the last 60 days - whatever comes first.

    Additionally, users that posted one or more succesful stories in the last 60 days gain extra bonus points which will boost up their overall rating.

    - "section_help", "block" => "section_block", @@ -14,7 +14,7 @@ function section_help() { ?>

    When submitting new stories, every story is assigned a section or category. Sections can be maintained from the administration pages.

    For moderation purpose, you can specify a post, dump and expiration thresholds for each available section according to type and urgency level of a section. This is useful considering the fact that some sections do not really "expire" and stay interesting and active as time passes by, whereas news-related stories are only considered "hot" over a short period of time.

    - "story_cron", "help" => "story_help", @@ -37,7 +37,7 @@ function story_help() {

    Queued stories: user-contributed stories are automatically whisked away to a submission queue for moderators (i.e. registered user) to frown at. Moderators vote whether or not a story should be posted to the front page for discussion.

    Posted stories: published stories accessible to all visitors.

    Dumped stories: rejected stories that are no longer available to visitors.

    - "story_cron", "help" => "story_help", @@ -37,7 +37,7 @@ function story_help() {

    Queued stories: user-contributed stories are automatically whisked away to a submission queue for moderators (i.e. registered user) to frown at. Moderators vote whether or not a story should be posted to the front page for discussion.

    Posted stories: published stories accessible to all visitors.

    Dumped stories: rejected stories that are no longer available to visitors.

    - "submission_menu", "page" => "submission_page"); diff --git a/modules/watchdog.module b/modules/watchdog.module index 13908e39d..0252d5105 100644 --- a/modules/watchdog.module +++ b/modules/watchdog.module @@ -1,4 +1,4 @@ - "watchdog_help", "cron" => "watchdog_cron", @@ -8,7 +8,7 @@ function watchdog_help() { ?>

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

    To ease administration, the watchdog will automatically remove old logs.

    - "watchdog_help", "cron" => "watchdog_cron", @@ -8,7 +8,7 @@ function watchdog_help() { ?>

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

    To ease administration, the watchdog will automatically remove old logs.

    - "wishlist_page", "help" => "wishlist_help"); @@ -60,7 +60,7 @@ function wishlist_page() {
  • create a theme with black background - darker theme
  • try to get existing themes HTML validated
    • - - <? print $site_name; ?> + <?php print $site_name; ?>