Wiki

Evaluation Drupal 6 wiki modules

starbow — Wed, 19 Nov 2008 20:57:23 +0000

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

Wiki

An actual wiki in Drupal

samrose — Tue, 07 Oct 2008 22:15:24 +0000

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.

If you feel the same as me, then what I am proposing here is a new way to make links specifically for wiki in Drupal. This way of making links would work with a wiki content-type (or content type of your choosing). Would work with Drupal's search system

I am thinking of something kind of like what is described here: http://drupal.org/node/156523 and in this patch http://drupal.org/files/issues/proper_links_0.patch but basically goes further into being more like the guts of actual wiki parsers (creating direct links to nodes that are run through regular expression filters, etc) basically, creating an actual parser, and one that can work with WYSIWYG editors (in my case FCKeditor).

I have someone asking me to make this already, so no matter what looks like it will come into existince. But, I thought I'd share this proposed (albeit somewhat vague at this point) direction for feedback from those interested.

Would it really be that bad to have an actual wiki parser for Drupal? Or, is it enough to simply have the patch that allows freelinking to point straight to nodes, given that the whole linking scheme works better in Drupal through Input Filters? What do you think?

Wiki

Wiki Templates (or mimicking Wikipedia functionality)

Gerard McGarry@drupal.org — Sat, 04 Oct 2008 22:11:42 +0000

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?

Wiki

Edit Link for Wiki Pages

leoklein@drupal.org — Sun, 27 Jul 2008 17:06:36 +0000

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.

Wiki

Do we need Mediawiki syntax when we have WYSIWYG editors?

Gerard McGarry@drupal.org — Mon, 16 Jun 2008 10:29:17 +0000

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!

What I want to know from others who've tried the same thing is - do we need a mediawiki parser when we're already providing visitors with a WYSIWYG interface? Personally, the only feature that I consider essential is the content autocreation/double-bracketted linking method that allows a new page link.

Anyone else care to share their thoughts on this one?

Wiki

Import from mediawiki XML?

Miraploy — Wed, 04 Jun 2008 17:58:03 +0000

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.

Wiki

Refactor Collaborative Editor

marvil07 — Sat, 29 Mar 2008 19:38:26 +0000

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.

In 2006's edition of Google Summer of code a student made collaborative_editor module, giving this facility. But I think it's not so good managing revisions.

During this Summer of Code, I want to make the simultaneous editing better, using the better tool I found in my research. The initial list of posibilities to handle the changes include: some VCS, COMET, AJAX(used in the module).

Why?

Drupal is growing up and it is being used to different kind of websites, but it's not widely used by wikis. So it is a potentially new group of users who can make grow up Drupal still more.

Simultaneous editing improve user interaction inside a web, which is a notably a usability feature, which is one of the planned improvements goals in Drupal 7.

Reactivate the life of the collaborative_editor module developed on GSOC 2006, that actually has no activity.

Wiki

Installing Pear Wiki Filter

addisonkirk — Fri, 21 Mar 2008 16:30:51 +0000

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?

Wiki

Mediawiki namespaces

rötzi@drupal.org — Tue, 11 Mar 2008 23:05:19 +0000

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.

In my implementation, namespaces are mostly mapped onto node types. The main namespace (or no namespace) is mapped to a node type 'wiki', the template namespace is mapped to a node type 'template' and the image namespace is mapped to the image module. The user namespace can be mapped to the user profile page and Talk namespaces are ignored since Drupal handles this via comments.

But Mediawiki defines a couple of other namespaces: "Help", "Project", "Mediawiki" and actually any number of user defined namespaces. This brought me to the realisation that a simple mapping onto node types is not good enough. There are various ideas to have a different kind of mappings which could also be dependent on the namespace:

A namespace is a whole node type (e.g. 'image', maybe 'template')
A namespace is a term of a category (e.g. a category with 'Main', 'Help', 'Project' and any number of user defined terms)
A namespace is a group (organic groups)
Maybe something else

This would be a quite flexible approach as you can define your namespaces and the granularity of the namespaces.

