diff options
| -rw-r--r-- | INSTALL | 3 | ||||
| -rw-r--r-- | includes/story.inc | 2 | ||||
| -rw-r--r-- | modules/affiliate-site.module | 2 | ||||
| -rw-r--r-- | modules/ban.module | 10 | ||||
| -rw-r--r-- | modules/block.module | 8 | ||||
| -rw-r--r-- | modules/block/block.module | 8 | ||||
| -rw-r--r-- | modules/box.module | 18 | ||||
| -rw-r--r-- | modules/cron.module | 6 | ||||
| -rw-r--r-- | modules/documentation.module | 41 | ||||
| -rw-r--r-- | modules/headline.module | 6 | ||||
| -rw-r--r-- | modules/story.module | 8 | ||||
| -rw-r--r-- | modules/story/story.module | 8 |
12 files changed, 69 insertions, 51 deletions
@@ -3,6 +3,7 @@ - online installation guidelines * http://drop.org/module.php?mod=drupal - - drupal project page + - drupal project page if you would like to get involved in the + ongoing development diff --git a/includes/story.inc b/includes/story.inc index a1ba62796..04e93661a 100644 --- a/includes/story.inc +++ b/includes/story.inc @@ -13,7 +13,7 @@ class Story { function story_visible($story) { global $user; - return ($story->status == 1 && $user->id) || ($story->status == 2) || user_permission(); + return ($story->status == 2) || ($story->status == 1 && $user->id) || user_permission($user); } ?>
\ No newline at end of file diff --git a/modules/affiliate-site.module b/modules/affiliate-site.module index d8e1e1079..fda10b46e 100644 --- a/modules/affiliate-site.module +++ b/modules/affiliate-site.module @@ -6,7 +6,7 @@ $module = array("help" => "affiliate_help", function affiliate_help() { ?> - <P>This is a small module to manage related and/or affiliate sites. The module exports 2 different blocks with links to the affiliate sites.</P> + <P>This is a small module to manage related and/or affiliate sites. The module exports two different blocks with links to the affiliate sites.</P> <? } diff --git a/modules/ban.module b/modules/ban.module index 862077a47..b370e2da7 100644 --- a/modules/ban.module +++ b/modules/ban.module @@ -10,19 +10,19 @@ function ban_help() { ?> <P>The ban module keeps a list of bans in four categories:</P> <UL> - <LI>E-mail bans: this type of ban specifies which email-addresses will be rejected when registering new users. Can be used to prevent users from using a free-mail account (e.g. hotmail.com).</LI> + <LI>Email bans: this type of ban specifies which email addresses will be rejected when registering new users. Can be used to prevent users from using a free email account (e.g. userid@hotmail.com).</LI> <LI>Profanity bans: <I>under construction</I></LI> - <LI>Hostname bans: this type of ban allows you to block certain hostnames to access to your site or to register as a new user.</LI> + <LI>Hostname bans: this type of ban allows you to block certain hostnames from access to your site or from registering as a new user.</LI> <LI>Username bans: this ban will block certain usernames from registration. Typical examples include <I>admin</I>, <I>anonymous</I>, <I>root</I>, <I>webmaster</I>, etc.</LI> </UL> - <P>The ban system allows you to use a flexible wild-card ban system. This means you can block all email addresses from a certain domain name, block every username starting with "guest", etc. To do this, you can use the following wild-card characters:</P> + <P>The ban module allows you to use a flexible wild-card ban system. This means you can block all email addresses from a certain domain name, block every username starting with "guest", etc. To do this, use the following wild-card characters:</P> <UL> <LI> % : matches any number of characters, including zero characters.</LI> <LI> _ : matches exactly one character.</LI> </UL> - <P><U>Examples</U>:</P> + <P><U>Examples:</U></P> <UL> - <LI>E-mail address bans <CODE>%@hotmail.com</CODE>, <CODE>%@altavista.%</CODE>, <CODE>%@usa.net</CODE>, etc. Used to prevent users from using free-email accounts, which might be used to cause trouble.</LI> + <LI>Email address bans <CODE>%@hotmail.com</CODE>, <CODE>%@altavista.%</CODE>, <CODE>%@usa.net</CODE>, etc. Used to prevent users from using free email accounts, which might be used to cause trouble.</LI> <LI>Username bans <CODE>root</CODE>, <CODE>webmaster</CODE>, <CODE>admin%</CODE>, etc. Used to prevent administrator impersonators.</LI> </UL> <? diff --git a/modules/block.module b/modules/block.module index bfa38bae9..2d112c0be 100644 --- a/modules/block.module +++ b/modules/block.module @@ -6,10 +6,10 @@ $module = array("page" => "block_page", function block_help() { ?> - <P>Blocks are the boxes visible in the side bars on the left and the right-hand side of the website. They are either exported by the engine or by any of the available modules. To really get your teeth in a drupal website, you are going to have to deal with blocks and administrating blocks in a fairly sophisticated fashion. This means you are going to have to be sensitive to the way the block placement strategy works.</P> - <P>The placement of blocks is delegated to the administrator but for most blocks, i.e. those called "custom blocks", the sole force behind enabling and disabling them is the user itself.</P> - <P>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 heavy blocks will sink down whereas the light blocks will be positioned at the top.</P> - <P>As mentioned above, blocks can be arranged to fit in two regions: left and right. For theme builders, each region is identified by a corresponding constant: "left" and "right".</P> + <P>Blocks are the boxes visible in the side bars on the left- and right-hand side of the website. They are either exported by the engine or by any of the active modules. To really get your teeth into a drupal website, you are going to have to deal with blocks and administering blocks in a fairly sophisticated fashion. This means you will need to understand how the block placement strategy works.</P> + <P>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.</P> + <P>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.</P> + <P>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".</P> <? } diff --git a/modules/block/block.module b/modules/block/block.module index bfa38bae9..2d112c0be 100644 --- a/modules/block/block.module +++ b/modules/block/block.module @@ -6,10 +6,10 @@ $module = array("page" => "block_page", function block_help() { ?> - <P>Blocks are the boxes visible in the side bars on the left and the right-hand side of the website. They are either exported by the engine or by any of the available modules. To really get your teeth in a drupal website, you are going to have to deal with blocks and administrating blocks in a fairly sophisticated fashion. This means you are going to have to be sensitive to the way the block placement strategy works.</P> - <P>The placement of blocks is delegated to the administrator but for most blocks, i.e. those called "custom blocks", the sole force behind enabling and disabling them is the user itself.</P> - <P>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 heavy blocks will sink down whereas the light blocks will be positioned at the top.</P> - <P>As mentioned above, blocks can be arranged to fit in two regions: left and right. For theme builders, each region is identified by a corresponding constant: "left" and "right".</P> + <P>Blocks are the boxes visible in the side bars on the left- and right-hand side of the website. They are either exported by the engine or by any of the active modules. To really get your teeth into a drupal website, you are going to have to deal with blocks and administering blocks in a fairly sophisticated fashion. This means you will need to understand how the block placement strategy works.</P> + <P>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.</P> + <P>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.</P> + <P>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".</P> <? } diff --git a/modules/box.module b/modules/box.module index 9a2cd51a9..d516b6863 100644 --- a/modules/box.module +++ b/modules/box.module @@ -7,21 +7,21 @@ $module = array("help" => "box_help", function box_help() { ?> - <P>The content of the site can be almost entirely altered through boxes. Simply put, <I>boxes</I> are small bits of text, HTML or PHP code which will get plugged into the site just like any other block. Boxes are typically used to add custom blocks to the site.</P> - <P>Each box consists of a subject and an associated block of text, HTML or PHP code which can be as long as you want it to be and that will 'render' the content of the box.</P> + <P>The content of the site can be almost entirely altered through <I>boxes</I>. Simply put, boxes are small bits of text, HTML or PHP code which will get plugged into the site just like any other block. Boxes are typically used to add custom blocks to the site.</P> + <P>Each box consists of a subject and an associated block of text, HTML or PHP code that can be as long as you wish and that will 'render' the content of the box.</P> <H3>PHP boxes</H3> - <P>If you know how to script in PHP, PHP boxes are pretty easy to create. Don't worry if you're no PHP-wizard: simply use ASCII or HTML boxes instead.</P> + <P>If you know how to script in PHP, PHP boxes are easy to create. Don't worry if you're no PHP-wizard: simply use ASCII or HTML boxes instead.</P> <P>You can use any piece of PHP code to make up the content of a PHP box: this implies that you can declare and use functions, consult the SQL database, access configuration settings and much more. A PHP box's code is stored in the database and the engine will dynamically embed the PHP code just-in-time for execution.</P> - <P>There are however some factors to keep in mind when using and creating PHP boxes: PHP boxes can be extremely useful and flexible, yet they can be dangerous and insecure if not properly used. If you are not familiar with PHP, SQL or even with the site engine for that matter, avoid experimenting with PHP boxes because you can - and you probably will - corrupt your database or even render your site unusable! If you don't plan to do fancy stuff with boxes then you're probably better off with ASCII or HTML boxes.</P> - <P>Remember that the code within each PHP box must be valid PHP code, including things like terminating statements with a semicolon so the parser won't die. Therefore, it is highly recommended to test your boxes separately using a simple test script on top of a test database before migrating to your production environment running your real database.</P> - <P>Note that you can use global variables such as configuration parameters within the scope of a PHP box. Also keep in mind that variables that have been given values in a PHP box will retain these values in the engine or module afterwards.</P> + <P>There are however some factors to keep in mind when using and creating PHP boxes: PHP boxes can be extremely useful and flexible, yet they can be dangerous and insecure if not properly used. If you are not familiar with PHP, SQL or with the site engine, avoid experimenting with PHP boxes because you can - and probably will - corrupt your database or render your site unusable! If you don't plan to do fancy stuff with boxes then you're probably better off with ASCII or HTML boxes.</P> + <P>Remember that the code within each PHP box must be valid PHP code -- including things like correctly terminating statements with a semicolon so that the parser won't die. It is highly recommended that you develop your boxes separately using a simple test script on top of a test database before migrating to your production environment.</P> + <P>Note that you can use global variables such as configuration parameters within the scope of a PHP box. Also keep in mind that variables which have been given values in a PHP box will retain these values in the engine or module afterwards.</P> <P>You can use the <CODE>return</CODE> statement to return the actual content for your block as well.</P> <P><U>A basic example:</U></P> - <P>Given the box with subject "Welcome", used to create a "<I>Welcome</I>"-box. The content for this box could be created by using:</P> + <P>Given the box with subject "Welcome", used to create a "<I>Welcome</I>" box. The content for this box could be created by using:</P> <PRE> return "Welcome visitor, ... welcome message goes here ..."; </PRE> - <P>If we are however dealing with a registered user, we can customize the message by using: + <P>If we are however dealing with a registered user, we can customize the message by using:</P> <PRE> if ($user->userid) { return "Welcome $user->userid, ... welcome message goes here ..."; @@ -30,7 +30,7 @@ function box_help() { return "Welcome visitor, ... welcome message goes here ..."; } </PRE> - <P>For a more in-depth example, we recommend you to check the existing boxes and to use them as a start.</P> + <P>For more in-depth examples, we recommend that you check the existing boxes and use them as a starting point.</P> <? } diff --git a/modules/cron.module b/modules/cron.module index cb3bbb1fa..05dbdb0eb 100644 --- a/modules/cron.module +++ b/modules/cron.module @@ -5,9 +5,9 @@ $module = array("help" => "cron_help", function cron_help() { ?> - <P>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.</P> - <P>Note that cron does not guarantee that the commands will be executed at the specified interval. However, the engine will make sure that the commands are run at the specified intervals as closely as possible.</P> - <P>Check the documentation page for more information about cron and how to setup it correctly.</P> + <P>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 <i>n</i> 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.</P> + <P>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.</P> + <P>Check the documentation page for more information about cron and how to setup it correctly.</P> <? } diff --git a/modules/documentation.module b/modules/documentation.module index 9150be178..5a9aec24e 100644 --- a/modules/documentation.module +++ b/modules/documentation.module @@ -16,7 +16,8 @@ function documentation() { <H1>Chapter 1: introduction</H1> <P>Drupal is the English pronunciation for the Dutch word 'druppel' which means 'drop'. Drupal is a fully-featured content management/discussion engine suitable to setup a news-driven community or portal site. Drupal aims to provide easy installation, excessive configuration and fine-grained maintenance capabilities. Due to its modular design, drupal is flexible and easy to adapt or extend.</P> - <P>Drupal is primarily written by Dries Buytaert (dries_at_drop.org) and built after Slash (<A HREF="http://slashcode.com/">http://slashcode.com/</A>) and Scoop (<A HREF="http://scoop.kuro5hin.org/">http://scoop.kuro5hin.org/</A>).</P> + <P>Drupal is primarily written by Dries Buytaert (dries_at_drop.org) and built after Slash (<A HREF="http://slashcode.com/">http://slashcode.com/</A>) and Scoop (<A HREF="http://scoop.kuro5hin.org/">http://scoop.kuro5hin.org/</A>). Drupal is released under the GNU General Public License (GPL) so if you are interested in helping out the drupal project in any way, drop me an e-mail.</P> + <P>Everybody can download, use and modify drupal to suit his or her needs. Everybody can freely distribute modified or unmodified versions of it, provided that they too are licensed under the GNU GPL. Drupal is maintained by volunteer effort at a best effort basis but you can always contact me or other drupal developers for consulting services related to drupal.</P> <H1>Chapter 2: installation</H1> @@ -40,22 +41,36 @@ function documentation() { <BLOCKQUOTE>$ mysql -h <I><hostname></I> -u <I><username></I> -p<I><password> <database></I> < database/database.mysql</BLOCKQUOTE> <P>5. Rename the configuration file <CODE>includes/hostname.conf</CODE> to match your server's hostname:</P> <BLOCKQUOTE>$ cp includes/hostname.conf includes/www.yourdomain.com.conf</BLOCKQUOTE> + <P><CODE>/</CODE>'s and <CODE>:</CODE>'s are translated to <CODE>.</CODE>'s. So if the URI of your drupal site would be <CODE>http://www.yourdomain.com:80/foo/</CODE> your configuration file should be named <CODE>www.yourdomain.com.80.foo.conf</CODE>.</P> <P>6. Edit your configuration file to set the required settings such as the database options and to customize your site to your likings.</P> <P>7. Launch your browser and point it to http://yourdomain.com/, create an account, log in and head on to http://yourdomain.com/admin.php. The first user will automatically have administrator permissions. Play with it for a bit and spend some time getting used to the administration interfaces.</P> <P>8. Optionally (yet recommended for smooth operation) edit the <CODE>.htaccess</CODE> file and set the values of the PHP variables to your likings: <CODE>session.name</CODE>, <CODE>session.cookie_lifetime</CODE>, <CODE>session.gc_maxlifetime</CODE>, <CODE>session.cache_expire</CODE> and <CODE>session.save_path</CODE>. Check your PHP reference manual for the exact purpose of each variable mentioned.</P> <P>9. Optionally (yet recommended for smooth operation) setup a crontab to periodically visit http://yourdomain.com/cron.php.</P> <P>Use a browser like lynx or wget but make sure the process terminates: either use /usr/bin/lynx -source http://yourdomain.com/cron.php or /usr/bin/wget -O /dev/null http://yourdomain.com/cron.php. Take a look at the example scripts in the <CODE>scripts</CODE>-directory and make sure to adjust them to your needs.</P> <P>A good crontab-line to run the cron-script once every hour would be:</P> - <PRE> - 00 * * * * /home/www/drupal/scripts/cron-lynx - </PRE> + <PRE> 00 * * * * /home/www/drupal/scripts/cron-lynx</PRE> <P>10. Optionally create your site's theme or at least customize the existing themes. To get started, head on to the <CODE>themes</CODE>-directory and make a custom logo for each theme. <P>11. Optionally add and remove modules to customize the functionality of your site. Adding and removing modules is plain easy. You can add a module by copying the files into the <CODE>modules</CODE>-directory and you can remove a module by removing a module's file from the <CODE>modules</CODE>-directory. The drupal engine will then automatically include or exclude this module. If for some reason, this seems to fail, "manually" rehash the modules list from http://yourdomain.com/admin.php?mod=module.</P> <P>12. If you get it to run, let us know at <A HREF="mailto:info@drop.org">info@drop.org</A> so we can add your site to our list of drupal sites. If you can't get it to run, you can find support at the drupal site or you can contact us by e-mail at <A HREF="mailto:info@drop.org">info@drop.org</A>.</P> - <H2>More than one (sub)domain on one machine</H2> + <H2>More then one drupal site on one machine</H2> + + <H3>Multiple directories</H3> + + <P>Drupal allows you to setup multiple drupal sites using different directories on top of one physical source tree. This might be useful if you want to setup multiple sites about different topics (e.g. <CODE>http://yourdomain.com/travel/</CODE> and <CODE>http://yourdomain.com/sport/</CODE>) or if you want to provide users on your system with a personal drupal site (e.g. <CODE>http://yourdomain.com/~joe/</CODE> and <CODE>http://yourdomain.com/~john/</CODE>). When using Unix/Linux as your host operating system, this can be best accomplished by using symbolic links:</P> + <PRE> + $ ls -l includes/*.conf + -rw-rw-r-- 1 drupal drupal includes/yourdomain.com.~joe.conf + </PRE> + <P>Once you created the configuration file, create a fake directory using symbolic links that matches the URI. For a drupal site with URI <CODE>http://yourdomain.com/~joe/</CODE> use:</P> + <BLOCKQUOTE>$ ln -s . ~joe</BLOCKQUOTE> + <P>If you want Joe to be able to configure his own drupal site, create another symbolic link to make the configuration file <CODE>includes/yourdomain.com.~joe.conf</CODE> available to Joe in his home directory:</P> + <BLOCKQUOTE>$ ln -s /path-to-drupal/includes/yourdomain.com.joe.conf /home/joe/</BLOCKQUOTE> + + <H3>More than one domain or vhost one machine</H3> + + <H4>Multiple domains using the same database</H4> - <H3>Multiple (sub)domains using the same database</H3> <P>If you want to host multiple domains (or subdomains) on top of the same database (e.g. http://yourdomain.com/ and http://www.yourdomain.com/), simply use symbolic links to setup the required configuration files:</P> <BLOCKQUOTE>$ ln -s includes/yourdomain.com.conf includes/www.yourdomain.com.conf</BLOCKQUOTE> <PRE> @@ -64,7 +79,8 @@ function documentation() { lrwxrwxrrx 1 drupal drupal includes/www.yourdomain.com.conf -> includes/yourdomain.com.conf </PRE> - <H3>Multiple (sub)domains using different databases</H3> + <H4>Multiple domains or vhosts using different databases</H4> + <P>Apache supports both IP- and name-based virtual hosts (vhosts). While running more than one engine (by using vhosts) can be very useful for development and testing purpose, it might even be more interesting for hosting companies. Therefor, we tried to support vhosts in the best possible way in order to make the life of any administrator easier. We do so by making it possible to run an unlimited amount of vhosts on the same physical source tree, though by using different configuration files. Moreover, you can setup multiple configuration files in your <CODE>includes</CODE>-directory.</P> <PRE> $ ls -l includes/*.conf @@ -88,7 +104,7 @@ function documentation() { <H1>Chapter 3: drupal engine</H1> - <P>While we in no way consider the design and implementation of the drupal engine to be finished, we feel that our own accompanying intensive experience has given us a fairly stable and well-proven design. The following provides a brief over-view of the different aspects of drupal's core engine and features.</P> + <P>While we in no way consider the design and implementation of the drupal engine to be finished, we feel that our own accompanying intensive experience has given us a fairly stable and well-proven design. The following provides a brief over-view of the different aspects of drupal's core engine and features.</P> <H2>Cron</H2> @@ -185,8 +201,8 @@ function documentation() { $theme->header(); // displays the header of a page for each $article to be displayed { - $theme->article($article); - // displays a themed article or story + $theme->article($article); + // displays a themed article or story } $theme->footer(); // displays the footer of a page @@ -227,7 +243,7 @@ function documentation() { <H3>Linux</H3> <P>To gain access via (anonymous) CVS use the following steps. In this example it is assumed that you want a copy of the drupal source code.</P> - <P>1. Install a recent copy of CVS. All you really need is a copy of the CVS client binary. Alternatively you can download the latest CVS source code from <A HREF="http://www.cyclic.com">Cyclic Software</A>. Don't worry: CVS is free software under the GNU GPL.</P> + <P>1. Install a recent copy of CVS. All you really need is a copy of the CVS client binary. Alternatively you can download the latest CVS source code from <A HREF="http://www.cyclic.com">Cyclic Software</A>. Don't worry: CVS is free .</P> <P>2. Set CVSROOT in your environment:</P> <BLOCKQUOTE>$ export CVSROOT=":pserver:anonymous@drop.org:/home/dries/cvs"</BLOCKQUOTE> <P>3. Login by running the command:</P> @@ -251,6 +267,7 @@ function documentation() { <P>If you can want to interface the CVS repository just like Linux users do (raw and uncut), then check <A HREF="http://oodt.jpl.nasa.gov/doc/developers-resources/developing/windows/index.html">this site</A>.</P> <H3>Additional references</H3> + <UL> <LI><A HREF="http://cvsbook.red-bean.com/">CVS book</A></LI> <LI><A HREF="http://www.loria.fr/~molli/cvs/doc/cvs_toc.html">CVS docs</A></LI> @@ -281,4 +298,4 @@ function documentation() { <P>5. <B>Mail or submit the patch:</B><BR>Remember: no MIME, no HTML mail, no links, no compression, no attachments. Just plain text.</P> <? } -?> +?>
\ No newline at end of file diff --git a/modules/headline.module b/modules/headline.module index 306944cea..6d5f19a5b 100644 --- a/modules/headline.module +++ b/modules/headline.module @@ -70,9 +70,9 @@ function headline_cron() { function headline_help() { ?> <P>Drupal's headline module both imports and exports RDF/RSS headlines.</P> - <P>A lot of news-oriented websites are now publishing news (headlines) and make their content available through XML, RSS and RDF backend files. They syndicate content for free and allow retrieval and further transmission, aggregation, or online publication. At the current state, drupal's headline module supports RDF and RSS backends.</P> - <P>RSS was originally developed by Netscape to be able to add news channels to "My Netscape" sites, but has since become adopted as the defacto standard for distributing headlines and brief descriptions of things that change around the net.</P> - <P>The headline module goes out to a list of configured news sites once an hour or so (driven from 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 at http://yourdomain.com/export/headlines.rdf.</P> + <P>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.</P> + <P>RSS was originally developed by Netscape to allow adding news channels to "My Netscape" sites, but it has since become adopted as the <I>de facto</I> net standard for distributing headlines and brief dynamic texts.</P> + <P>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 <CODE>http://yourdomain.com/export/headlines.rdf</CODE>.</P> <? } diff --git a/modules/story.module b/modules/story.module index 69b97dfd3..130ae42e3 100644 --- a/modules/story.module +++ b/modules/story.module @@ -16,10 +16,10 @@ function story_cron() { function story_help() { ?> - <P><B>Scheduled stories</B>: stories that are scheduled to be automatically published at a given date and time. Useful when you have to leave the site alone for a while or when you want to regulate the flow of new content.</P> - <P><B>Queued stories</B>: user-contributed stories are automatically whisked away to a submission queue for moderators to frown at it. Moderators vote whether or not a story should be carried to the front page for discussion.</P> - <P><B>Posted stories</B>: published stories accessible to all visitors.</P> - <P><B>Dumped stories</B>: rejected stories that are no longer available to visitors.</P> + <P>Scheduled stories: stories that are scheduled to be automatically published at a given date and time. Useful when you have to leave the site alone for a while or when you want to regulate the flow of new content.</P> + <P>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.</P> + <P>Posted stories: published stories accessible to all visitors.</P> + <P>Dumped stories: rejected stories that are no longer available to visitors.</P> <? } diff --git a/modules/story/story.module b/modules/story/story.module index 69b97dfd3..130ae42e3 100644 --- a/modules/story/story.module +++ b/modules/story/story.module @@ -16,10 +16,10 @@ function story_cron() { function story_help() { ?> - <P><B>Scheduled stories</B>: stories that are scheduled to be automatically published at a given date and time. Useful when you have to leave the site alone for a while or when you want to regulate the flow of new content.</P> - <P><B>Queued stories</B>: user-contributed stories are automatically whisked away to a submission queue for moderators to frown at it. Moderators vote whether or not a story should be carried to the front page for discussion.</P> - <P><B>Posted stories</B>: published stories accessible to all visitors.</P> - <P><B>Dumped stories</B>: rejected stories that are no longer available to visitors.</P> + <P>Scheduled stories: stories that are scheduled to be automatically published at a given date and time. Useful when you have to leave the site alone for a while or when you want to regulate the flow of new content.</P> + <P>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.</P> + <P>Posted stories: published stories accessible to all visitors.</P> + <P>Dumped stories: rejected stories that are no longer available to visitors.</P> <? } |