Wiki

After spending/wasting a lot of time this weekend trying to get a functioning wiki built using a combination of wikitools, pearwiki filter and freelinks module (in combination with TinyMCE).

I ran into a hell of a lot of problems trying to implement the PEARWiki filter in conjunction with Wikitools and TinyMCE and in the end I just gave up completely!

I'm just wondering how to import mediawiki XML and turning it into a wikitools drupal system. This should theoretically be simple, but I'm not sure where to begin.

Based on the Refactor revisions to use a version control system proposal changed, I post this proposal.

The problem

Core only allows the first user that sumbit the node form to save the changes; so the others have to see the saved node again and manually make the changes, hoping no other user save it before he does it. Clearly, it's a really slow way to make a contributed document.

I am trying to install the pear wiki filter, but I am not understanding this part of the readme instructions:

Use the following command to get the CVS Version of all the required PEAR packages
(which I would recommend at least for the Mediawiki parser):

cvs -d :pserver:cvsread@cvs.php.net:/repository checkout -d Text pear/Text_Wiki/Text

Any help? I think it means to use some sort of command line, which I am unfamiliar. Is there a way to do it without it?

I'm currently working on integrating the Mediawiki parser into Drupal. The basics work: formatting, links, templates, images.
Two major things are still missing: category links and namespaces. Cagegory associations can easily be mapped into taxonomy module. The question remains for namespaces.

I'm debating whether to integrate wiki (a simple solution that I'm familiar with and would basically take care of all my needs in 1 fell swoop), or use various modules to do a native Drupal wiki.

So to help me make this decision, I'm asking if the Drupal wiki modules are able to duplicate at least all the basic functions of mediawiki. I'm a little confused about freelinking module. Is it neccessary? Shouldn't the wikitools module be able to do the same thing? Or am I missing something?

Proposal added to official ideas list at http://drupal.org/node/237619

The node_revisions table currently stores a full copy of everything for every revision.

For space considerations it would make a lot of sense to store it as diffs instead.
Many sites like drupal.org also have issues with simultaneous editing - using diffs might allow for merging of edits rather than the current locking system.

Note that in D7 core, node_revisions may well be handled similarly to CCK fields - so something extensible to both models is likely to have the most chance of future use.

I like wikimedia as it is, the syntax and everything are very good for most documents, the only thing I don't like, is the discussion pages. is it possible to just have the discussion (talk) pages link into drupal ? instead of going for full integration. How hard would that be ?

Hi folks,

Have any of you Drupal wiki pioneers come up with a good way of mimicking namespaces? We're looking for a wiki solution for a corporate intranet and we already use Drupal for some other things... Seems like that is one of the missing pieces.

The main contenders besides Drupal for the wiki are Confluence, WikiSpaces.net, Dokuwiki and Mediawiki.

Any feedback or thoughts appreciated. Thanks!

Following the release of the Flexifilter module, I thought I'd mention how this can be used to create a mediawiki-style markup format— and it's completely customizable in that any features can be omitted, altered, or added.

I've been using http://drupal.org/project/liquid thus far.

Following the recent developments, I am making the switch to http://drupal.org/project/wikitools

Over the past few years, Drupal wiki capabilities have blossomed. I think- and correct me if you disagree- that they've reached such a point as to make a drupal-powered wiki.drupal.org a distinct possibility. Even now, we continue to get silly questions in the drupal.org forums: "can you make a wiki with Drupal?", etc. Let's prove to them that it can. As groups.drupal.org came to represent the power of Drupal with regard to community effort, wiki.drupal.org will come to represent the power of Drupal in information exchange.

This would be an ideal place for both developers and Drupal newbies to record what they know and to learn what they don't. Api.drupal.org and the Drupal handbooks partially achieve this: but a wiki site, with anonymous users given editing power, would make the documentation of Drupal explode from a partially-complete, somewhat-vague set of instructions to a complete, powerful, comprehensive set of documentation.

Drupal needs this, or something like this; at api.drupal.org, for instance, many of Drupal 6's key functions and hooks are yet not documented. Even more of them have vague documentations: "Implementation of hook_forms()" does not even begin to describe a function.

