Soks 0.0.5 → 0.0.6

data/templates/default/banned_titles.txt

@@ -3,6 +3,42 @@ the
 of
 and
 a
+b
+c
+d
+e
+f
+g
+h
+i
+j
+k
+l
+m
+n
+o
+p
+q
+r
+s
+t
+u
+v
+w
+x
+y
+z
+0
+1
+2
+3
+4
+5
+6
+7
+8
+9
+0
 to
 in
 is

data/templates/default/content/Api%20for%20classes%20to%20modify%20the%20wiki.textile

@@ -0,0 +1,24 @@
+h1. API for classes to modify the wiki
+
+There is a very simple API for classes to modify the wiki.
+
+Any class can register to be notified of changes to the wiki by:
+
+* @@wiki.watch_for( :page_created ) { |event, page, revision| do whatever you want }@
+* @@wiki.watch_for( :page_revised ) { |event, page, revision| do whatever you want }@
+* @@wiki.watch_for( :page_deleted ) { |event, page, revision| do whatever you want }@
+
+These notifications are sent by a separate low priority thread from the one that is interacting with the user.   Using these notifications a class can make changes to the wiki by calling:
+
+<code>
+@wiki.revise( pagename, newcontent, author )
+</code>
+
+The normal place for these classes to be initialized is from the start.rb file.  The normal place for these classes to be stored is in the soks/lib/helpers directory.
+
+Examples of helpers that use this api:
+* [[AutomaticSummary => automatic summaries]] (which in turn are used by the SiteIndex and RecentChanges classes.
+* AutomaticCalendar and AutomaticUpcomingEvents
+* rss2wiki
+* mail2wiki
+* wiki2html

data/templates/default/content/Author.textile

@@ -2,11 +2,11 @@ h1. The Author
 
 Soks was written by Tom Counsell.  He can be reached at tamc@rubyforge.org.  
 
-Further details can be found at http://tom.counsell.org.
-
 h2. Thanks to
 
-* Sebastien Clediere for a patch to fix uploads on windows
+* Bil Kleb for new page categories, meta page improvements and other suggestsions.
+* Sebastien Clediere for a patch to fix uploads on windows and other bugfixes
+* Giovanni Ferro for a patch to allow soks to be used from a memory stick
 * _why for the RedCloth library
 * Austin Ziegler for the Diff:LCS library
 * Matz and ruby-core for the ruby language

data/templates/default/content/Automatic%20Summaries.textile

@@ -1,20 +1,10 @@
 h1. Automatic Summaries
 
-Any class can register to be notified of changes to the wiki by:
-<code>
-@wiki.watch_for( :page_created ) { |event, page, revision| do whatever you want }
-@wiki.watch_for( :page_revised ) { |event, page, revision| do whatever you want }
-@wiki.watch_for( :page_deleted ) { |event, page, revision| do whatever you want }
-</code>
+In lib/helpers/default-helpers.rb you will find an AutomaticSummary class.  This uses the [[api => api for classes to modify the wiki ]] to watch for changes to the wiki, and if the page that is changed matches a given regexp, adds it to a summary page.
 
-These notifications are sent by a separate low priority thread from the one that is interacting with the user.   Using these notifications a class can make changes to the wiki by calling:
-<code>
-@wiki.revise( pagename, newcontent, author )
-</code>
+You can use it by creating a line in your soks-wiki/start.rb file of the form @AutomaticSummary.new( wiki, settings )@ where settings can be (defaults shown):
 
-In soks-helpers.rb you will find some classes that make use of this api.  One particular one is the AutomaticSummary class.  This watches for changes to the wiki, and if the page that is changed matches a given regexp, adds it to a summary page.
-
-It has quite a powerful set of settings, defaults are:
+<pre>
 <code>
 DEFAULT_SETTINGS = {
 	 	:regexp_for_title => /.*/, # These three regexps act as an AND
@@ -32,9 +22,13 @@ DEFAULT_SETTINGS = {
 		:remove_deleted_pages => true, # If false will keep references to deleted pages
 	}
 </code>
+</pre>
+
+h2. Examples
 
-Two examples of its use, included in the soks-helpers.rb file, are the Site Index and the Recent Changes page:
+Two examples of its use, included in the default-helpers.rb file, are the Site Index and the Recent Changes page:
 
+<pre>
 <code>
 AutomaticSummary.new( wiki, {
  	:regexp_for_title => /.*/ # Match all pages
@@ -44,7 +38,9 @@ AutomaticSummary.new( wiki, {
 	:sort_pages_by => :name_for_index,
 } )
 </code>
+</pre>
 
+<pre>
 <code>
 AutomaticSummary.new( wiki, { 
  	:regexp_for_title => /.*/ # Match all pages
@@ -58,8 +54,11 @@ AutomaticSummary.new( wiki, {
 	:remove_deleted_pages => false,
 })
 </code>
+</pre>
 
 You might also use it to construct a basic blog class:
+
+<pre>
 <code>
 AutomaticSummary.new( wiki, {
  	:regexp_for_title => /^Blog:.*/ # Match all pages starting with blog
@@ -73,5 +72,6 @@ AutomaticSummary.new( wiki, {
 	:reverse_sort => true,
 })
 </code>
+</pre>
 
 If you have any other ideas or examples, please add them here

data/templates/default/content/Automatic%20linking%20between%20pages.textile

@@ -3,3 +3,5 @@ h1. Automatic linking between pages
 Any reference to the title of another page in the wiki will be automatically linked.  e.g. home page is linked to the home page.
 
 The links are made left to right, top to bottom, with the longest possible link made at any given time.
+
+The easiest way to create a new page (if your browser supports it - I can only positively say that Safari does) is to highlight the text you want to link from and press ctrl-n. 

data/templates/default/content/Bug%3A%20RSS%20feed%20does%20not%20validate.textile

@@ -0,0 +1,10 @@
+Checking the RSS feed against the validator at http://feedvalidator.org/ reveals four errors:
+
+# The appears to be encoded as "UTF-8", but your server is reporting "US-ASCII"
+# 'utf8' codec can't decode bytes in position 1304-1307: invalid data (maybe a high-bit character?) - it is an umlaut !
+# link must be a full and valid URL - They haven't been url encoded and still contain spaces and the like
+# author must include an email address - Just has the authors name
+
+--
+
+Partially fixed in v-0-0-6 by changing the xml coding.

data/templates/default/content/Bug%3A%20Textile%20mishandles%20paragraphs.textile

@@ -0,0 +1,33 @@
+The "paragraph not kept separate" below should appear on a separate line from "A paragraph" but does not.
+
+<pre>
+Something
+</pre>
+A paragraph
+
+A paragraph not kept separate
+# Blah
+
+The cause seems to be some interaction between the pre block and the following list block.  Putting a blank line after the pre or before the list makes it function as expected:
+
+e.g.
+
+<pre>
+Something
+</pre>
+
+A paragraph
+
+A paragraph not kept separate
+# Blah
+
+or
+
+<pre>
+Something
+</pre>
+A paragraph
+
+A paragraph not kept separate
+
+# Blah

data/templates/default/content/Bug%3A%20Unanticipated%20Rollbacks.textile

@@ -0,0 +1,21 @@
+Bil Kleb reports:
+
+bq. Unfortunately, I don't have any diagnostic data at
+this point, but I have noticed on 3 occasions
+that my home page has been rolled back to the previous
+version when I restart WEBbrick (or when I moved the
+Wiki to a new location/machine?).
+
+I haven't seen this happen, but data loss is a very bad thing, so I would really appreciate any reports anyone has.
+
+If it happens, could you let me know:
+
+# Is it only ever the home page?
+# If you look at the the revisions (edit, show all changes) does it show that the page has been rolled back, or just that the most recent edit never happened at all?
+# If you look at the content/Home%20Page.yaml file, does it show that the most recent edit ever happened?
+# Which version of the page does the content/Home%20Page.textile file contain?
+# Are the timestamps of the Home%20Page.textile and Home%20Page.yaml files wildly different?
+
+Thanks
+
+tamc2

data/templates/default/content/Home%20Page.textile

@@ -2,7 +2,7 @@ h1. Congratulations, you have installed SOKS
 
 Welcome to Soks.  It is yet another wiki, written in ruby.  Please bear in mind that it is alpha, and therefore do not trust your mission critical sites to it.  Please feel free to use and adapt, the soks licence is free and liberal (although if you feel like contributing towards a new mac for the author that would be apreciated).  
 
-p{background:yellow;padding:10px;}. A limited selection of help and bug reports are included here.  For more information, and to share experiences, please visit http://soks.counsell.org. If you are upgrading, you may wish to look at the list of changes.
+p{background:yellow;padding:10px;}. A limited selection of help and bug reports are included here.  For more information, and to share experiences, please visit http://www.soks.org. If you are upgrading, you may wish to look at the list of changes.
 
 [[insert SOKS features]]
 
@@ -10,10 +10,11 @@ p{background:yellow;padding:10px;}. A limited selection of help and bug reports
 
 [[insert known bugs]]
 
+Be sure to check http://www.soks.org/wiki/KnownBugs for the latest bug reports.
+
 h2. Feedback
 
 * Please send me your feedback.  tamc@rubyforge.com.  
-* Or add to the list of known bugs.  
 * To keep track of developments, you may wish to subscribe to the mailing list at http://rubyforge.org/projects/soks.
 
 [[insert picture of a pair of soks]]

data/templates/default/content/How%20to%20administrate%20this%20wiki.textile

@@ -13,32 +13,17 @@ ruby start.rb
 h2. To make your site accessible beyond localhost
 
 Open start.rb in your directory. Un-comment the lines
+
 <code>
 # :url => 'http://localhost:8000',
 # :port => 8000,
 </code>
-and replace them with the url and port you wish the wiki to run on.
-
-h2. To password protect your site.
-
-Open start.rb in your wiki directory. Un-comment and edit the authenticators section and edit the array.  The format is [  [ first regexp to match against title, authenticator to use ],  [ second regexp to match against title, authenticator to use ] .... ]. For example:
 
-# This matches against all the standard 'non editing commands' and doesn't ask for any authentication
-<code>[ %r{/(view|rss|print|find|meta)/.*}, WEBrick::HTTPAuth::NoAuthenticationRequired.new ]</code>
-
-# This doesn't permit any file or picture uploads
-<code>[ %r{/upload/.*}, WEBrick::HTTPAuth::NotPermitted.new ]</code>
-
-# This asks for a site wide password to edit or save changes to the home page
-<code>[ %r{/(edit|save)/home page}, WEBrick::HTTPAuth::SiteWidePassword.new('password','You need to enter the site wide password to edit the home page') ]</code>
-
-# This uses the standard WEBrick authentication system on any page whose name starts with private. The standard WEBrick authentication uses a database of usernames and passwords.  See [[ Gnome's Guide => http://shogo.homelinux.org/~ysantoso/webrickguide/html/html_webrick.html ]] for details.
-<code>[ %r{/(view|edit|save)/private.*},WEBrick::HTTPAuth::BasicAuth.new( :UserDB => htpasswd, :Realm => realm ) ]</code>
+and replace them with the url and port you wish the wiki to run on.
 
-# This is the default. For any page it just asks for a username, but the password can be left blank.
-<code>[ %r{.*}, WEBrick::HTTPAuth::AskForUserName.new( 'No password, just enter a name') ]</code>						
+h2. To password protect your wiki.
 
-Note a big bug is that viewing attached images and files is NOT password protected.  If someone knows how to make WEBrick::HTTPServlet::FileHandler use an authenticator, please let me know. 
+See how to password protect your wiki.
 
 h2. To edit the default site settings used by soks-create-wiki.rb
 

data/templates/default/content/How%20to%20get%20the%20latest%20Soks%20from%20cvs.textile

@@ -0,0 +1,21 @@
+h1. How to get the latest Soks from cvs
+
+If you can't wait for the next release of Soks, then you can check a copy out of  the cvs.  Note that the cvs copy of Soks *{color:red}may have serious bugs*, so please don't try and upgrade a running site with it.  It also contains an outdated set of default content in the templates.
+
+h2. Just download and go
+
+# Download a tarball from http://rubyforge.org/cgi-bin/viewcvs.cgi/soks/soks.tar.gz?tarball=1&cvsroot=soks
+# @tar -xvzf soks.tar.gzip@
+# @cd soks@ and play
+
+h2. Using CVS
+
+Steps:
+# If you don't have a copy of cvs, get it from www.cvshome.org
+# Go into a terminal
+# @cd wherever_you_want_to_download_soks_to@
+# @cvs -d:pserver:anonymous@rubyforge.org:/var/cvs/soks login@
+# Press enter when asked for a password
+# @cvs -z3 -d:pserver:anonymous@rubyforge.org:/var/cvs/soks checkout soks@
+# Soks will now download...
+# @cd soks@ and play.

data/templates/default/content/How%20to%20import%20data%20to%20this%20wiki.textile

@@ -0,0 +1,45 @@
+*The basic question:* How can I import data into Soks?  (both pages and attachments)
+
+h2. Scenario
+
+I have a table worth of information that I would like to load into my Soks wiki.  Each row of the table will become a page and each row has a PDF file associated with it.
+
+What would be the process of dumping my tabular data in the wiki?  Do I merely need to dump out @.textile@ versions of the pages in the contents directory (properly escaped)?  Do I need the YAML revision companions?  Do I merely dump the PDF files in the @attachments@ directory (with proper @.textile@ files also placed in @contents@)?
+
+So far, I have something like,
+<pre>
+projects.each do |p|
+ name = CGI.escape("2005 ii Proposal: #{p.organization}: #{p.title}")
+ File.open(name+'.textile','w') do |f|
+  f.puts "h2. #{p.title}"
+  f.puts
+  f.puts "|Author:|#{p.author}|"
+  f.puts "|Organization:|#{p.organization}|"
+  f.puts "|FTE:|#{p.fte}"
+  f.puts "|Beneficiary:|#{p.beneficiary}|"
+  f.puts "|Submission:|Attached #{p.proposal.gsub(/\s/,'+').sub(/\..*?$/,'')}|"
+ end
+end
+</pre>
+
+Am I heading in the correct direction? --Bil
+
+Yes.  comments:
+# You don't need to escape the file-names, Soks should detect they are not escaped and correct them.
+# You don't need to create revisions files, Soks will create them automatically.
+# If a revision file exists, but is out of date, Soks will bring the revision file up to date.
+# (I think you have realised this, but just in case) To import the PDFs, you need to both put them in the attachment directory and create a page in the content directory whose name starts 'attached ' and whose content is @/attachment/filenameof.pdf@
+# You can do this while the wiki is running (soks periodically scans the content folder and updates itself with any changes[1]) but if you are adding a lot of files it is best to stop the wiki while the changes are made.
+-- tamc2
+
+An alternative (only appropriate if you plan to update the wiki from the database frequently) would be to write a helper class that you call from start.rb and that uses the @wiki.revise(pagename, content, author) methods.
+
+A third alternative would be to use DRb (e.g. write @require 'drb'@  @DRb.start_service( 'druby://localhost:9001', view)@ somewhere in your start.rb file) and then write a script (or use irb) to remotely call the @wiki.revise( pagename, content, author) methods.
+
+fn1.  Changes detected by looking at the file's timestamp, not its content.
+
+----
+
+Puzzled by Textile's non-rendering of the paragraph break between my signature above and Tom's "Yes.  Comments:" --Bil
+
+I've had a little look and seems to be an interaction between the pre tag and the following list.  Corrected here and noted at Bug: Textile mishandles paragraphs.  I think it is Redcloth, so will report there.

data/templates/default/content/How%20to%20install%20Soks.textile

@@ -2,16 +2,18 @@ h1. How to install Soks
 
 h2. Requirements
 
-Essential: Ruby 1.8.2 from http://www.ruby-lang.org/en/
-Preferred: Ruby Gems from http://rubyforge.org/projects/rubygems/
+# Essential: Ruby 1.8.2 from http://www.ruby-lang.org/en/
+# Preferred: Ruby Gems from http://rubyforge.org/projects/rubygems/
 
 h2. The easy install
 
 If you have ruby gems, type:
-<code>
-gem install Soks
-soks-create-wiki.rb
-</code>
+
+@gem install Soks@
+
+then
+
+@soks-create-wiki.rb@ (Gems should have installed this in your path so you can type it anywhere, if it hasn't, look in your ruby library under @gems/Soks-X.X.X/bin/@ )
 
 ...and then surf to http://localhost:8000
 
@@ -19,9 +21,11 @@ h2. The harder install
 
 Download the latest version of Soks from http://rubyforge.org/frs/?group_id=481
 
+<pre>
 <code>
-tar -xvzf Soks-0.0.3.tgz
-ruby Soks-0.0.3/bin/soks-create-wiki.rb
+tar -xvzf Soks-x.x.x.tgz
+ruby Soks-x.x.x/bin/soks-create-wiki.rb
 </code>
+</pre>
 
 ...and then surf to http://localhost:8000

data/templates/default/content/How%20to%20password%20protect%20your%20wiki.textile

@@ -0,0 +1,43 @@
+h1. How to password protect your wiki
+
+You can specify what authentication to be used based on a regular expression match against the url used to access the page.
+
+Open @start.rb@ in your wiki directory. Un-comment and edit the authenticators section and edit the array.  The format is [  [ first regexp to match against title, authenticator to use ],  [ second regexp to match against title, authenticator to use ] ... ]. For example:
+
+* The following matches against all the standard 'non editing commands' and doesn't ask for any authentication:
+
+<code>[ %r{/(view|rss|print|find|meta)/.*}, WEBrick::HTTPAuth::NoAuthenticationRequired.new ]</code>
+
+* The following doesn't permit any file or picture uploads:
+
+<code>[ %r{/upload/.*}, WEBrick::HTTPAuth::NotPermitted.new ]</code>
+
+* The following asks for a site wide password to edit or save changes to the home page:
+
+<code>[ %r{/(edit|save)/home page}, WEBrick::HTTPAuth::SiteWidePassword.new('password','You need to enter the site wide password to edit the home page') ]</code>
+
+* The following uses the standard WEBrick authentication system on any page whose name starts with private. The standard WEBrick authentication uses a database of usernames and passwords.  See [[ Gnome's Guide => http://shogo.homelinux.org/~ysantoso/webrickguide/html/html_webrick.html ]] for details.
+
+<code>[ %r{/(view|edit|save)/private.*},WEBrick::HTTPAuth::BasicAuth.new( :UserDB => htpasswd, :Realm => realm ) ]</code>
+
+* The following is the default. For any page it just asks for a username, but the password can be left blank.
+
+<code>[ %r{.*}, WEBrick::HTTPAuth::AskForUserName.new( 'No password, just enter a name') ]</code>			
+
+* BasicAuth isn't very secure as it transfers passwords over plaintext. If you can cope with some incompatability with very old browsers, DigestAuth is more secure. To implement DigestAuth:
+# run this command: @htdigest -c /path/to/your/soks-wiki/htdigest "name of your realm" yourusername@ and enter your password. On gentoo, the full path is @/usr/sbin/htdigest2@
+# Add this line into start.rb, inside the authenticators= block: @[ %r{/(view|edit|save)/private.*},WEBrick::HTTPAuth::DigestAuth.new( :UserDB => WEBrick::HTTPAuth::Htdigest.new('/path/to/your/soks-wiki/htdigest'), :Realm => "name of your realm") ]@
+# Uncomment this line: @:authenticators => authenticators@ 
+-- Skorgu
+
+Note a big bug is that viewing attached images and files is NOT password protected.  This will be fixed in version 0.0.6.
+
+----
+
+Is there any means to changing the authentication on the fly like how the editable "sidebar page" works?  (Have a "master" page that is access controlled, on which one would put other page links that would then become access controlled.) --Bil
+
+----
+
+Can someone point me to an example (or outline the steps) to having the user names checked for validity by an LDAP server ?  (Note: I asked a similar question on the Webricken mailing list.) --Bil
+
+Not used LDAP myself, but the example at http://dataspill.org/posts/show/4 seems to show how one might communicate with the LDAP server to check valididty.  This would need to be inserted into a WEBrick authenticator. If you just duplicate the code of an existing WEBrick authenticator (e.g. 1.8/webrick/httpauth/basicath.rb) you should be able to do a few tweaks to the authenticate method to get what you want.  --tamc2

data/templates/default/content/How%20to%20report%20a%20bug.textile

@@ -2,7 +2,7 @@ h1. How to report a bug
 
 I really appreciate bug reports.
 
-Please go to http://soks.counsell.org and create a new page whose title starts with bug:, e.g. @bug: does not make tea@.
+Please go to http://www.soks.org and create a new page whose title starts with bug:, e.g. @bug: does not make tea@.
 
 In that page, please give as much information as you can and leave some contact details.
 

data/templates/default/content/How%20to%20use%20the%20keyboard%20shortcuts.textile

@@ -11,3 +11,5 @@ Soks has a number of keyboard short cuts.  Depending on your browser, only some
 * ctrl-h: Home page
 * ctrl-i: Site Index
 * ctrl-r: Recent changes to this site
+
+Note: on Linux/Firefox, substitute "meta" or "alt" for "ctrl".

data/templates/default/content/How%20to%20use%20this%20wiki.textile

@@ -21,6 +21,7 @@ h2. Editing Pages
 * To alias a link: <notextile> [[ a different name for </notextile>=><notextile> site index ]] </notextile>
 * To insert another page: <notextile>[ [ insert site index ]]</notextile>
 * This is particularly usefull if you want to insert a picture: <notextile>[ [ insert picture of the soks logo ]]</notextile>
+* It can also be usefull to save one step in directing people to download an attached file: <notextile>[ [ insert attached file to download ]]</notextile>.
 
 h2. Searching
 

data/templates/default/content/Instructions%20and%20Howtos.textile

@@ -1,6 +1,6 @@
 h2. Instructions and Howtos
 
-p{font-size: x-small;}. Instructions and Howtos was created automatically from pages whose title matches /^How to /i.
+p{font-size: x-small;}. Instructions and Howtos was created automatically from pages whose title matches ==/^How to /i==.
 
 <automaticsummary>
 
@@ -13,6 +13,9 @@ p{font-size: x-small;}. Instructions and Howtos was created automatically from p
 * [[ How to use the keyboard shortcuts ]] 
 * [[ How to use this wiki ]] 
 * [[ How to report a bug ]] 
+* [[ How to get the latest Soks from cvs ]] 
+* [[ How to password protect your wiki ]] 
+* [[ How to import data to this wiki ]] 
 
 
 </automaticsummary>

data/templates/default/content/Known%20bugs.textile

@@ -5,10 +5,13 @@ p{font-size: x-small;}. Known bugs was created automatically from pages whose ti
 <automaticsummary>
 
 * [[ Bug: Does not make use of if-modified-since request headers ]] revised on 2005 Jan 25 18:23 by AutomaticImport
-* [[ Bug: Uploads are not password protected ]] revised on 2005 Jan 25 18:23 by AutomaticImport
 * [[ Bug: GEM limits title lengths ]] revised on 2005 Jan 26 08:55 by tamc2
-* [[ Bug: Punctuation in page titles still problematic ]] revised on 2005 Feb 12 10:08 by tamc2
 * [[ Bug: notextile does not prevent page inserts ]] revised on 2005 Feb 12 12:00 by tamc2
+* [[ Bug: RSS feed does not validate ]] revised on 2005 Mar 15 16:24 by tamc2
+* [[ Bug: Unanticipated Rollbacks ]] revised on 2005 Mar 08 05:50 by Bil Kleb
+* [[ Bug: Textile mishandles paragraphs ]] revised on 2005 Mar 09 05:13 by tamc2
+* [[ bug: competing edits ]] revised on 2005 Mar 10 14:47 by tamc2
+
 
 </automaticsummary>
 

data/templates/default/content/List%20of%20changes.textile

@@ -1,5 +1,54 @@
 h1. List of changes
 
+h2. Between v-0-0-6 and v-0-0-5
+
+h3. Features
+
+* The default template now includes a 'sidebar page' that can be edited inside the wiki. (Thanks to Bil Kleb).
+* Changed the way the soks libraries are required to hopefully allow a wiki to be more easily moved between machines (Thanks to Giovanni Ferro).
+* Some new settings:
+** Setting @:server_type =>  WEBrick::Daemon@ in start.rb causes Soks to try and fork into a separate process.  By default this is off.  (Thanks to Remy Drouilhet)
+** The name of the home page is now a setting in start.rb (@:home_page => "home page"@).
+** Setting @:redcloth_hard_breaks => true@ in start.rb causes Redcloth to revert to the 2.x approach of turning every newline to a @<br />@. This is off by default (i.e. the default works like Redcloth 3.x).  (Thanks to Seb Clediere.)
+* Roughed up a wiki2html helper that maintains a static html copy of the site in sync with the dynamic copy.
+* Toned down the colors and tweaked the layout of the default wiki look.
+* Removed the 'instiki' and the 'rails' templates from the distribution, because I haven't kept them up to date.
+
+h3. Refactoring
+
+* Filehandler servlet now incorporated into the WikiServlet.
+* General cleanup in WikiServlet 
+* Rewrote the RollingMatch class (in soks-view, deals with automatic linking) to be less complex and a little bit faster.
+
+h3. Bugfixes
+
+* Fixed Bug: Time per change on meta page view incorrect
+* Fixed Bug: Punctuation in page titles still problematic by adding two validations.  The first is a piece of javascript that warns the user from using problematic punctuation, the second is in the servlet and removes all problematic punctuation.  As a side effect, this has fixed Bug: ampersand in page name creates missing links that work .
+* Fixed Bug: Search textarea and button rendered without vertical separation by removing the search button.  It wasn't needed, and IMO looked clunky.
+* Fixed Bug: Certain text crashes yaml revision loading
+* Fixed Bug: Do not save and delete links confusing on edit page by replacing the links with form buttons.
+* Shutting down Soks with ctrl-c (which is trapped by the TERM signal - does this work on Windows? non OSX unix?) now waits until all the running helpers have finished making their changes to the wiki.  This should have fixed bug: Halting can corrupt revisions and may help with Bug: Unanticipated Rollbacks if graceless shutdown is the cause.  
+* Fixed Bug: Update frequency rounds inappropriately in meta view using Bil Kleb's extension to the Numeric class.
+* Fixed Bug: AutomaticRecentChanges ignores changes parameter
+* Fixed Bug: Uploads are not password protected 
+* Fixed Bug: Pictures and Attachments linked to site root
+* Partially fixed Bug: RSS feed does not validate, in that I changed the encoding given in the xml so that umlauts work.
+* Partially fixed Bug: Upload filenames needlessly mangled, in that it now only removes spaces from filename (which is unfortunately required for RedCloth to be able to make links to the file).
+* Robots.txt in the default template dissalows the 'meta' page view
+
+h3. Bugs remaining
+
+Seems like I've accumulated enough changes above to start thinking about another release.  This means that some bugs are not going to be fixed for this release.  If you strongly object, please let me know.
+* Bug: Does not make use of if-modified-since request headers
+* Bug: GEM limits title lengths
+* Bug: notextile does not prevent page inserts
+* Bug: Textile mishandles paragraphs
+* Bug: competing edits
+
+The following bugs have only been partially fixed, so some problems may remain
+* Bug: RSS feed does not validate
+* Bug: Unanticipated Rollbacks
+
 h2. Between v-0-0-5 and v-0-0-4
 
 h3. Features

data/templates/default/content/New%20Recent%20Changes%20class.textile

@@ -0,0 +1,58 @@
+h1. New recent changes class
+
+The current recent changes helper is pretty simple, and relies on automatic summary to do the dirty work.  
+
+Bil Kleb made the following request:
+
+1. Filter out the changes made by /^Automatic/ authors
+
+2. Chunk changes to a given page by day, i.e, collapse
+
+<pre>
+<code>
+    Feedback revised on 2005 Mar 05 04:37 by Bil Kleb
+    Feedback revised on 2005 Mar 05 04:36 by Bil Kleb
+    Feedback revised on 2005 Mar 05 04:35 by Bil Kleb
+    Feedback revised on 2005 Mar 05 04:34 by Bil Kleb
+    Feedback revised on 2005 Mar 05 04:33 by Bil Kleb
+</pre>
+</code>
+
+to something like usemod produces:
+
+<pre>
+<code>
+    March 5, 2005
+
+    * (diff) Feedback 4:37 am (5 changes) Bil Kleb
+</pre>
+</code>
+
+where "diff" shows you that last diff and "changes" shows you all the changes to this page
+
+This would require the following changes:
+
+1) Re-write the AutomaticRecentchanges so that it creates the page itself rather than passing off to an AutomaticSummary class.
+
+That would involve:
+a) registering with the wiki to be notified of page changes ( wiki.watch_for( :page_revised ) { |event, page, revision| do_something_with( page, revision ) }
+b) when a revision event occurs, update some data structure of the recent revisions
+c) converting the data structure into a textile representation and writing to the wiki ( wiki.revise pagename, content, author )
+
+2) Create some new 'view' types that would have the 'diff' and the 'changes' laid out as you would like.
+
+New views can be created in the views directory of the wiki.  If the wiki receives a request for a url http://whatever.com/diff/feedback it will look in the views folder for a file called Page_diff.rhtml.  This is expected to be an Erb file.  The ruby in the erb file is bound to the context of the View class, so has local variables: pagename (String), page (Page), renderedview (String - html from textile), and access to the methods of the View and the Wiki classes.
+
+3) (Maybe) the changes and diff probably want to point to a specific set of changes / diff.  That would mean would need to work out a way of getting a 'revision' variable from the url, through to the view method in the view class.
+
+I guess the format for the url could be:
+a) http://whaterver.com/diff/3/feedback
+or
+b) http://whaterver.com/diff/feedback?revision=3
+
+I guess I visually prefer a) but b) would be easier to code.
+
+Would then need to change:
+lib/soks-servlet.rb/WikiServlet#service to extract the desired revision number from the request (e.g. by looking at request.query['revision']) and then edit the call to view.view to have an extra parameter (e.g. view(pagename, view, person, revision)).
+
+Then modify lib/soks-view.rb/View#view to accept the extra parameter.  It would then be available as a local variable in the Page_diff.rhtml