Wiki

Moderation seems to be a large issue with any wiki system I have used. If there is any level of moderation, it is by users with special role that have some level of trust with the webmaster and are tasked with reviewing changes to the wiki. Sometime, it is just the wiki owner who is responsible for this task. Then there are wiki's like Wikipedia, which go unmoderated. User's are, for the most part, free to change anything they please (until they are banned) and then their contribution (or vandalism) is available for all to see until another competent user reverts it.

Wiki's are community driven websites, and it is for this reason that I think moderation should be a task for the community.

I was a bit disappointed with the fact that Freelinks didn't support embedding images, so I created a patch to make it do that. If you have the Image module installed and you freelink to an image node, you see the image preview on the page instead of the node title for the image. I submitted an issue (including the patch to implement it) here:

http://drupal.org/node/363406

Notes:
* This option must be explicitly turned on in the freelinks configuration page.
* You need the Image module for this to work, although not having it won't cause freelinks to break.

I have written up my experience evaluating the Drupal 6 modules for my attempt to create a mediawiki-like site.

http://starbowconsulting.com/node/111

Hey all,

I come from a wiki development background. have been involved in wiki communities and circles for a while now.

I have struggled with both Liquid and Wikitools in Drupal since Drupal 4.7, and have come to the conclusion that the problem is with Freelinking.

When I first used freelinking, I loved it. But, as I tried to customize and add functionality onto wiki in Drupal, Freelinking, and specifically the way that Freelinking makes links, has become a real bane to me in constructing wiki in Drupal.

There's a neat feature on Wikipedia pages where pages are related, they have a template at the bottom of the page with links to all of the relevant nodes.

For example, the Linkin Park entry will have a template at the bottom that has links to all their members pages, singles and albums, etc. This template is editable and when you make changes to it, it gets updated across all the pages that use it.

Seems like a great idea, and I'd love to implement something similar in a Drupal wiki. Does anyone know if it's possible using existing modules?

I'm building a community site for the Public Librarians and I was wondering how on Wiki Pages, the Edit link is added on Drupal Groups.

It's the link just under the Title that says, "You are viewing a wiki page. You are welcome..." Then depending on whether you're already a member of the Group, the link either goes to edit the page or join the group.

How nice.

Does anyone know how this was done? Is it something added to the theme template? I'm trying to figure out how it's done!

Any help would be appreciated.

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.

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 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 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?

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.

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 ?

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!

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.

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

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.

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.

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?

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.

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

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

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.

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

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.

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

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.

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