Let's prove to the world that Drupal can build effective wikis. Let's prove to the world what the Drupal community can do. And let's prove to the world that Drupal can do anything.

Hey there all,

I have been doing a bit of research about setting up wiki sites. The two big "central" modules for wikis are wikitools (by rotzi) and liquid wiki (by sorenp.) Neither module is being actively maintained (no commits since March.) I've spoken to Soren and he said he doesn't have time to maintain Liquid Wiki anymore and it would be better if someone in the community took it over. I never heard back from Julian but through the grapevine I heard that theoretically he had a project which would bring him back to work on wikitools, at least for a while, but probably not permanently (if at all) is my guess.

The new Digg menu is highly usable.

Take a look at http://digg.com/news/technology. Try to click on the down arrows to the right of each menu item on the top strip and you will see a menu folding down, with sub menus folding down as well. Also, all the contents of the menu are displayed in the second horizontal strip.

Improving the drupal core menu navigation to create a digg-like menu would be fantastic - it's very high usability.

What do you think would be the requirements for such a task?

Do you know of a drupal menu which is currently doing something similar?

Drupal's wiki features at this point are already pretty impressive, especially compared to what was available just a couple of years ago. My main personal interest, however, is not in building wiki functionality into a Drupal site, but rather in enabling cross-site integration between Drupal sites and Mediawiki sites.

One advantage to this sort of cross-site integration is that it could enable Drupal sites to leverage content from existing, already content-rich wikis such as Wikipedia.

I cobbled together a backlinks module which works with views, to provide a backlinks page for each node. It hasn't yet been used in production, but if anyone has a wiki sandbox I'd be curious to know if it's at all useful. You can download it from cvs; project page is http://drupal.org/project/backlinks

Not sure if I am missing ti someplace, but thought I would create one if it doesn't exist. Would be cool to see a page that was a wish list and a list or what is currently being worked on with regards to the wiki issues in drupal. Here is my list

I spent some time in Sunnyvale speaking with roetzi and toemaz about plans to improve the revisions system in core: namely, to add in features that don't make any sense that we're missing (like the ability to 'diff' revisions), and possibly to add in the ability to provide moderated revisions, etc.

Nice job, I just discovered that the toc works. Found it when I was lookin at wikiman's install instructions. Nice job.

Now you just gotta fix the "=" problem.

Cheers! Ricco

Yesterday I published the first version of my wiki installation profile. The installation offers the following features at the moment:

• Editing for anonymous users
• Moderator role which can revert / delete pages
• Revisions for pages
• Mediawiki input format + Image assist
• Categorization via free tagging vocabulary
• Views: All pages / All categories / All Images
• Recent changes

I will talk more about this and the future of Drupal wikis in general at my talk at OSCMS summit next week.

See you there.

Hey roetzi,

You asked me to post you and leave you a note about the wiki module not handling the first level of media wiki chapter syntax. It handles ==title==, and ===title===, etc... but does not handle =title=

Cheers!

PS -
* the ability to track the nick of the last person that edited the wiki page, via the view builder interface would ROCK
* table of content wouldn't suck

One feature of Wikipedia that I find attractive is the ability to restrict edits on a certain page to editors/administrators, particularly in the case of vandalism or high traffic. I was looking around at the best way to implement this feature in drupal, and found that a combination of workflows, na_arbitrator (integrated in Drupal 5 core), and workflows_access (not ready for Drupal 5 yet but seems to be on the short-term roadmap) will offer that functionality. Just posting for others' info just in case they were looking for this feature as well.

I just stumbled over rötiz Wikitools module and couldn't help noting that all features listed, except for "Node Search" and Freelinking integration are already supported by Liquid (*). I do in general welcome new approaches and I'm glad to see that more developers team up around the drupal wiki consept, but what is there a point in running two separate races for the same goal?

Best Regards,

Soren

(*) Node Search and Freelinking support has been implemented as a separate addon modules that will be distributed with the next version of Liquid

I really like the Wikipedia flagging feature where articles that need work can be flagged (such as {{needs citation}}). I've been thinking about the best way to implement this in Drupal with a wiki system. Some possibilities include:

