This is a snapshot of the on-line copy of the JSPWiki FAQ. You should go there for more up-to-date questions and answers.
How do WikiAttachments work ?
Yes, please do see the wiki attachments page for more information.
We just basically look at the modification time of each file, then show them in reversed order. Currently the cutoff point is at 60 days, but you can see a full list of all changes at FullRecentChanges.
However, if a page gets modified twice, the change is only marked up once. This helps to keep the list compact.
Simple. Just put a link to the page DELETEME? as the first item on your page, and at some point the administration will delete these pages. Easier page deletion will be implemented on upcoming versions.
First one to save wins, the next guy gets a warning and a note telling that you should check what changed and try a re-edit.
You can download the JSPWiki distribution package, including a war-file and the source code from JSPWiki:JSPWikiDownload.
Create a link that points to a new (not existing) page using its WikiName. Click question mark (?) after the new link and you will get an editor for the new page.
The reason for this is that linking between WikiPage?s is the way how people find to these pages. If a page is not linked to, nobody can find it and it is thus useless. By forcing people to create a link first, you encourage people to link more and more. In fact, whenever you write something that you think someone could write an explanation for, just make it a hyperlink. Someone will pick it up, someday.
I am pondering the possibility of installing a Wiki on a site I run. Well, I actually have already decided I will, so now I am looking at different implementations. My hosting provider supports perl, python, php and java, so I can really use anyone. However, since the rest of the site is JSP based I prefer to use a JSP based Wiki if possible. I'd like to know which are the advantages or features of JSPWiki? as compared to other JSP WikiWikiWeb:WikiWikiClones. How easy is it to modify the editing markers, for example? --VictorJalencas? PS: BTW, I have just seen all the RPC hooks in the JSPWiki:JSPWikiDevelopment page... seems like I am almost decided ;)
MahlenMorris?: I hope you aren't expecting to get some sort of unbiased answer from the people who hang out here. :)
Well, the reasons i chose to use JSPWiki over others were:
Since I adopted it, the XML-RPC server stuff that Janne put in has grabbed my brain and shook it like a wet kitten, inspiring me to start my first FreeSoftware? project, JSPWiki:Hula. I haven't even had time to implement some of my wackier ideas using that, but stay tuned.
Plus, hey, Janne's been a joy to intercontinentally work with. So that's why I'm using JSPWiki.
Go to the JSPWiki main site, and ask around in there.
This is because the ReferenceManager (the piece of software that is responsible for creating the "Referenced by" -list which you can see in the left menu footer, the unused pages -list and undefined pages -list, scans all wiki pages on your hard drive for links. For a large Wiki on a slow machine, this initialization can take a long time.
Are you using RCSFileProvider? or VersioningFileProvider?? If yes, then the reason is that JSPWiki has to go and find the author for each page separately. Especially with RCSFileProvider, this can take some time.
The solution is to enable the CachingFileProvider?, which keeps a list of recently used pages and author information in memory.
No. JSPWiki uses an entirely flat file structure for pages. The different PageProviders may use subdirectories, but these are not visible to the user.
This is actually a conscious decision: Wikis are flat by nature, and if you want to have a hierarchy, then what you need to do is to define the pages by hand. This is actually very useful - for example, see JSPWikiDevelopment? for a page that contains all pages that have something to do with JSPWiki development.
You can easily "simulate" hierarchies by using dots, but JSPWiki in itself does not limit the structure in any way. --JanneJalkanen?
Go to PageIndex. It is in fact just a regular WikiPage which has just the IndexPlugin from AlainRavet embedded.
The background color is determined in three locations:
Please see JSPWiki:ContributingChanges.
Q: I keep getting the following message on all pages -
A: You're not using any of the versioning file providers: RCSFileProvider or VersioningFileProvider. If you use only FileSystemProvider, then the username is not stored with the changes. --JanneJalkanen?, 15-Nov-02
Some time below, somebody complained about a terribly slowly running JSPWiki - I ran into a similar situation: after having successfully installed JSPWiki 1.8.2 within a LiteWebserver I observed long delays between an HTTP request and the corresponding response from the server (30 seconds and more) - surprisingly, the whole(!) server was blocked during that time, i.e., concurrent requests with other URIs (I'm using that server for a HTML wrapping facility based on servlets which I wrote myself) did not proceed as well!
I then figured out, that the delay might have been caused by problems with DNS lookups (the method HttpRequest.getRemoteHost took very long to complete) and switching off DNS immediately solved the problem.
Consequence: you may not have to switch off DNS resolution yourself (I just used this to verify my assumption), but you may want to change your DNS servers or help your system with a local "hosts" file...
Hoping that this remark is of any help...
You may be right. There should be an option to disable DNS queries (which incidentally, are currently only used by the logging routines. Duh. Perhaps I should just disable them completely.)
Hmmm, can I disable logging by log4j somehow? This package was the one which caused most of the trouble when installing JSPWiki on my LiteWebServer...
Simple: Look at the jspwiki.properties, right at the end. Comment out anything that has anything to do log4j, and you should be set. Unfortunately, since string concatenation is done before the logging, you'll still get the DNS resolution. Easiest is to remove the offending statements from the JSP pages.
This material is based upon work supported by the National Science Foundation under award 0225676. Any opinions, findings and conclusions or recomendations expressed in this material are those of the author(s) and do not necessarily reflect the views of the National Science Foundation (NSF).
Copyright 2004 Partnership for Biodiversity Informatics, University of New Mexico, The Regents of the University of California, and University of Kansas