Please leave your comments or suggestions here:

Is there any way to have a wiki word (two capitalized words placed together) not be a link?

Yes - by putting something into the word to break it up. Of course you want this 'something' to be invisible to users, so the most obvious one is an HTML comment, which is achieved with double square brackets. Another option is using 6 apostrophes in a row, as users of the original wiki [1] do. (Effectively this turns on bold and turns it off again immediately.) Below are a couple of examples - click edit to view the source:

Thanks!!! More questions:

  1. Can Monkeyweb do tables?

    No, the nearest you can get is the old-fashioned method of using a <pre> block. Because this appears in a non-proportonal font, and spaces are all honoured, you can create a basic table of data. Of course it is not nearly the same as real tables.

  2. What about having links to external web pages that aren't explicitly shown (like having a word represent the link instead of having the whole link shown to the reader)?

    These are known as Free Links, and no, they are not implemented in Monkey Wiki

  3. Can you do bookmarks? I have a page of vendors I'm building and I'd like to be able to link to the actual location of the vendor in my list of vendors.

    Again, not implemented I'm afraid

  4. Is it possible to have a list not start with a blank line above it? I'd like to have the title of the list be right above (no spaces) the list.

    Interesting. If you look at the HTML source generated by Monkey Wiki, there is nothing at the beginning of a list that explicitly inserts a blank line - this is simply how a browser displays it. If you want to change that, I'm sure it is possible with a stylesheet. Because you can Define Templates, you can easily ensure that each page in your wiki is asscociated with a stylesheet. In turn you can code for lists to appear exactly as you want.

  5. What about redirecting the Edit ... etc links if you select to redirect the page. When I choose to rewrite the URL, some of my urls are pretty (the actual pages) whilst others are the full path (Edit, Rename, etc). I happen to have /private/* in my path - which I was hoping to hide from the end user. The page links nicely hide that --- but the supplemntary links like Goto, Edit, Rename etc give it away. Nice engine by the way. Drop and go!

    Ironically this was exactly how I wrote Monkey Wiki orginally, but changed to the current setup. See Spider Problem. To revert to the behaviour you are seeking you would need to hack the get_href method - it should be quite easy, but feel free to contact me if you need a hand:

    I considered the ugly URL issue at the time I changed it, but felt that it was justified: 99% of usage will invlove users following the pretty URLs, and where a different action is invoked, it seems more natural and honest to show that a script is being called with various arguments, rather than show an obviously contrived call to an HTML file - normal HTML files are not executable! Also note that in any case, the script will be called by name (with a POST request) when a user commits an edit/delete/rename.

    Ah. I will try that. One other thing I've edited is the (.html) extension part of the script. I prefer a slightly more RESTful URL so I dropped the extension altogether in favor of syntax like /monkey/FrontPage and /monkey/StuffTodo. It was easy to find and edit and works just fine. Thanks again for the script.

A lot of the features not implemented were omitted quite deliberately: the simpler the feature-set, the more people will be comfortable using it. I have never been a great believer in any truly sophisticated editing capablities in a wiki - if you need them, you might as well let your users write HTML tags (or a subset of them), or it may be that a full-blown CMS would be more suitable than a wiki at all.

I understand. Thanks for your comments and your hard work.

The system doesn't seem to support UNICODE languages like Chinese. Just tried typing a few Chinese characters and they showed up in unicode encoding in the page. Other than that, it looks need. Wish to have table support :)

I just downloaded Monkey Wiki - it's pretty and has a number of features I missed while trying Piki Piki this weekend. I'd like to know if you have thought about adding:

Per Erik Strandberg

PS: Aaaah, a rename feature "There's no end to the possibilities..." niceness maximalius.

Yes I have thought about adding an upload image feature, and am now working on one. I am a little torn between keeping Monkey Wiki as a single-file script for simplicity, and having a core module that is small and neat. It may be that I write a 'macros' module and have various functions like image upload in there that can be added to whenever soemthing arises.

As for accented characters, I have done some minor rewriting to allow for this, but I have to confess that programming for different locales is not a strong point, and I am not 100% confident I have yet taken all the necessary factors into account.

I discovered yesterday that images are considered to be links if the have an extension such as .JPG instead of .jpg:

I'll try to look in the source and see if it is trivial to change (it probably is), just thought you'd like to know.

Thanks again for an excellent tool.

/Per Erik Strandberg [2]

Good point! The phrase dealing with images is of course case-sensitive, but should be quite easy to rectify.

I'm no expert when it comes to reg-exp's, but this worked for me (line 78 in my file)


I guess it's easier to make the reg exp case insensitive, but I've forgotten how to do that and this just worked :D

Here's a working example: [3]

/Per Erik Strandberg

Mr Monkey I just realized that I have no Idea of who the monkey is and why this Wiki engine is called MonkeyWiki. Could you please elaborate on that?


Last modified: Sat Mar 1 10:31:53 2014

Valid XHTML 1.0 Strict Valid CSS! [Python Powered] hosting by gradwell dot com Ltd
Wiki Spam controlled by LinkSleeve