MoinMoin   Moin Moin Ideas UserPreferences
Help Info Print View Search Diffs Edit
 인덱스   도움말   찾기   대문   바뀐글 

If you miss a feature, have a neat idea or any other suggestion, please put it here.
To discuss the merit of the planned extensions from MoinMoinTodo? or ideas presented here, please use MoinMoinDiscussion.


  1. Current Discussion
    1. Timestamping
    2. Use Server Authentication
    3. EMail send page
    4. Email notification
      1. Subscribers
    5. Structured Text Markup
    6. Macro Collection
    7. Category based headers
    8. Garth's Wishlist
      1. Smart Edit Conflict Detection
      2. Suppress Gratuitous WikiNames
      3. Hotkeys
  2. Another Random Wishlist
  3. Older entries

See also: [BadWikiTag]WikiIdeas [Wiki]WikiWikiSuggestions [WWW]Ward's Meta-Wiki

Your ideas always welcome here...

Current Discussion


Sometimes I use MoinMoin for a weblog-type recording of events. It would be great to have maybe a macro that gets substituted by the current date and time when the user saves the page.

Something like [[TimeStamp]] that would get substituted by 31/01/01 17:05, just one time.

Use Server Authentication

It would be nice if the wiki would automatically determine if a user has been authenticated through a web server and use that for the User. If I happened to be using IIS, I could set it up to authenticate and then use os.environ'REMOTE_USER'? to find out who they are. If I were using Apache, I could do the same. If I were using Orion, etc, etc.

EMail send page

It would be nice if the page, one is currently reading or changing could be sent to an arbitrary email. This could perhaps be a new action and added to a toolbar. -- GM

Email notification

Email notification about changed wiki pages? Yes, definitely.

An alternative is some method of indicating that a particular page is of interest to some person or groups of people. The Attention Page macro on MacroMarket is one attempt towards this end. -- RichardJones?

We have a working system for this at Lineo. The python module for this
is located at [action/]. Our system
works as follows:

To subscribe to a page, a user puts the word "Subscribers" as a heading, at
any level (preceded and follow it with equals signs) anywhere on the page.
Then a user puts their e-mail address under this heading. Multiple e-mail
addresses are allowed. Due to the nature of wikis, anyone can add or
remove their (or anyone elses) "subscription" at any time. On submission
of the edited page, the page "diff" is mailed to all addresses so registered.

For example, to subscribe to this page, I could just put the following on it:

===== Subscribers ===== 

Structured Text Markup

A simple BizarStructuredText
? markup has been written and is available on the ParserMarket page. It is very similar to the StructuredText that Digital Creations developed for [WWW]Zope. Its differences are mostly to do with ease of use. I also included the table markup as defined in the standard wiki markup that MoinMoin ships with. -- RichardJones?

Macro Collection

I realize that this wouldn't be part of the MoinMoin itself, but there should be a repository in the download area for MoinMoin macros that people have written. As of the latest version, it's so easy to write macros, there should be a place where we can place macros we've written so others can get them (I've written some macros that people have asked for in other areas of this site, Even a macro that will look for all macros available on a MoinMoin and list them!) -- Christian Bird -

