This fixes the caching problem http://golem.ph.utexas.edu/instiki/show/Known+Bugs?rev=13#Caching which afflicts some installations of 0.16.3. With the patch, it's no longer necessary that the Instiki directory be owned by the instiki user (yay!).
Dunno why this was buggered again. ":back" doesn't seem to function as it used to. Also, when uploading a file from page "foo", it's important to return to "foo" after a successful upload, rather than redirecting to the HomePage. Finally, a favicon tweak.
Add a favicon for Instiki. Also, add an id for the svg path (which makes it reusable).
Use a SPAN instead of a DIV in the logo. H1 allows only inline content.
A Maruku-syntax <div> with an unclosed IAL (and, it seems, at least one equation) would cause Instiki to hang. Badly. Requiring a 'kill -9' to terminate it. Reverting the OpenDiv and CloseDiv Regexps to my, more simple-minded, versions fixes the problem.
Adobe Illustrator's path optimizer produces much smoother results than Sam's program (and it's WYSIWYG).
Thanks to Sam Ruby, SVG logo is half the size it was before. Also, use the "wrapper div" trick to make the logo work in older browsers.
Textile and RDoc users can't see the SVG anyway, so don't bother rendering it.
Added an SVG logo for Instiki.
… check for other possible missing dirs.
WEBrick in Rack doesn't respond to TERM signals. This is a problem (especially on MacOSX). Make sure we use our bundled version instead.
Instiki now runs on the Rails 2.3.0 Candidate Release. Among other improvements, this means that it now automagically selects between WEBrick and Mongrel. Just run ./instiki --daemon
Links in the 'show' action should be to the 'show' action. Links in the 'published' action should be to the 'published' action. Try to focus, Distler!
The BlahTeX/PNG code was busted by Revision 344. Fixed now. Ari better supply me with a test suite, so this doesn't happen again.
Functional Test for the new behaviour of Revisions 344-345.
... should still allow you to manually upload files and have them render. Fixed.
On Webs with file uploads enabled, uploaded files were stored (in version 0.16.1 and earlier) in the public/ directory. This was a security threat. A miscreant could upload a .html file. When a user clicked on the link to the file, it was opened (unsanitized) in the browser. As of version 0.16.2, uploaded files are stored in the webs/ directory. Now, when the user clicks on the link, the file is sent with the Content-Disposition: attachment header set, which causes the file to be downloaded, rather than opened in the browser. As always, files downloaded from the internets should be treated with caution. At least, this way, they are not aoutomatically opened in the browser. To move your existing uploaded files to the new location, do a rake upgrade_instiki