My initial thought is to configure separate wiki's for each, then
override the AuthPlugin mechanism to use a common user table.
Luis Zarrabeitia wrote:
I want to use mediawiki to publish my faculty's courses on the web. For what I
need, a full-blown CMS is not needed, and certain features of mediawiki are
quite desirable (for instance, the <math> and <gnuplot> extensions are
specially useful and I haven't seen them on any CMS)
However, as the courses are independent, I would like the pages to be
independent: if two equally named files are uploaded to different courses,
they should not overwrite each other, i.e, I could have
Also, editors of course1 shouldn't necesarily be able to edit course2.
The problem could be solved by installing different wikis, one for each course
(or a single wiki that used different databases/tables for diferent urls) but
that way sharing users between wikis (a teacher or a student with two
courses) or setting up an unified skin would be harder if not impossible.
What would be the best course of action in this situation?
MediaWiki-l mailing list