Skip to content
Browse files

Doc updates for upcoming slash-1.0.6

  • Loading branch information...
1 parent ffb8dae commit 23f6ce8ab58b7079a3d0a8497f466f1295722355 @pudge pudge committed Jul 10, 2000
Showing with 138 additions and 189 deletions.
  1. +69 −51 CHANGES
  2. +12 −25 INSTALL
  3. +5 −5 README
  4. +1 −1 Slash.pm
  5. +12 −25 docs/INSTALL
  6. +14 −44 docs/INSTALL.html
  7. +12 −25 docs/INSTALL.pod
  8. +5 −5 docs/README
  9. +4 −4 docs/README.html
  10. +4 −4 docs/README.pod
View
120 CHANGES
@@ -1,6 +1,11 @@
-slash-1.0.6, 2000.06.xx
+slash-1.0.6, 2000.07.10
-----------------------
+* Don't let BLOCKQUOTEs nest more than 4 in comments.pl (same
+ as UL and OL)
+
+* Added Bundle::CPAN to Bundle::Slash (see INSTALL)
+
* Don't let users edit authors without seclev >= 500 (ttyp0)
* Fix for all TEXTAREA sections, converting all < and > and &
@@ -37,8 +42,9 @@ slash-1.0.6, 2000.06.xx
* Submission titles are now shown on the browser's titlebar
-* Section articles appearing on the main index now also have a link
- to the section's home page by the "Read More" link (Russ Nelson)
+* Section articles appearing on the main index now also have a
+ link to the section's home page by the "Read More" link
+ (Russ Nelson)
* Fixed bug where authors could moderate if they were logged in as
authors, but not logged in as a registered user
@@ -49,81 +55,93 @@ slash-1.0.6, 2000.06.xx
fact that there are some situations where we may want to make
certain moderations that don't get applied still applicable to
M2 review. comments.pl and article.pl have been made aware of
- this new field
+ this new field/
* Metamoderation results are now counted. The number of times a
user's moderation is voted fair or unfair is now counted in
users_info (columns m2fair and m2unfair)
-* Fixed small bug in admin.pl which would result in bugs while saving
- and editing topics if $I{basedir} was not derived from $I{datadir}
- (ie, if the 2 directories were on different partitions)
+* Fixed small bug in admin.pl which would result in bugs while
+ saving and editing topics if $I{basedir} was not derived from
+ $I{datadir} (i.e., if the 2 directories were on different
+ partitions)
-* If there were no images in the topic images directory, the topic
+* If there were no images in the topic images directory, the topic
editor would display a select list with no items. Now, a warning
is displayed and the user is given an input box filled with the
current filename
-* Hit counting has been disabled (again) in search.pl due to problems
- with httpd stability. Aparently precounting results, even
- on fast servers will cause a huge load on MySQL which then
+* Hit counting has been disabled (again) in search.pl due to
+ problems with httpd stability. Aparently precounting results,
+ even on fast servers will cause a huge load on MySQL which then
flakes out the httpds. Will be analysing this to see if a
- solution can be found. Until then, we will only count the number
- of matches we've encountered and the bottom link will say
- "More matches..." as opposed to "x more matches"
+ solution can be found. Until then, we will only count the
+ number of matches we've encountered and the bottom link will
+ say "More matches..." as opposed to "x more matches"
-* More counts added for M2, now in addition to counting the number of
- times a user is voted fair or unfair, we also count the times a user VOTES
- fair or unfair. The last pair of numbers can be used to determine if
- your Slash metamoderation system is being abused. (This adds 2 new columns
- to users_info: m2fairvotes and m2unfairvotes)
+* More counts added for M2, now in addition to counting the
+ number of times a user is voted fair or unfair, we also count
+ the times a user VOTES fair or unfair. The last pair of numbers
+ can be used to determine if your Slash metamoderation system is
+ being abused. (This adds 2 new columns to users_info:
+ m2fairvotes and m2unfairvotes)
* Changes to the moderation system, these can be summed up by
describing the following new variables added to slashdotrc.pl:
- m2_maxunfair: Float from 0 to 1. This number determines the percentage
- of unfair votes that indicates abuse. The user performing
- M2 will quietly be assessed a karma penalty and their
- votes will be ignored if their percentage of unfair
- votes equals or exceeds this value.
-
- m2_toomanyunfair: Float from 0 to 1. This number determines the
- percentage of unfair votes that indicates POSSIBLE
- abuse of the system. If the percentage of unfair
- votes exceeds this value then these votes are
- ignored. No penalty is assessed.
+ m2_maxunfair: Float from 0 to 1. This number determines
+ the percentage of unfair votes that indicates
+ abuse. The user performing M2 will quietly be
+ assessed a karma penalty and their votes will
+ be ignored if their percentage of unfair votes
+ equals or exceeds this value.
- m2_mincheck: Integer. Number of comments which have to be voted on
- before the above checks are performed.
+ m2_toomanyunfair: Float from 0 to 1. This number
+ determines the percentage of unfair votes that
+ indicates POSSIBLE abuse of the system. If the
+ percentage of unfair votes exceeds this value
+ then these votes are ignored. No penalty is
+ assessed.
- m2_comments: Number of comment moderations to be displayed in a single
- M2 session.
+ m2_mincheck: Integer. Number of comments which have to
+ be voted on before the above checks are
+ performed.
- m2_bonus: Amount of karma to be awarded upon completion of M2.
+ m2_comments: Number of comment moderations to be
+ displayed in a single M2 session.
- m2_penalty: Amount of karma to be subtracted if M2 is abused.
+ m2_bonus: Amount of karma to be awarded upon completion
+ of M2.
- m2_maxbonus: Karma maximum from M2. If a user's karma exceeds this
- value, then said user receives no further bonus
- for his participation.
+ m2_penalty: Amount of karma to be subtracted if M2 is
+ abused.
-* Added the 'flag' column in metamodlog. This indicates how an M2 session
- was treated and is a good way to check for possible M2 problems. Currently
- flag can be the following values:
- 0 - No detected problems with M2.
- 1 - Questionable M2. Votes ignored.
- 2 - Abuse of M2. Votes ignored and UID penalized.
+ m2_maxbonus: Karma maximum from M2. If a user's karma
+ exceeds this value, then said user receives no
+ further bonus or his participation.
+
+* Added the 'flag' column in metamodlog; this indicates how an M2
+ session was treated and is a good way to check for possible M2
+ problems. Currently flag can be the following values:
+ 0 - No detected problems with M2
+ 1 - Questionable M2. Votes ignored
+ 2 - Abuse of M2. Votes ignored and UID penalized
* Renamed slashdotrc.pl variables:
- 'goodkarma_limit' is now 'goodkarma'
- 'badkarma_limit' is now 'badkarma'
+ 'goodkarma_limit' is now 'goodkarma'
+ 'badkarma_limit' is now 'badkarma'
+
+* User's ID (UID) added to comment headers
-* User's ID (UID) added to comment headers.
+* Names of the comment poster have been removed during
+ metamoderation
-* Names of the comment poster have been removed during metamoderation.
+* Fixed a minor bug in metamod.pl that inadvertantly stopped the
+ injection of new eligible users into the metamoderation pool
-* Fixed a minor bug in metamod.pl that inadvertantly stopped the injection
- of new eligible users into the metamoderation pool.
+* Added "<rss> ... </rss>" to .rdf file, and added encoding
+ of "ISO-8859-1" (will later be configurable) in slashd
+ (Roger Carneiro Soares)
slash-1.0.5, 2000.06.13
View
37 INSTALL
@@ -47,7 +47,7 @@ SOFTWARE REQUIREMENTS
Perl modules
- DBI-1.13
+ DBI-1.14
http://search.cpan.org/search?dist=DBI
Data-ShowTable-3.3
@@ -595,31 +595,18 @@ INSTALLATION AND SETUP
blocks data changed. Examine the script and CHANGES and determine if you
want to run the script, or whatever.
- Upgrade 0.9.5 -> 1.0.0
-Just run the script update_db-1.0.0.sql in the sql/updates/1.0.0/ directory, and
-make sure you have the latest code.
+ Other Upgrades
- Upgrade 1.0.0 -> 1.0.0.1
-Just run the script update_db-1.0.0.1.sql in the sql/updates/1.0.0.1/
-directory, and make sure you have the latest code.
-
- Upgrade 1.0.0.1 -> 1.0.2
-Just run the script update_db-1.0.2.sql in the sql/updates/1.0.2/
-directory, and make sure you have the latest code.
-
- Upgrade 1.0.2 -> 1.0.3
-Just run the script formkeys.sql in the sql/updates/1.0.3/
-directory, and make sure you have the latest code. Note that the
-commentkey table is no longer used; feel free to delete if you want to.
-
- Upgrade 1.0.3 -> 1.0.4
-Just run the script formkeys.sql in the sql/updates/1.0.4/
-directory, and make sure you have the latest code.
-
- Upgrade 1.0.4 -> 1.0.5
-Just run the udpate script in the sql/updates/1.0.5/
-directory, and make sure you have the latest code.
+ From To Run Scipts in Dir
+ ------- ------- --------------------
+ 0.9.5 -> 1.0.0 sql/updates/1.0.0/
+ 1.0.0 -> 1.0.0.1 sql/updates/1.0.0.1/
+ 1.0.0.1 -> 1.0.2 sql/updates/1.0.2/
+ 1.0.2 -> 1.0.3 sql/updates/1.0.3/
+ 1.0.3 -> 1.0.4 sql/updates/1.0.4/
+ 1.0.4 -> 1.0.5 sql/updates/1.0.5/
+ 1.0.5 -> 1.0.6 sql/updates/1.0.6/
AUTHOR
- Patrick Galbraith and Chris Nandor. Last Modified June 13, 2000.
+ Patrick Galbraith and Chris Nandor. Last Modified July 10, 2000.
View
10 README
@@ -2,7 +2,7 @@ NAME
README - Slashdot Readme
DESCRIPTION
- This is the README file for Slash, release 1.0.5. Please read all
+ This is the README file for Slash, release 1.0.6. Please read all
documentation carefully. The various documents explain the database
schema, the various fields in the database, and some of the reasoning
behind the design of the schema, installation and setup.
@@ -30,9 +30,9 @@ DESCRIPTION
See the Slash web site, with support, docs, latest downloads, FAQs, and
more, at &lt;URL:http://slashcode.com/&gt;.
- This release is tagged in CVS as v1_0_5_0. See the SourceForge site at
- http://sourceforge.net/project/?group_id=4421 for CVS, bug reporting,
- patch submissions, and downloads.
+ This release is tagged in CVS as v1_0_6_0. See the SourceForge site at
+ http://sourceforge.net/projects/slashcode/ for CVS, bug reporting, patch
+ submissions, and downloads.
What is Slash?
@@ -84,5 +84,5 @@ DESCRIPTION
See INSTALL.
AUTHOR
- Patrick Galbraith and Chris Nandor. Last Modified June 13, 2000.
+ Patrick Galbraith and Chris Nandor. Last Modified July 10, 2000.
View
2 Slash.pm
@@ -42,7 +42,7 @@ BEGIN {
require Exporter;
use vars qw($VERSION @ISA @EXPORT @EXPORT_OK %EXPORT_TAGS %I $CRLF);
- $VERSION = '1.0.5';
+ $VERSION = '1.0.6';
@ISA = 'Exporter';
@EXPORT = qw(
sqlSelectMany sqlSelect sqlSelectHash sqlSelectAll approveTag
View
37 docs/INSTALL
@@ -47,7 +47,7 @@ SOFTWARE REQUIREMENTS
Perl modules
- DBI-1.13
+ DBI-1.14
http://search.cpan.org/search?dist=DBI
Data-ShowTable-3.3
@@ -595,31 +595,18 @@ INSTALLATION AND SETUP
blocks data changed. Examine the script and CHANGES and determine if you
want to run the script, or whatever.
- Upgrade 0.9.5 -> 1.0.0
-Just run the script update_db-1.0.0.sql in the sql/updates/1.0.0/ directory, and
-make sure you have the latest code.
+ Other Upgrades
- Upgrade 1.0.0 -> 1.0.0.1
-Just run the script update_db-1.0.0.1.sql in the sql/updates/1.0.0.1/
-directory, and make sure you have the latest code.
-
- Upgrade 1.0.0.1 -> 1.0.2
-Just run the script update_db-1.0.2.sql in the sql/updates/1.0.2/
-directory, and make sure you have the latest code.
-
- Upgrade 1.0.2 -> 1.0.3
-Just run the script formkeys.sql in the sql/updates/1.0.3/
-directory, and make sure you have the latest code. Note that the
-commentkey table is no longer used; feel free to delete if you want to.
-
- Upgrade 1.0.3 -> 1.0.4
-Just run the script formkeys.sql in the sql/updates/1.0.4/
-directory, and make sure you have the latest code.
-
- Upgrade 1.0.4 -> 1.0.5
-Just run the udpate script in the sql/updates/1.0.5/
-directory, and make sure you have the latest code.
+ From To Run Scipts in Dir
+ ------- ------- --------------------
+ 0.9.5 -> 1.0.0 sql/updates/1.0.0/
+ 1.0.0 -> 1.0.0.1 sql/updates/1.0.0.1/
+ 1.0.0.1 -> 1.0.2 sql/updates/1.0.2/
+ 1.0.2 -> 1.0.3 sql/updates/1.0.3/
+ 1.0.3 -> 1.0.4 sql/updates/1.0.4/
+ 1.0.4 -> 1.0.5 sql/updates/1.0.5/
+ 1.0.5 -> 1.0.6 sql/updates/1.0.6/
AUTHOR
- Patrick Galbraith and Chris Nandor. Last Modified June 13, 2000.
+ Patrick Galbraith and Chris Nandor. Last Modified July 10, 2000.
View
58 docs/INSTALL.html
@@ -30,12 +30,7 @@
<LI><A HREF="#Upgrade_0_9_2_0_9_3">Upgrade 0.9.2 -> 0.9.3</A>
<LI><A HREF="#Upgrade_0_9_3_0_9_4">Upgrade 0.9.3 -> 0.9.4</A>
<LI><A HREF="#Upgrade_0_9_4_0_9_5">Upgrade 0.9.4 -> 0.9.5</A>
- <LI><A HREF="#Upgrade_0_9_5_1_0_0">Upgrade 0.9.5 -> 1.0.0</A>
- <LI><A HREF="#Upgrade_1_0_0_1_0_0_1">Upgrade 1.0.0 -> 1.0.0.1</A>
- <LI><A HREF="#Upgrade_1_0_0_1_1_0_2">Upgrade 1.0.0.1 -> 1.0.2</A>
- <LI><A HREF="#Upgrade_1_0_2_1_0_3">Upgrade 1.0.2 -> 1.0.3</A>
- <LI><A HREF="#Upgrade_1_0_3_1_0_4">Upgrade 1.0.3 -> 1.0.4</A>
- <LI><A HREF="#Upgrade_1_0_4_1_0_5">Upgrade 1.0.4 -> 1.0.5</A>
+ <LI><A HREF="#Other_Upgrades">Other Upgrades</A>
</UL>
<LI><A HREF="#AUTHOR">AUTHOR</A>
@@ -152,7 +147,7 @@
</A></H2>
<DL>
-<DT><STRONG><A NAME="item_DBI">DBI-1.13
+<DT><STRONG><A NAME="item_DBI">DBI-1.14
</A></STRONG><DD>
<PRE> <A HREF="http://search.cpan.org/search?dist=DBI">http://search.cpan.org/search?dist=DBI</A>
@@ -1224,53 +1219,28 @@
<P>
<HR>
-<H2><A NAME="Upgrade_0_9_5_1_0_0_Just_run_">Upgrade 0.9.5 -> 1.0.0
-Just run the script update_db-1.0.0.sql in the <EM>sql/updates/1.0.0/</EM> directory, and
-make sure you have the latest code.
+<H2><A NAME="Other_Upgrades">Other Upgrades
</A></H2>
-<P>
-<HR>
-<H2><A NAME="Upgrade_1_0_0_1_0_0_1_Just_ru">Upgrade 1.0.0 -> 1.0.0.1
-Just run the script update_db-1.0.0.1.sql in the <EM>sql/updates/1.0.0.1/</EM>
-directory, and make sure you have the latest code.
-
-</A></H2>
-<P>
-<HR>
-<H2><A NAME="Upgrade_1_0_0_1_1_0_2_Just_ru">Upgrade 1.0.0.1 -> 1.0.2
-Just run the script update_db-1.0.2.sql in the <EM>sql/updates/1.0.2/</EM>
-directory, and make sure you have the latest code.
-
-</A></H2>
-<P>
-<HR>
-<H2><A NAME="Upgrade_1_0_2_1_0_3_Just_run_">Upgrade 1.0.2 -> 1.0.3
-Just run the script formkeys.sql in the <EM>sql/updates/1.0.3/</EM>
-directory, and make sure you have the latest code. Note that the
-commentkey table is no longer used; feel free to delete if you want to.
-
-</A></H2>
-<P>
-<HR>
-<H2><A NAME="Upgrade_1_0_3_1_0_4_Just_run_">Upgrade 1.0.3 -> 1.0.4
-Just run the script formkeys.sql in the <EM>sql/updates/1.0.4/</EM>
-directory, and make sure you have the latest code.
+<PRE> From To Run Scipts in Dir
+ ------- ------- --------------------
+ 0.9.5 -&gt; 1.0.0 sql/updates/1.0.0/
+ 1.0.0 -&gt; 1.0.0.1 sql/updates/1.0.0.1/
+ 1.0.0.1 -&gt; 1.0.2 sql/updates/1.0.2/
+ 1.0.2 -&gt; 1.0.3 sql/updates/1.0.3/
+ 1.0.3 -&gt; 1.0.4 sql/updates/1.0.4/
+ 1.0.4 -&gt; 1.0.5 sql/updates/1.0.5/
+ 1.0.5 -&gt; 1.0.6 sql/updates/1.0.6/
+</PRE>
-</A></H2>
<P>
-<HR>
-<H2><A NAME="Upgrade_1_0_4_1_0_5_Just_run_">Upgrade 1.0.4 -> 1.0.5
-Just run the udpate script in the <EM>sql/updates/1.0.5/</EM>
-directory, and make sure you have the latest code.
-</A></H2>
<P>
<HR>
<H1><A NAME="AUTHOR">AUTHOR
</A></H1>
-Patrick Galbraith and Chris Nandor. Last Modified June 13, 2000.
+Patrick Galbraith and Chris Nandor. Last Modified July 10, 2000.
<P>
View
37 docs/INSTALL.pod
@@ -62,7 +62,7 @@ Refer to your OS distribution.
=over 4
-=item DBI-1.13
+=item DBI-1.14
http://search.cpan.org/search?dist=DBI
@@ -731,31 +731,18 @@ F<blocks_update.sql> should only be run by people who want some of their
blocks data changed. Examine the script and CHANGES and determine if you
want to run the script, or whatever.
-=head2 Upgrade 0.9.5 -> 1.0.0
-Just run the script update_db-1.0.0.sql in the F<sql/updates/1.0.0/> directory, and
-make sure you have the latest code.
+=head2 Other Upgrades
-=head2 Upgrade 1.0.0 -> 1.0.0.1
-Just run the script update_db-1.0.0.1.sql in the F<sql/updates/1.0.0.1/>
-directory, and make sure you have the latest code.
-
-=head2 Upgrade 1.0.0.1 -> 1.0.2
-Just run the script update_db-1.0.2.sql in the F<sql/updates/1.0.2/>
-directory, and make sure you have the latest code.
-
-=head2 Upgrade 1.0.2 -> 1.0.3
-Just run the script formkeys.sql in the F<sql/updates/1.0.3/>
-directory, and make sure you have the latest code. Note that the
-commentkey table is no longer used; feel free to delete if you want to.
-
-=head2 Upgrade 1.0.3 -> 1.0.4
-Just run the script formkeys.sql in the F<sql/updates/1.0.4/>
-directory, and make sure you have the latest code.
-
-=head2 Upgrade 1.0.4 -> 1.0.5
-Just run the udpate script in the F<sql/updates/1.0.5/>
-directory, and make sure you have the latest code.
+ From To Run Scipts in Dir
+ ------- ------- --------------------
+ 0.9.5 -> 1.0.0 sql/updates/1.0.0/
+ 1.0.0 -> 1.0.0.1 sql/updates/1.0.0.1/
+ 1.0.0.1 -> 1.0.2 sql/updates/1.0.2/
+ 1.0.2 -> 1.0.3 sql/updates/1.0.3/
+ 1.0.3 -> 1.0.4 sql/updates/1.0.4/
+ 1.0.4 -> 1.0.5 sql/updates/1.0.5/
+ 1.0.5 -> 1.0.6 sql/updates/1.0.6/
=head1 AUTHOR
-Patrick Galbraith and Chris Nandor. Last Modified June 13, 2000.
+Patrick Galbraith and Chris Nandor. Last Modified July 10, 2000.
View
10 docs/README
@@ -2,7 +2,7 @@ NAME
README - Slashdot Readme
DESCRIPTION
- This is the README file for Slash, release 1.0.5. Please read all
+ This is the README file for Slash, release 1.0.6. Please read all
documentation carefully. The various documents explain the database
schema, the various fields in the database, and some of the reasoning
behind the design of the schema, installation and setup.
@@ -30,9 +30,9 @@ DESCRIPTION
See the Slash web site, with support, docs, latest downloads, FAQs, and
more, at &lt;URL:http://slashcode.com/&gt;.
- This release is tagged in CVS as v1_0_5_0. See the SourceForge site at
- http://sourceforge.net/project/?group_id=4421 for CVS, bug reporting,
- patch submissions, and downloads.
+ This release is tagged in CVS as v1_0_6_0. See the SourceForge site at
+ http://sourceforge.net/projects/slashcode/ for CVS, bug reporting, patch
+ submissions, and downloads.
What is Slash?
@@ -84,5 +84,5 @@ DESCRIPTION
See INSTALL.
AUTHOR
- Patrick Galbraith and Chris Nandor. Last Modified June 13, 2000.
+ Patrick Galbraith and Chris Nandor. Last Modified July 10, 2000.
View
8 docs/README.html
@@ -40,7 +40,7 @@
<H1><A NAME="DESCRIPTION">DESCRIPTION
</A></H1>
-This is the README file for Slash, release 1.0.5. Please read all
+This is the README file for Slash, release 1.0.6. Please read all
documentation carefully. The various documents explain the database schema,
the various fields in the database, and some of the reasoning behind the
design of the schema, installation and setup.
@@ -82,8 +82,8 @@
<P>
-This release is tagged in CVS as v1_0_5_0. See the SourceForge site at <A
-HREF="http://sourceforge.net/project/?group_id=4421">http://sourceforge.net/project/?group_id=4421</A>
+This release is tagged in CVS as v1_0_6_0. See the SourceForge site at <A
+HREF="http://sourceforge.net/projects/slashcode/">http://sourceforge.net/projects/slashcode/</A>
for CVS, bug reporting, patch submissions, and downloads.
@@ -188,7 +188,7 @@
<H1><A NAME="AUTHOR">AUTHOR
</A></H1>
-Patrick Galbraith and Chris Nandor. Last Modified June 13, 2000.
+Patrick Galbraith and Chris Nandor. Last Modified July 10, 2000.
<P>
View
8 docs/README.pod
@@ -4,7 +4,7 @@ README - Slashdot Readme
=head1 DESCRIPTION
-This is the README file for Slash, release 1.0.5. Please read all
+This is the README file for Slash, release 1.0.6. Please read all
documentation carefully. The various documents explain the database
schema, the various fields in the database, and some of the reasoning
behind the design of the schema, installation and setup.
@@ -32,8 +32,8 @@ first.
See the Slash web site, with support, docs, latest downloads, FAQs, and
more, at &lt;URL:http://slashcode.com/&gt;.
-This release is tagged in CVS as v1_0_5_0. See the SourceForge site
-at http://sourceforge.net/project/?group_id=4421 for CVS, bug reporting,
+This release is tagged in CVS as v1_0_6_0. See the SourceForge site
+at http://sourceforge.net/projects/slashcode/ for CVS, bug reporting,
patch submissions, and downloads.
@@ -95,4 +95,4 @@ See F<INSTALL>.
=head1 AUTHOR
-Patrick Galbraith and Chris Nandor. Last Modified June 13, 2000.
+Patrick Galbraith and Chris Nandor. Last Modified July 10, 2000.

0 comments on commit 23f6ce8

Please sign in to comment.
Something went wrong with that request. Please try again.