Either send them directly to me ( or to the moin-dev mailing list ( Then I'll add them to the default distribution or to a new macro collection.

See the new MacroMarket page. Interestingly enough, creating that page did not require any change to the code, though you can directly rip the macros from the subpages.

-- JrgenHermann

Category based headers

It would be interesting to throw a custom header (logo graphic, navigational links, css ) based on a tag similar to a ProcessingInstructions tag. ie: #homepage If no instruction were found, would use site-wide default. This might be non-trivial if header is currently thrown before parsing the page.


Garth's Wishlist

I'm sure these should be put elsewhere, sorted, etc. I'm equally sure that if anyone is really bothered by where I've put them they can refactor them.

I'm currently trying to figure out whether I can adapt MoinMoin so that I can produce a consolidated Wiki and blog site so that Wiki pages and blog entries can point to each other really easily. If the potential seems to be there, I'm sure I'll get around to hacking these guys in eventually.


Smart Edit Conflict Detection
One of my hacks to ZWiki was to suppress edit conflict detection if it figured that someone was colliding with themselves. This enabled the familiar edit-back-edit-back action without letting people collide with each other.

Suppress Gratuitous WikiNames?
In a page which MoinMoin mentions another MoinMoin several times, it's a bit irritating MoinMoin to have every single MoinMoin of them highlighted as a MoinMoin link. I'd like to render only the first in the page or, if there are multiple headings in the document, the first time under a particular heading.

Minor format tweak for the user interface: the accesskey attribute on an INPUT is a major timesaver, letting people save changes without having to reach for their mouse. It's only MSIE, but that's a major proportion of the userbase.

Another Random Wishlist

This is a wishlist from an older version --- some of this stuff has already been done, other stuff is dealt with elsewhere... some of it's novel, hopefully.

  1. Full support for StructuredText (standard?) -- will come, I still owe Richard the adaption of his code
  2. Page delete? -- yes, code is there
  3. Page rename? -- yes, code is there
  4. true raw HTML (cf. HelpOnProcessingInstructions) -- if some1 gives me a reliable HTML filtering module (remove <script>, <object> and the like), no problem
  5. Edit the InterWiki map from within the Wiki.
  6. Extend the ToC macro so that a ToC for one page can be embedded in another
  7. Transclusion would be nice, after all.
  8. More metadata on pages: instead of just last edit time, that + who edited.
  9. edit code for Wiki implementation through the Wiki -- use XSLT
  10. embed Python code directly in Wiki pages? { { { } } }, hilighting will come
  11. number clicks total, number clicks since last rev reported per-page
  12. WhoHasReadThis - read history per-page
  13. MyFavoritePages - an automatic personal most-visited list, for easier nav to common stuff
  14. embeddable diagram tools: cf: [Wiki]HotDraw, JavaHotDraw (?)
  15. smart dynamic "macros" such as "list of 5 most recent changes like xxx..."
  16. More in-site administration / config: WikiDashboard?
  17. Visual Wiki! Check out [Wiki]VisualizeTheWiki. The mind boggles.
  18. More filters / views...
  19. Diff view should give several other pieces of info -- ==> PageInfo?
  20. Filters / sorts on RecentChanges:
  21. More robust "RecentChanges" functionality:
  22. FindSimilar capability. -- LikePages
  23. Blog-like way to post a link to a personal links page via a bookmark.
  24. Bookmark / feed page.
  25. Personal pages / views.
  26. Transitive search (i.e., content / history search).
  27. Eventually: dynamic history!
  28. Easy upload of real docs vi WebDAV, interaction -w- external docs!!!
  29. Grammar checker? -- unlikely

-- JeffBone?, [EMAIL]

Take this with a grain of salt: if you don't even take the time to weed out the done points, why should I care to implement the rest? And there is some pretty heavy stuff in there, even if it might not look like that. A good third is too sketchy to even get what you mean. -- JrgenHermann

This was more of a braindump than a series of requests, Jrgen. Given cycles, I'll be happy to come back and try to clarify and cleanup; but in the meantime, rather than keeping this locked in our Wiki, I thought I'd dump it up here. That way, if there's anything of value in it, somebody else can benefit. But to your question, you shouldn't care to implement anybody's requests, unless it just tickles your fancy. If any of the above does that, great, otherwise, that's fine too. -- JeffBone?

Older entries


Security (against the WikiNature, and possibly not needed when we have versioning):

This is what is left from Piki-Todo:
Also check out the patches in

PythonPowered EditText of this page (last modified 2007-09-14 05:51:18)
FindPage by browsing, searching, or an index
Or try one of these actions: DeletePage, DeleteUploadedFile, LikePages, SpellCheck, UploadFile