But I realised that when I use Mediawiki, I never use anything except the "Main" namespace. I never used "Help" or "Project" or defined my own namespace. So the question is:

Would you use namespaces? And what for?

I would say that categorisation is enough (that's why I never used a custom namespace with Mediawiki), but maybe someone has a good use case for namespaces. The use on mediawiki.org (http://www.mediawiki.org/wiki/Project:Namespaces) could probably be replaced by a simple categorisation as well, I don't think there are many pages with the same name in these namepsaces.

Wiki

Is Drupal Wiki ready for primetime?

Miraploy — Sun, 09 Mar 2008 03:48:55 +0000

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?

Wiki

Refactor revisions to use a version control system

catch — Fri, 07 Mar 2008 18:19:02 +0000

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.

This project would probably be implemented as a patch to core and/or cck module.

Modules which deal with revision related stuff already:
http://drupal.org/project/diff
http://drupal.org/project/revision_moderation

Difficulty:
Pretty hard.

Wiki

intigrating just part of wikimedia into drupal ?

Tenchi — Tue, 12 Feb 2008 10:59:09 +0000

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 ? auth would have to be shared between drupal and wiki, which has already been done. the hard part would be to have wiki generate forum posts in drupal when a page is created, or, and much preferred, have discussion forum created only when someone clicks the discussion link, and of course open the forum post if it already exsist, in an i-frame or something within the wiki page. (not the whole forum, just the forum post that is linked to that wiki page) buy simply allowing talk pages to go back to drupal, and allow searching from within drupal to encompass the wiki, would be best option because it would also allow to keep up with wikimedia, so these modification would be easy to change if a jump in wikimedia version changed the way things were searched for \ talk pages displayed. I may also be able to provide some financial support to anyone willing to do this.

Wiki

Namespaces, other wiki comparisons

mtndan — Mon, 14 Jan 2008 16:49:22 +0000

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!

Wiki

Creating a wiki format with flexifilter

cwgordon7@drupal.org — Mon, 14 Jan 2008 02:05:53 +0000

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.

1. Prepend with </nowiki>.
2. Append with <nowiki>
3. Do a chunk grab on </nowiki> and <nowiki>.
1. Add several pattern-based text replace components:
2. Replace ''' (three single dashes) with alternating <strong> and </strong>.
3. Replace '' (two single dashes) with alternating <em> and </em>.
4. Replace ==== (four equals signs) with alternating <h4> and </h4>
5. Replace === (three equals signs) with alternating <h3> and </h3>
6. Replace == (two equals signs) with alternating <h2> and </h2>
7. Create a chunk grabber on [[ and ]].
1. Add an IF component within the chunk grabber.
1. Add the condition "text contains" with the parameter |.
2. As subcomponents of this IF statement, prepend with <a href="/drupalwikipath/
3. String replace | with ">.
4. Append </a>.
2. Now, outside the if statement, create an IF NOT statement with the same condition.
1. String replace ~ with \~ (escape the character).
2. Append ~~.
3. Add an advanced append. Step 20 should be added to this component.
4. String replace ~~ with </a>.
5. Now, outside of the advanced append, prepend with <a href="/drupalwikipath/
6. String replace ~~ with ">
7. String replace \~ with ~.

Wiki

WYSIWYG, WikiTools, PearWiki Filter, and Markup

samrose — Wed, 09 Jan 2008 17:34:26 +0000

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

One question that I have is: how does PearWiki Filter deal with using wiki markup in WYSIWYG editors? What is the best WYSIWYG editor to use in conjunction with WikiTools module, adn PearWiki filter, to allow mixed use of both richtext and different wiki markup on the same page? This is a feature that is generally supported in wiki engines like MoinMoin, social text, OddMuse, and other common wiki engines (plus services like WikiSpaces). It seems that this could be possible in Drupal. Perhaps it will take a custom input filter. Your advice would be greatly appreciated here :)

Wiki

Are we ready for a wiki.drupal.org?

cwgordon7@drupal.org — Tue, 25 Dec 2007 02:11:13 +0000

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.

Wiki

Wiki module maintainership

add1sun — Mon, 12 Nov 2007 17:49:57 +0000

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.

I think that wiki functionality is something that a lot of people in the community are interested in and it behooves us to have a regularly maintained module/suite of modules that "gets it done." I'd like to proposed that we 1) decide on one wiki module to support and move forward with, 2) deprecate the other, 3) get at least two people who are willing to be co-maintainers and keep the module alive and healthy. The upgrade to 6 will be coming soon and having patches sit in the queue for 3 months waiting for an inactive maintainer to review and commit will be nasty. There are also a number of other related modules and we should check the health of those as well and work as a community to make sure they don't go by the wayside.

So basically this post is just to start of a discussion about the health of wiki modules and future maintenance to see what others think, determine the best course of action for the community and see who is interested in stepping forward.

I'm also posting a link to this to both modules' issue queues.

Wiki

Usable expandable menus on Core - Creating a mission group

levavie — Sun, 23 Sep 2007 07:33:47 +0000

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?

Which high quality and easily expandable module would you recommend to start with?

Who do you think would need to join for this endavor to be successfull?

If you are developers and would like to join, please put there a note.

Feel free to edit this page with answers.

Thanks in advance,

Amnon

Yes, looks totally awesome.
Yet, maybe a bit much, cause it is duplicating the menu experience. For me, it would be enough to have a normal Dropdown menu with first sublevel appearing, this being doubled in the second horizontal row.

Thomas (user eigentor)

Unfortunately this is a wikipage, so I can't comment on it, or unfortunately this is a wiki page, which can't be commented on -- depending on how you see it.

In answer to your search:

DHTML menu, my favourite, difficult to make horizontal
Nice menus, horizontal and vertical, javascript-less, impressive use of CSS
Active Menu, a windows file tree like menu tree with + and - boxes, part of JS tools, no horizontal AFAIK
Drupal Administration Menu, the menu for administrative purposes (sun)

Bevan/

The digg menu looks pretty much like your classic CSS/DHTML menu, with a click instead of a rollover being the trigger event to reveal the menu.

We've found a number menus like OpenCube's Infinite Menus and Quick Menus that are accessible and easily customizable, but that don't perform so well on a high-traffic Drupal site.

The perfect menu is, well, the Holy Grail of usability. The perfect menus is a combination of built-in features and PHP wrangling in template.php. I've gone ahead and turned it into a forum topic (http://drupal.org/node/178665) under theme development.Each menu should be its own sub-topic, so folks can critique and comment extensively on integrating it into Drupal.

modulist

The new Digg menu is highly usable.

Hmmm...

A hover highlights both the menu item and the arrow down at the same time, but clicking the menu item and clicking the arrow down result in different actions.
The menu item / arrow down and the submenu graphically have no connection.
Once deselected the arrow down (and menu item) stays highlighted.

I believe there is room for improvement.

gaele

rszrama's reply: I actually found the menu to be a little confusing. The fact that clicking on the same menu item in two different places results in different actions (browsing to the section vs. expanding the menu) is very confusing. Then having to click the down arrow again made it worse. Honestly, I think the most "usable" menus we'll find are the ones people are most "used" to... which are Windows style menus. You click on it once to expand, and any further expansions are denoted w/ the right pointing arrow and expand automatically when hovered. The menu titles themselves wouldn't be links. For an example, click on your Bookmarks menu item in Firefox.

Unfortunately, I'm not sure that this is the best way to browse a website. This may be good for sites using Drupal as a general application framework where browsers are actually users who have come to perform tasks... but for general browsing, I don't think it's the way to go.

Wiki

Integration with Mediawiki sites

Sheldon Rampton — Sat, 28 Jul 2007 17:18:44 +0000

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've been doing this for some time between two of my websites -- PRWatch.org, which is currently running Drupal 4.7 (soon to be 5.2), and SourceWatch.org, which is currently running Mediawiki 1.8.2. The advantages to Mediawiki are that it is the same software that runs Wikipedia, and is therefore already feature-rich, has its own developer community, can handle lots of traffic, and lots of people already know how to use the interface. I find Drupal an ideal platform for blogging, and adding customized features is much easier on Drupal than on Mediawiki, whether through installing available contrib modules or through writing my own. For the wiki end of things, however, I think it would be difficult to emulate everything Mediawiki can offer, including namespaces, templates, user watchlists, etc.

For integration thus far, I've got PRWatch.org and Sourcewatch.org sharing the same user list, so that people can log in to either site under the same username and password. I'm doing this right now using a hacked-up version of a Mediawiki extension called "EMU." In the future, however, I'd like to go further and create a more seamless single signon system. Right now user accounts are synchronized, but people still have to log in separately on each site. I'd like to see if something along the lines of Drupal's cosign or Site Pass modules can enable users to to log in once and then be able to jump back and forth between the two sites without needing to log in a second time.

For cross-linking from PRWatch.org to SourceWatch, I wrote the interwiki module (now in Drupal contribs), which provides an easy way of linking to articles on the wiki by simply putting two square brackets around a phrase. My main wiki is Sourcewatch, but I can also link to Wikipedia articles by putting "w:" in front of the phrase being linked, e.g., w:ice cream. More recently, I've found a combination of my interwiki module and Drupal's PEAR Wiki filter module to enable other features of Mediawiki syntax, such as equals signs for subheads, while still having double-bracketed phrases point to Sourcewatch articles rather than create new articles within PRWatch. This makes it easy to reference Sourcewatch articles when blogging from the Drupal site, and it's also easy to copy-and-paste text between the two sites. We're also starting to work now with other organizations to help them set up their own, similarly-configured Drupal-powered "Sourcewatch partner sites." The idea is that they can brand the Drupal site however they want and use all of Drupal's community-building tools, while collaborating with other Sourcewatch partners in using a shared wiki for collaborative research and referencing purposes.

I've also started experimenting with ways of transcluding content (either whole articles, or sections of articles) from Mediawiki into Drupal. For example, I've tried using thickbox so that links to Sourcewatch articles pop up INSIDE Drupal pages. I'm also interested in finding a way of using Mediawiki's user watchlists as a means of displaying targeted subsets of the full wiki inside other sites. This could be useful also as a way of selectively presenting desired content from Wikipedia within a Drupal site. Suppose, for example, that you want to create a Drupal site devoted to tennis, and within it you wanted to have a section that mirrors just Wikipedia's tennis-related related articles. To do so, you could create a Wikipedia user account, add the tennis articles to your watchlist, and then mirror just those articles on your Drupal site. (I think this feature could be especially powerful if used in combination with Drupal groups.)

Wiki

backlinks module

mfb — Mon, 25 Jun 2007 01:18:38 +0000

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

Wiki

wish list

Ricco — Thu, 05 Apr 2007 04:10:19 +0000

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 would love to see the view module be able to added the "person who made most recent change" to a wiki page. I might look into seeing if I can do it myself by using mySQL and perhaps adjusting my actual module, but it would be cool if it was a standard feature. I think my wiki pages would be more useful to me if I could see easily who most recently has edited them.
have the the DIFF pages display the actual changes. I think I saw an item someplace that it is
known that it is not working properly. But that seems like a really useful features

Wiki

Making revisions not suck in core, part 1

webchick — Tue, 27 Mar 2007 20:05:32 +0000

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.

IMO, opening the opportunity to improve the core revisions system starts with de-coupling it from node module. Right now, node.module consists of some 3,000 lines of code... adding more to add in additional useful features is just asking for trouble. Further, there are many, many sites out there just using the normal node functionality and no revisions at all. Why use an extra JOIN per node_load for those people?

So please review.. It needs some work still, but especially needs testing to make sure the break was clean and all old behaviour still works.

Wiki

nice! [[toc]] works, nobody told me :)

Ricco — Wed, 21 Mar 2007 02:39:45 +0000

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

Wiki

Wiki installation profile

rötzi@drupal.org — Sat, 17 Mar 2007 15:31:58 +0000

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.

Wiki

roetzi, you asked me to give you a note about the = issue

Ricco — Sat, 17 Mar 2007 03:15:11 +0000

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

Wiki

Wiki management with workflow

bburan@drupal.org — Fri, 09 Mar 2007 15:14:25 +0000

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.

Wiki

Wikitools and Liquid

sorenp@drupal.org — Tue, 27 Feb 2007 12:15:40 +0000

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

Wiki

Should comments on Wiki pages be enabled or disabled by default?

gusaus — Sat, 24 Feb 2007 22:58:52 +0000

Wiki

Ideas for flagging wiki articles

bburan@drupal.org — Sat, 24 Feb 2007 19:18:16 +0000

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:

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.
Replacement tags - http://drupal.org/project/reptag - Can be set up to parse {{needs citation:[user comment here]}} and replace it with a nicely formatted "box" at the top of the node. The flag shows up in the revision history as well. However, I don't see a way of auto-generating a list of nodes that are flagged so that interested users who are looking to contribute by cleaning up articles can browse a list of nodes that need work.
Implementing a CCK with checkmarks for the flags, as well as a text field for remarks. This doesn't seem quite as "clean" in my mind as it adds more options to the node creation page and edit page that seems unecessary. I like the idea of keeping the UI as clean and uncluttered as possible.

Does anyone have suggestions.

Wiki

Can this be a SoC project?

Jenny — Thu, 22 Feb 2007 21:53:51 +0000

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.

Wiki

what about backlinks

alaa — Mon, 19 Feb 2007 07:55:12 +0000

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.

Wiki

the next step

rötzi@drupal.org — Fri, 16 Feb 2007 08:05:35 +0000

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.

The first one helps you keeping track of the changes on your site by providing a Mediawiki like recent changes page as well as an rss feed. This module integrates nicely with the diff module by providing links to the diff-view as well as incorporating the diff in the rss feed.

The second one is an assortment of smaller things which don't really need an own module. The best way to see what it does is by taking a look at the features list on the project page or by looking at the demo. It integrates nicely with the freelinking filter so if you use freelinking alredy, just give it a try and if you don't like it you can disable the module and you will be back to normal.

The how to on my page now reflects the new modules.

And if you look again at the list of missing features you will see that there are no show-stoppers left.

Wiki

Wiki session at DrupalCon OSCMS 2007?

Development Seed@drupal.org — Sat, 10 Feb 2007 22:10:25 +0000

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

Wiki

Setting up Wiki Best Practices - Drupal 5

nikle — Tue, 30 Jan 2007 17:25:41 +0000

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
9. Diff (compare previous versions)

1 Basic Editing

How do we allow users to create new wiki pages?
What filters do we use?
- Markdown
What WYSIWG editors should be considered?
AutoSave would be a good to have
Dif & Revisions
Section editing like MediaWiki helps for large pages

2 Creating new pages

What modules are available (some mention to wiki404)
Namespace? Allowing for top level sections eg (Parent/Child) instead of (wiki/Child)
Templates? What about contempate

3 Linking to pages

What tools do we have to dynamically allow people to browse existing pages and link to them.
- There is a wonderful implementation of this on wetpaint.org where you click "Find Pages" and you are presented with a hierarchal list of all pages available.

4 TOC

Moshe points us to the TweakBox Module. The TweakBox Module has a patch to get it to work under 5.x. I was able to get it to work within PEAR wiki input type but you must set Tweakbox at a lower level of importance on the config tab:
Home » Administer » Site configuration » Input formats » [name of your imput format] -harrikat2

5 Discussion (Talk)

Built in comments? Talk page?

6 User Friendliness

What can we do to make the wiki as easy to use for end users.
Helptip to educate users

7 Classification & Hierarchies

What about taxonomies / categories
What about the Book Outline features, other forms of Hierarchies? (see Namespaces above)

8 History

Can the Revision system be made more friendly to allow all visitors to view and compare (see below) past versions of pages?

9 Diff

The current Diff module is pretty basic and does some strange things. We really need a more robust diff engine (like MediaWiki's DifferenceEngine.php) which allows for a nicely formatted easy to understand comparison of prior versions.

Discussion

How do we gain access to the diff module for this wiki page (or any for that matter?) so we can change what has changed since we last checked? Alternatively Moshe mentioned that changes might trigger RSS/Email updates pending on some setting but didn't go into specifics as to what settings? - nikle 2007-01-30 22:51

Hi, I'm currently leading a workgroup on WikiCreole, a common wiki markup language to be used across different Wikis. It's not replacing existing markup but instead enabling wiki users to transfer content seamlessly across wikis, and for novice users to contribute more easily. You might also be interested in looking at MediaWiki Ideal to get a feel for general wiki features. I would however advise not to make the system too complicated, following the KISS principle. A very basic wiki can be written in just 222 characters of Perl code, except I think one of the most essential features of a wiki is the RecentChanges list which from what I see here does not exist. :( Is there a plan to make a RecentChanges page for just wiki pages? Perhaps it might be interesting for all pages on the site as well, so a user can quickly see what's new on the site. I believe there is such a plugin for Drupal, but I can't use it for my Drupal site, because it does not support i18n, if I recall correctly.

-- amuzulo 2007-Jan-31

Wiki

PEAR Wiki filters

rötzi@drupal.org — Fri, 19 Jan 2007 06:28:23 +0000

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).

The advantage of this module is that it lets you choose among different Wiki formats, but the problem with this module is that the implementation of the parsers and renders depend on PEAR. The parsers don't get udpated very often, and thus you can't count that features which are not implemented yet will be available very soon...

A feature which I implemented today is integration of the filter with freelinking. This allows you to write Wikilinks and have the options of freelinking available for wiki links: searching for title or creating a new page with the wikilink title.

But until I figured out the Drupal release system the best way to obtain the current version with freelinking integration is CVS...

Wiki

Welcome, wiki pages

moshe weitzman — Thu, 04 Jan 2007 15:30:31 +0000

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.

One gotcha that is eventually fixable is that anyone can edit a wiki page, and not just a group subscriber. Thats not a big deal on g.d.o, since we almost all groups are open subscription anyway. A workaround is to make the post Private, and thus restrict viewing and editing to subscribers.

Ideas for improving the usability of the wiki pages

provide some UI that clearly indicates they are a wiki page such as the "This is a wiki page - you can edit it." with the "edit it" part linked to the edit function
** one idea is to override the theme_menu_local_task function and use a different CSS class for the local task tabs on wiki node types
Diff would of course be nice, but I hear that it's borken right now (?)
** Ideally, I'd like to see a 'side-by-side' diff, similar to that used in MediaWiki. I've looked at the DifferenceEngine.php file in MediaWiki, but it is way beyond my PHP coding level. (gmak)
It feels weird not having comments. I think comments could work similarly to the "talk" pages on wikis, especially if provided in a collapsible/collapsed fieldset
** is there an easy way to list comments as a local task link, as opposed to below the node? This would be very similar to the 'discussion' tab on mediawiki, for example.
would it make sense to allow a wiki to be anonymous? being that a wiki is collaborative by nature, the doc could evolve into something completely different than what the original author posted.
** Senpai sez: Yes, Wiki posts on g.d.o should be anon, so that the document can take on a life of its own. I feel weird editing this page, because it's gonna look like Moshe originally wrote this sentence. Let's make a wiki setup that d.o can eventually adopt, and start by making wiki pages a-nony-mouse. If it's absolutely required to know who wrote it, start with a "posted by:". Remove that info once the page is re-written my anyone else. Or, better yet, maintain ownership info for site admins, but theme the g.d.o site to remove that info for wiki content.
what else?

I'd love some suggestions for how to present wiki pages differently from other pages and also additional features like real wikis. We already have markdown input format, in case you never noticed that. I'd love a 5.0 version of tweakbox module which provides a Table of Contents filter.

*** There is a hacked version of the TOC module (from TweakBox) which I have managed to make work with Drupal 5. You can find it here. (gmak) ***

Also, folks might want to experiment with group specific categories (see the categories tab on group home page) in order to help visitors navigate your group and its wiki pages.

This is very cool! I wonder if this change shows up in the diff...

Apparently down here we can do whatever we want and it's outside of the diff. is that on purpose. m3avrck smells bad! (<-nobody knows that I wrote that!!!)

I don't see anything wrong with enabling comments... seems to make a lot of sense on the drupal handbook interface -geilhufe

I'm writing over some text to see if it shows up on a history page. Is there anyway to view the history overview presently?

This may be a stupid question, but how do you tell the difference between a wiki node and a story node, or does it matter?

How about getting something like mediawiki input format working - I tried but it requires a bunch of other php/wiki files and the directions are skimpy. -harriska2 (nevermind, motzi created a module for PEAR wiki which includes tikiwiki and mediawiki syntax along with a bunch of other types - works great) -harriska2

Maintenance

Plans - structure, roadmap?

Gunnar Langemark — Tue, 21 Nov 2006 09:48:48 +0000

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

Wiki

TOC module available

moshe weitzman — Thu, 09 Nov 2006 16:36:55 +0000

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

that module might need some love.

Wiki

anyone experienced in TWiki and Drupal?

zblace@drupal.org — Sun, 05 Nov 2006 15:22:01 +0000

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 ;-)

Wiki

Import/export wikipedia info

gusaus — Tue, 10 Oct 2006 23:55:14 +0000

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.

When setting up a venue, services such as Upcoming, Eventful, Zvents, require the same standard info (name, address, category, brief description, etc.) that also could be found in a wiki (Wikipedia: Music Venues).

Being a non-programmer, I have no idea how easy/difficult it would be to pull and present relevant data, from wikis, in a structured, standardized fashion. Seems like it would save a lot of time/money/effort for both the sites/services as well as the artists and venues themselves.

I'm wondering if there's any development and/or thinking along these lines. I'd like to contribute any way I can.

Wiki

Make a wiki with Drupal or put/integrate a wiki into Drupal?

Development Seed@drupal.org — Tue, 03 Oct 2006 14:29:13 +0000

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
This may be related to also the ability to have multiple wikis, but it is about who can edit the wiki. A possible approach is node access based on cck type, or a module that allows full node access awareness for cck nodes (right now it is just whether a role can create a certain type, but no viewing by role is handled).

Write in wiki format or in html
Ability to use tinyMCE or just the plain textarea, switch back and forth, etc. and tinyMCE should never gobble anything up. This was discussed at the DrupalCon presentation, but I do not have links to anything yet.

Category assignment
this can just be done using a textfield and free tagging, it's better than writing Category: blah blah on every page you make.

Revisioning and rollback
this is already done. Save as draft is helpful if you want to moderate your wiki.
http://drupal.org/node/48731

Diffing revisions
This is handled to an extent in http://cvs.drupal.org/viewcvs/drupal/contributions/modules/diff/ but Moshe explained it could work better, maybe work better with HTML.

Links back to a page
this may be done using the links module, but it's the idea of what links to a given story which is like the References section on the bottom here http://en.wikipedia.org/wiki/Drupal It would be nice to have this automated as opposed to having to manually assign node references.
http://cvs.drupal.org/viewcvs/drupal/contributions/modules/links/

CamelCase
Make a new page using new page or whatever - this is already done, but may just be buggy
http://cvs.drupal.org/viewcvs/drupal/contributions/modules/freelinking/

Advanced and would be nice

Making Table of Contents for a single page
this could also be special markup/filter and is a matter of some regex work. You can see an example of it here http://en.wikipedia.org/wiki/Drupal where it says "Contents"

Multiple wikis
So, you could have wiki_drupal-development/ which is a wiki about drupal development, and then you could have wiki_wordpress-development so you have two wikis, and so if you CamelCase within one of them, it will put your new page in the correct wiki.

Wiki

Wiki site recipes

Boris Mann — Tue, 03 Oct 2006 14:12:23 +0000

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.

Wiki

Wiki Development

rport — Mon, 02 Oct 2006 11:34:17 +0000

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

Add your ideas below!

Existing projects:

Search:

Russ

Wiki