December 1, 2007: Bugfix release 1.0.4 now available at http://www.usemod.com/wikicode/usemod-1.0.4.tar.gz. A version for Windows users is available at http://www.usemod.com/wikicode/usemod-1.0.4.zip. --MarkusLude
September 12, 2007: Bugfix release 1.0.3 now available at http://www.usemod.com/wikicode/usemod-1.0.3.tar.gz. A version for Windows users is available at http://www.usemod.com/wikicode/usemod-1.0.3.zip. --MarkusLude
August 26, 2007: Bugfix release 1.0.2 now available at http://www.usemod.com/wikicode/usemod-1.0.2.tar.gz. A version for Windows users is available at http://www.usemod.com/wikicode/usemod-1.0.2.zip. --MarkusLude
July 9, 2007: Bugfix release 1.0.1 is now available at http://www.usemod.com/wikicode/usemod-1.0.1.tar.gz. I hope to add more patches during next weeks/months. --MarkusLude
September 12, 2003: Version 1.0 is now available at http://www.usemod.com/wikicode/usemod10.tar.gz (see note below for WGET users)
People considering a new UseModWiki installation may also be interested in OddMuse (a UseModWiki descendant) which adds (and removes) several features from UseModWiki 0.92. PatchedScripts also has links to a few other variants.
If you download UseModWiki, please send mail to [email@example.com] to be notified when newer versions are released. There is also a /MailingList for major announcements (like this one). --CliffordAdams
The .zip distribution includes a few minor changes from the standard distribution:
See WikiPatches for diverse patches applicable to 0.92
See WikiBugs/DownloadPageRedirectsToMSWithWget if you get strange results (the Microsoft home page) when using wget. That page also includes a workaround for the problem.
I have a different WGET question:
I want to extract a static snapshot of my wiki (to read offline e.g.), but wget only grabs one page because it thinks it has already downloaded 'wiki.pl'. Is it possible to convince wget to follow links? I realize this is a rather non-trivial problem since, wiki.pl?MyPage may be different than wiki.pl?MyPage&foo=bar etc. ...DougConley
Q - I think it's weird, but when I download the file, the filetype name is missing. You know, names like EXE, INI, DLL, or TXT. What can I do about that?
The problem with using .txt is that on a lot of standard systems they will be opened with Notepad, which doesn't handle the UNIX-style end-of-lines (\n only) well at all. (I did not want to deal with a separate Windows version of the documentation files.) I figured that more advanced users would rename the files. --CliffordAdams
Oooh, I'm so advanced, I renamed a few files! Hehe. -DavidWall
What about using the .rtf format? It works in both Unix and Windows afaik :-) -- MikaelSorlin
The format of documentation files should remain plain text. The suggestion was not about the format, but about the file extension.
Since version 1.0.2 I renamed the documentation files in the .zip distribution to .txt and converted them to dos line breaks. --MarkusLude
Does anyone have input on installing the wiki on a server that won't reveal the path to their cgi bin? I called my hosting company and they don't support telnet and won't tell me the damn path. What's an alternative? As far as I know I'll need to path to put into the wiki code, can I forgo this? If so please give me directions.
Change your hosting provider. http://pair.com offers ssh access. So does http://he.net It's possible to run the script outside cgi-bin on some servers if you set the +x bit. It's much easier to set up if you can change permission bits from a shell.
i didnt have telnet access . I used cgitelnet.pl - http://www.rohitab.com/cgiscripts/cgitelnet.html, which effectively gives you some telnet access