The other thing thats needed is a wiki markup filter. I think there were a couple of them started, including the one in Liquid. None of them did what I wanted, so I put together a wiki markup filter using the Pear Text_Wiki package. I haven't contributed it yet since I'm fairly new to Drupal and it was a fast job (not to mention the others that are already there somewhere). But people are welcome to go get it, and I'd be happy to contribute it. I don't have lots of time to work with it though, and once it got to the level that it does what I needed... Anyway, if anybody could use it, its here until I get around to getting an account to add it to drupal.org. http://davidcaylor.com/drupal_text_wiki_filter On Wednesday 23 August 2006 12:17, Bèr Kessels wrote:
Op woensdag 23 augustus 2006 19:24, schreef Neil Drumm:
I recently helped set up a wiki for one of our client sites. We used: - CCK (4.7) - TinyMCE - freelinking - input_format_restrictions - a formapi hack module that lets you define the default and available input formats for each node type [1]. I plan on making a patch for core for this, but haven't had time. The first step, in case anyone wants it, is being able to set the default and available input formats when calling the function which generates that form widget.
Here is my recipe: book module (It's great to be able to actually structure a wiki!) node_privacy_by_role (we needed three groups that could not edit or see eachothers content. If you need more OG configured for books will be a good option) freelinking markdown icw with a properly configured input format. (My client found markdown far more "natural" then HTML or WikiSyntax) inline module upload module (icw inline provides a simple way to include images)
Bèr