This is another WishList page, if you'd like a feature to appear in ewiki, that is yet not noted on our FeatureList.

• forum plugin
• rss/rdf feeds (a fragments/ script)
• I vote for RSS/RDF/ATOM feeds. This would really help integrate ewiki into existing weblog/cms frameworks.
• NewFileSystem (nice file handling)--project persued by Andy
• Comments on *WikiPosts
• Comparision feature between two or more versions of the same document like in the Adobe Acrobat's "Compare Documents' feature (but NOT in tune with TextPad's)
• Mailing List integration for email notification to posters in case they admit that they want to be informed about the changes made to the wiki and inputs their email address.
• Login system, customizable (permission on/off to groups) by the admin/owner
  1. this is already there
  2. check out *plugins/auth/README.auth and the _perm_unix or _liveuser plugins
• Support for vpwiki api so external wiki clients can post
  • milky: After some googling I believe this is a proprietary API, and moreover provides no benefits over the more or less standardized WikiXmlRpc interface (many other Wikis support this). So I don't think we should support it, especially if it just means code dup and working with silly authentication tokens (if HTTP is used as transport then HTTP Basic or Digest auth would do much better). No final decision, since with the new *WikiApi lib interface (for XmlPlusRpc and JavaScriptInterpreter) creating function aliases wouldn't be that hard anyhow...
  • milky: It is really tied to one very specific Wiki implementation, I doubt this one makes sense for ewiki.
• Support for mod_rewrite rules to create cruft-free URIs.
  • milky: At least that's already there! See fragments/htaccess for an example. Also you could use PathInfoUrls
    • *rb: I was able to find the info on htaccess (thanks). How do I get rid of the "?id=" in the URI? I've tried a couple options, in both the .htaccess file and removing it from the "Ewiki_Script" define. Thanks for your help.
    • milky: you must put that 'define("EWIKI_SCRIPT","/wiki/index.php/");' line up into config.php or so. Usually that's it. It only must occour before the first/default 'define()', because after this it cannot be overriden anymore.
• blog plugin
  • comments that can be edited by the owner of the blog
  • rss feed per blog
• a plugin to insert a time stamp of the time of the edit (there appears to be a TimeStampMarkup plugin but I can't find it in the live distro).
• IrcChannel where newbies can bug the developers about everything and anything :)
• *SyntaxHighlighting for sourcecode like c++
  • easy to do for PHP, since there is a syntax highlighting module built-in, to seriously integrate something that way, we needed a non-GPL module to include (...*ToDoList)
• Support for the Markdown formatting system, as seen in the Instiki Wiki would be nice. Perhaps making use of PHPMarkdown.

done

• uploading staroffice documents into pages (on-the-fly conversion)
• title != pagename --requested by MM