Well, 1.1.6 was released last night; today it got posted on freshmeat.net
as well, so for the day I have to babysit FrontPage on
phpwiki.sourceforge.net because people occasionally edit it.
I had to disable part of the [more info] page so it would not render the
source of the page; it turns out this would allow people to render HTML
since it goes through unchecked. A simple patch would be to do a s/// for
<, > and &.
You can see a DBM-based copy at http://phpwiki.sourceforge.net/1.1.6/. I
haven't looked at the bug in RecentChanges yet, speaking of which:
I know some time ago, very early in the development of 1.1, I rewrote
UpdateRecentChanges so it listed the pages newest-first instead of putting
the newest at the bottom. I wonder what happened to this change? I don't
know if I have a copy of it still.
The mSQL support: I started on this because the web server I co-admin,
wcsb.org, has mSQL running on it. It turns out to be much harder to port
to mSQL than Postgresql (which was quite easy) because the TEXT data type,
which can take any amount of text but cannot be used in LIKE clauses. This
gave me endless headaches all weekend.
I don't want to limit pages to lengths of 1,000 or 10,000 chars, so after
trying two approaches that were dead ends, I decided on putting the pages
in a separate table. The page content would be divided up into lines of 80
chars in length, and the white space would be preserved. This was tricky
to code but last night I finally got it almost right (two bugs to address
still). This approach will be very space efficient (for mSQL at least ;-)
I think the next thing to work on is the HitCount. It should be
straightforward to add to PhpWiki. Do we want to include it at the bottom
of each page? Also, "version" provides a way to count how many times a
page was edited. Do we want to add this info to the bottom of the page
too, or leave it in [more info] ?
Hear FM quality freeform radio through the Internet: http://wcsb.org/
home page: http://www.wcsb.org/~swain