1. Flag content - http://drupal.org/project/flag_content - Is limited and does not allow for users to specify the reason for flagging the node. Also does not put a note on the node itself (like Wikipedia does) when an node is flagged. The flag also does not show up in revision history.

Hi, Just discovered this group. Our organization is planning to apply as a Google SoC mentoring organization. A couple project ideas are to enhance our current Drupal based platform where Wiki is one key feature that we would like to see fully baked with Drupal. Wondering any students on this group? we perhaps can consolidate the requirements discussed here and use the SoC opportunity to advance the progress. Thoughts? (note: this effort is separate from Drupal SoC effort but of course the output will be contributed back to Drupal)

Cheers.

it seems no one mentioned BackLinks yet, it's not an essential wiki feature but for larger wiki's it's always good to know what pages link here. and AFAIK no drupal module implements that feature.

not sure how you'd go about implementing that though.

On the test wiki I set up recently I got some input in what is missing for a wiki in drupal. Some of the points I addressed with three custom modules.

In the meantime, these modules have matured into two official modules: recent changes and wikitools.

I know there was a session on Wikis last fall in Brussels. It seems like there has been a lot of movement. Does it make sense to do a session in California, and have a demo of a wiki in Drupal, and a Drupal wiki?

Ian

Goals

• To build a user friendly wiki on top of Drupal
• To have a central place to
  • Discuss best practices for implementing this wiki
  • To investigate and compare various modules
  • To document the progress so others can build their own wiki based on their needs and our findings

There is also a Discussion header at the bottom of this document.

Feature Requests

Feel free to add your own
1. Basic editing
2. Creating new pages
3. Linking to pages
4. TOC
5. Discussion (Talk)
6. User Friendliness
7. Classification & Hierarchies
8. History

Last week I released a module which uses PEARs Text Wiki packages for formatting. This lets you choose one from several different input formats, my favorite being the well known Mediawiki syntax (not because I like the syntax particularly, but because a lot of people know the syntax from Wikipedia).

As an experiment, I have created a new content type called 'wiki page' and given everyone the permission to edit them. This post is an example of one. Feel free to edit it, within reason. Your edits don't generate email notifications but might generate items in rss feeds depending on reader preferences.

How are things going? Is anybody actively developing a wiki module of some kind?
How can I help?
I would love to have a real wiki module which works like the rest of Drupal.

If no module developers are working actively towards a goal - should I compile a set of requirements?

What is missing? (Funding?)

best
Gunnar

a table of contents filter is available in the tweakbox module. useful for wikis and nodes in general.

that module might need some love.

I think TWiki is most advanced and sofisticated Wiki System around and should be looked deep into when planning to ad Wiki features into Drupal. It would be great if we would find a person who has deeper understanding of both systems and could adress potential benefits of this cross-polination ;-)

In an effort to contribute to various music/arts-centric solutions, I've been looking for ways to use wikis as a repository for basic info that often gets duplicated.

Couple instances:

Many music sites such as emusic, MP3.com, Yahoo Music, and Rhapsody are licensing content from services like All Music Guide. On the other hand, sites like Wikipedia and Wikia already, or could, provide much of the same info.

I'm going to try and outline some notes from the Wiki session at DrupalCon. I may have missed some big ones. This is a good example of where a wiki would be nice - to make this list. Is it safe to say it is not certain whether to use Drupal modules and glue to make a wiki, or whether to integrate a wiki into Drupal? Maybe it depends on the case?

Basic and necessary

Access control

I've written up a couple of wiki recipes in the past: http://wiki.bryght.com/wiki/drupalwikirecipe -- they were originally for 4.6, so they need updating, especially in the selection of a node access module that allows for editing by a certain role.

And, if anyone wants to use a wiki to document some items, feel free to use our public dev wiki at https://svn.bryght.com/dev for anything Drupal related.

What is it about a WIKI that we are all seeking?

Add your ideas below!

Existing projects:

• WIKI (Filter)
• Liquid Wiki Engine Project

Search:

• Search drupal.org
• Search groups.drupal.org

Russ