Drupal and wikis?

Sjuzet's picture

Hi all... have any of you used used Drupal with wikis, either by setting up part of a Drupal site to behave in a wiki-like way or by integrating Drupal with another software package such as MediaWiki? If so I'd be curious to hear about your experiences. I'm trying to create a Drupal wiki myself—for now I'm going off the "Wiki" Chapter in Using Drupal, but ultimately I'm going to need more fine-grained permissions control than that of the example in the chapter, so I'll have to experiment. I'll let you know how it goes!

Login to post comments

Drupalcamp Wisconsin had a

btopro's picture
btopro - Fri, 2009-06-05 23:06

Drupalcamp Wisconsin had a session today about setting up drupal as a wiki. Dono when the video of it will be posted but it should be online in the future.

"Plaguing the world with Drupal; One Plone, Moodle, Wordpress, Joomla user at a time since 2005." ~ btopro

http://elearning.psu.edu/
http://elearning.psu.edu/projects/
http://elearning.psu.edu/drupalineducation/


Thanks! I found the example

Sjuzet's picture
Sjuzet - Mon, 2009-06-08 14:28

Thanks! I found the example wiki site from that talk (http://johnthomson.org/druwiki/) -- I'll give it a look-over and keep an eye out for video. The fellow who made the site included info on the modules he used and how he set things up, but I'm curious to hear more, particularly about the philosophical design aspects he mentions.


Wiki Group

DavidWheelerPhD's picture
DavidWheelerPhD - Sat, 2009-06-06 01:29

You might want to browse/join the Drupal Wiki Group for answers.

http://groups.drupal.org/wiki


I took a look at that group

Sjuzet's picture
Sjuzet - Mon, 2009-06-08 14:53

I took a look at that group earlier but it didn't look like there's been any activity in the past several months and that made me uneasy. I'm still working to get a sense of how long information various Drupal solutions stays "fresh" despite upgrades and version changes... at this point I feel pretty clueless about that and it makes me hesitant to go off anything that isn't very recent. I hope that as I keep doing this I'll develop an awareness of what info is useful and what has become dated or irrelevant.

I gave the group another look and went ahead and joined... I'll hear if there's any new activity, and maybe I'll ask them a question or two of my own. Thanks!


What kind of access control?

linclark's picture
linclark - Sat, 2009-06-06 17:25

Hey Laura,

What kind of permissions are you looking for?

I haven't worked with any of the wiki modules, but I have set up fine grained access control using the combined powers of Content Access and Access Control List.

If you are looking to have different teams that each work on their own wiki's, you might want Organic Groups. Each group can have its own set of wikis.

Good luck!
-Lin


By role, I think...

Sjuzet's picture
Sjuzet - Mon, 2009-06-08 15:49

Hi Lin,

The course I'm making this website for has students work on a series of team-based projects that culminate in a big end-of-semester show that draws an international audience. I'm intending the website/wiki to be (1) the course's public face to the world, (2) a way to orient students and provide assignments, tutorials, etc, (3) a general knowledgebase resource, and (4) administrative aid for the TAs, staff, faculty, and outside contractors who make this beast run.

So I've got visitors (anonymous users), outside collaborators (mostly people running tech for the show), department faculty&staff, students who are in the course, TAs for the course, course instructors, and the site administrator/webmaster. I think I can handle permissions by role, but it needs to be page- and file-specific. I'm tentatively planning that all authenticated users (except perhaps the outside collaborators) will have permission to create and edit wiki pages, but for almost every role there will be some sections of the wiki that they can view but not edit, and others they should not even be able to view.

I used Taxonomy Access Control Lite for really basic access control on a team blog last semester... I'll have to take a look at Content Access and Access Control List now that I'm doing something more involved.

Thanks!


Drupal wikis are lacking...

eevn - Tue, 2009-06-09 02:30

I implemented an internal wiki for a company recently using Drupal. I found it very time consuming and ultimately was not very satisfied with the end result. I also based it on the "Wiki" Chapter in the O'Reilly Using Drupal book. I wanted to use WikiMedia-style markup for users to edit wiki pages, but found the PAIR module for it completely undocumented and not up to date with the latest version of MediaWiki. I had to go with Markdown markup instead. If I had to do it all over, I would just use MediaWiki, which I am completely familiar with from a user perspective since I've been using it for 4 years. Can you get a simple wiki up and working with Drupal? Yes. Does it come anywhere close to being as powerful or useful as an "out-of-the-box" MediaWiki install? IMHO, no.


how about Mediawiki with Drupal?

Sjuzet's picture
Sjuzet - Wed, 2009-06-17 15:53

Hm. More and more I'm thinking about using Drupal for the overall website and MediaWiki for the wikis, but I get scared wondering whether I can make them place nicely together. Also, I've never worked with MediaWiki before -- how difficult is it to get going with it?

I've done up a mindmap of my site structure -- I envision it as a Drupal site that contains three wikis: "Knowledgebase," "BVW Show Bible," and "Freespace" (these could be either Drupal- or MediaWiki-based). Each wiki has slightly different access restrictions, but they're each internally consistent with the same restrictions for every wiki page.

So maybe I could use Drupal to manage access (I'm looking at the MediaWiki auth bridge module) and then let MediaWiki do what it does best. I'm hoping if I dig around I'll find people who have used MediaWiki auth bridge so I can check out their results & determine if I like what I see. The biggest thing that turns me off is that I'm not sure I'd be able to keep a consistent look (or even a consistent main navigation) across Drupal and MediaWiki. I wouldn't want the overall website to appear disjointed, as though the wikis were completely separate sites. That might be enough to keep me on the Drupal-only path.


MediaWiki auth bridge works

eevn - Thu, 2009-06-18 00:41

MediaWiki auth bridge works by taking a Drupal user's login and copying it over to MediaWiki. It then writes the login to an HTTP Cookie, so that when you navigate to MediaWiki, it sees you as logged in. It supports multiple installs of MediaWiki, so no issues there.

MediaWiki is really simple to install and get running. It's fully skinnable, so in theory, you could get it to match the look of your Drupal site for the most part. Theming MediaWiki is pretty poorly documented though, from what I've seen. If you're willing to dig through a basic theme and figure out how it works, you could get the look and feel sim. to your site I'd think. MediaWiki's default theme (Monobook?), used on Wikipedia etc., is rather complex though, I wouldn't start with that one!


Drupal's authoring workflow

michaek's picture
michaek - Tue, 2009-06-09 04:57

Drupal's authoring workflow is pretty different from a conventional wiki authoring workflow, but the druwiki process seems like a pretty reasonable way to shoehorn a wiki into Drupal. However, I agree with eevn - if I were setting out to create a wiki, I would start with wiki software (most likely MediaWiki), not with Drupal.


PAIR?

eevn - Tue, 2009-06-09 07:37

Did I type "PAIR"? I meant PEAR used in conjunction with the PEAR Wiki Filter. Looking over the druwiki module list, it looks really close to what I used, so I'm thinking the O'Reilly Using Drupal chapter might have been based on that. michaek makes a good point. I went into it with MediaWiki in mind, wanting something similar, and ultimately wasn't satisfied, because Drupal wants to be Drupal.

Given your requirements: "all authenticated users (except perhaps the outside collaborators) will have permission to create and edit wiki pages, but for almost every role there will be some sections of the wiki that they can view but not edit, and others they should not even be able to view." There are some extensions to MediaWiki that allow access to pages by groups but the software was never designed for that purpose, and I don't think any of those extensions are extremely secure. Drupal might be the better option if you need access control at the per-individual-page or per-file level.


Absolutely - and a site that

michaek's picture
michaek - Tue, 2009-06-09 13:23

Absolutely - and a site that folks can add pages to and edit freely needn't be called a "wiki". Wikis are pretty structureless (without aggressive editorial oversight, that is) so it's hard for me to imagine "sections" of a wiki to which you could sensibly apply different permissions for each role. Maybe a different idiom makes more sense (such as Drupal's "book"...).


Yeah, you've got me thinking...

Sjuzet's picture
Sjuzet - Tue, 2009-06-09 20:33

Yeah, you've got me thinking... at the very least I should probably think of this as a few discrete wikis fit into the framework of an overall site, rather than one big wiki with some complicated permissions structure. I dismissed the book idea early on because of their automatic linking between sections -- it seemed way too hierarchical -- but I'll take a second look since it seems like there's more to them than I initially realized.


Looking at the book content type...

Sjuzet's picture
Sjuzet - Tue, 2009-07-21 15:11

Hey Michael, I'm coming around to this idea of using Drupal's book for this, but there's one big hangup that's giving me grief. I'd need to have 2 books with different access permissions -- one that is viewable to all site visitors and editable by all authenticated users, and one that can only be viewed and edited by a few select roles. I worry about whether the "book access" module (http://drupal.org/project/book_access) is in a good state to rely on, and I can't find a way to create a custom book content type (so I could get my access control via "content access") short of really hacky-looking stuff like this -- http://drupal.org/node/102446. If I could somehow automatically tag every page in a book with a taxonomy term, that's another possible workaround...

Am I overlooking some cleaner way to achieve the result I want? I'm surprised that this should be so difficult.


Book Access

DavidWheelerPhD's picture
DavidWheelerPhD - Tue, 2009-07-21 19:02

In addition to Book Access (http://drupal.org/project/book_access) you should check Book Page Access (http://drupal.org/project/book_page_access) for access control at the page level.

I have not tried either module; but, Book Access is being used by 410 sites with the number steadily climbing suggesting it is working OK. (http://drupal.org/project/usage)


Reporting back -- I tried

Sjuzet's picture
Sjuzet - Thu, 2009-07-23 17:15

edit
I think I found a workaround... I can use Book Access, and replicate Content Access using a combination of Taxonomy Defaults, TAC (or TAC-lite), and maybe Taxonomy Hide. Here's hoping it works!
/edit

Reporting back -- I tried the Book Access module and unfortunately it doesn't work at all if I have Content Access enabled. It works great as long as Content Access is disabled, but I need Content Access for other parts of the site.

So, I can either use Content Access and figure out some workaround to control access to my books, or use Book Access and figure out some workaround to control access to other content types.

I really don't want to have to create taxonomies that are redundant and useless except as a means of access control, but it's a temptation.


Post an issue in Book Access

DavidWheelerPhD's picture
DavidWheelerPhD - Thu, 2009-07-23 19:28

I am sure others would want Book Access to work with Content Access.
http://drupal.org/project/issues/book_access


Thanks a lot for the comparison

Sjuzet's picture
Sjuzet - Tue, 2009-06-09 20:18

Thanks a lot for the comparison info between the druwiki set-up and MediaWiki. It's helpful to know, even if it's not what I'd hoped -- I'll gauge my expectations appropriately. I think you and Michael H are right... what I'm looking for has some wiki-like properties but also incorporates more structured elements that need secure access control, so (even if MediaWiki is the better wiki) maybe Drupal is right for what I need overall.

I just hope I can make the more wiki-ish interactions with the site (free-form page creation, linking, and editing) painless enough that the community of people involved with this course will use the knowledgebase and keep it alive!


More links

linclark's picture
linclark - Wed, 2009-06-10 02:08

on the subject, funnymonkey just tweeted:

Can anyone say "I want a wiki-like functionality in #drupal ?" Get http://is.gd/Wc6y and http://is.gd/Wcdi to get most of the way there.

The modules behind those shortened urls are:
http://drupal.org/project/revision_fu
http://drupal.org/project/diff