I think you might be able to do what you want using the new FlaggedRevs
extension, rather than having an extra tab you would be able to have an
'reviewed / approved' version of the page ('as is') that is the default
page that is seen, and then a 'new version' of the page that would
contain suggested revisions etc ('to be').
You can set permission based on logged in / unlogged in, membership of
editors / approvers / readers groups etc.
One advantage is that this is an extension and doesn't require 'hacking'
of any of the standard code
http://www.mediawiki.org/wiki/Extension:FlaggedRevs
Ta
John
I saw a wiki once with a [draft] tab between [article] and [discussion]
- yet, having browsed thousands of web pages and hundreds of wikis each
week, I can't remember where I saw it, oh so long ago (maybe even only
DAYS ago, oh my!). Does anyone know of an example Mediawiki
installation with an additional [draft] tab? Thanks!
----
Additional background, for those interested in such a thing, and why:
We want it all! Who doesn't? ;-)
We want to lock the [article] pages to be the authored / approved
resource of our "encyclopedia" reference, and keep it 100% accurate and
searchable as a research resource. We will update these via admin
rights when changes and new versions are vetted out and approved (union,
lawyers, and so on).
We still want to invite visitors to make recommendations, to do their
own rewrites, to dialog with each other, to share and evolve their edits
together, and so on, letting them tell us "we'd prefer it THIS way" as a
copy of any [article] page that they think can and should be made
better.
The [discussion] page can be used for this, but ... like Wikipedia, the
discussion pages kind of have their own flow, and I can see a reason to
clearly separate proposed edits from chat. So, if we use the current
[discussion] pages only for the edits and the chat, then it gets messy
and uninviting for people with different purposes to clearly know where
to read. We'd prefer: edits go here ([draft]), chats go here
([discussion]).
In our wiki installation, our own goal is to have such a [draft] page
start out as an exact copy of the main [article] page. Is there a
MySQL/PHPMyAdmin way to simply build a copy of the current version
[article] table(?) and call it a new [draft] table so that the [draft]
pages start out as 100% exact copies of the current [article] page? We
do not need the [article] history - only the current "front [article]
page".
We want to make it clear that the [article] page is the approved
reference (locked, only for admins to update) and that [draft] is the
playpen / sandbox where visitors are to put their edits, their requests
for how they think the next publication of the [article] should look.
Thanks for any pointers to a wiki with an additional [draft] page
implementation.
----
Hi,
I'm currently in the process of installing multiple wiki's on one server
using the same database (different prefixes). Is it possible to have all the
wiki's use the same user table so registering on one wiki will enable u to
log in on all of them ?
Regards,
Kenny
Welcome to mediawiki-l. This mailing list exists for discussion and questions
about the MediaWiki software[0]. Important MediaWiki-related announcements
(such as new versions) are also posted to this list.
Other resources.
If you only wish to receive announcements, you should subscribe to
mediawiki-announce[1] instead.
MediaWiki development discussion, and all Wikimedia technical questions, should
be directed to the wikitech-l[2] mailing list.
Several other MediaWiki-related lists exist:
- mediawiki-api[5] for API discussions,
- mediawiki-enterprise[6] for discussion of MediaWiki in the enterprise,
- mediawiki-cvs[7] for notification of commits to the Subversion repository,
- mediawiki-i18n[8] for discussion of MediaWiki internationalisation support,
- wikibugs-l[9] for notification of changes to the bug tracker.
List administrivia (unsubscribing, list archives).
To unsubscribe from this mailing list, visit [12]. Archives of previous postings
can be found at [3].
This list is also gatewayed to the Gmane NNTP server[4], which you can use to
read and post to the list.
Posting to the list.
Before posting to this list, please read the MediaWiki FAQ[10]. Many common
questions are answered here. You may also search the list archives to see if
your question has been asked before.
Please try to ask your question in a way that enables people to answer you.
Provide all relevant details, explain your problem clearly, etc. You may
wish to read [13], which explains how to ask questions well.
To post to the list, send mail to <mediawiki-l(a)lists.wikimedia.org>. This is a
public list, so you should not include confidential information in mails you
send.
When replying to an existing thread, use the "Reply" or "Followup" feature of
your mail client, so that clients that understand threading can sort your
message properly. When quoting other messages, please use the "inline" quoting
style[11], for clarity.
When creating a new thread, do not reply to an existing message and change the
subject. This will confuse peoples' mail readers, and will result in fewer
people reading your mail. Instead, compose a new message for your post.
Messages posted to the list have the "Reply-To" header set to the mailing list,
which means that by default, replies will go to the entire list. If you are
posting a reply which is only interesting to the original poster, and not the
list in general, you should change the reply to only go to that person. This
avoids cluttering the list with irrelevant traffic.
About this message.
This message is posted to the list once per week by <river(a)wikimedia.org>.
Please contact me if you have any questions or concerns about this mailing.
References.
[0] http://www.mediawiki.org/
[1] http://lists.wikimedia.org/mailman/listinfo/mediawiki-announce
[2] http://lists.wikimedia.org/mailman/listinfo/wikitech-l
[3] http://lists.wikimedia.org/pipermail/mediawiki-l/
[4] http://dir.gmane.org/gmane.org.wikimedia.mediawiki
[5] http://lists.wikimedia.org/mailman/listinfo/mediawiki-api
[6] http://lists.wikimedia.org/mailman/listinfo/mediawiki-enterprise
[7] http://lists.wikimedia.org/mailman/listinfo/mediawiki-cvs
[8] http://lists.wikimedia.org/mailman/listinfo/mediawiki-i18n
[9] http://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[10] http://www.mediawiki.org/wiki/FAQ
[11] http://en.wikipedia.org/wiki/Posting_style#Inline_replying
[12] http://lists.wikimedia.org/mailman/listinfo/mediawiki-l
[13] http://www.catb.org/~esr/faqs/smart-questions.html
Hi,
I have ongoing and heavy problems with my MediaWiki installation; it
causes a continous high CPU load of 100% on a Dual Core AMD opteron (2
GB of RAM).
If I'm monitoring what's going on with "mytop", I find queries like, e.g.:
-- snip --
/* WhatLinksHerePage::showIndirectLinks 66.249.65.201 */ SELECT /*!
STRAIGHT_JOIN */ page_id,page_namespace,page_title,page_is_redirect FROM
`pagelinks`,`page` WHERE (page_id=pl_from) AND pl_namespace = '0' AND
pl_title = 'Fungistatikum' ORDER BY pl_from LIMIT 51
-- or --
/* CategoryViewer::doCategoryQuery 217.227.171.13 */ SELECT
page_title,page_namespace,page_len,page_is_redirect,cl_sortkey FROM
`page`,`categorylinks` FORCE INDEX (cl_sortkey) WHERE (1 = 1) AND
(cl_from = page_id) AND cl_to = 'Chemie' ORDER BY cl_sortkey LIMIT 201
-- snip --
66.249.65.201 and the other stressing acces are coming from a Google
subnet, so I don't like the idea very much to block these hosts with
ipchains.
However, these threads/processes run for hours and continue to increase
the load, until the server becomes completey inaccessible (ssh doesn't
respond any more) or MySQL simply dies.
I've tried so far (a) to mimic the setup of the Wikimedia wikis with a
similar robots.txt, and (b) to enable file caching in MediaWiki; this
might have halped a bit, but didn't solve the basic problem (i've to
stop and restart mysqld every few hours).
Any help on this (or pointers to existing solutions) is greatly appreciated!
Greetings, asb
Hi,
now this is really weird. Adding new articles in my wiki is just going fine.
But when adding the article named "cohecho" (its the spanish word for
"bribery"), wiki ends up with an 500 Internal Error (after saving it). No
detailed error message is given. Adding other articles works like a charm.
ONLY with the word "cohecho" I have problems. There is absolutely no error
when adding the plural "cohechos", only the singular "cohecho" makes
trouble.
I can get access to the article over Special:Contributions. I can even edit,
delete it, view the history.
I can search for the article and wiki even shows it. But when clicking on
it, I get the 500 error.
After typing it in the search box, by clicking on GO, I get the 500 error.
By clicking on SAVE, I get the 500 error.
Any help available?
Thanks in advance!
Z.
I am running mediawiki on MySQL on a Windows server. I am writing a TAG extension which needs to pull data from a MS SQL data source. In the extension's PHP code, I have the line:
$sqlconnect=odbc_connect($dsn,$username,$password);
When running this PHP code outside of the Wiki (e.g., in the DOS prompt by typing PHP code.php), the connection works and I actually pull out data from the database. But inside the extension code, $sqlconnect ends up being null. Is there a setting that I am missing that allows me to connect to an external database? Is one not allowed to connect to a database in a TAG extension code? (I am new to extensions).
I also tried pulling the same data via web services. I tried the line:
$client = new SoapClient("http://www.mydomain.com/MyService.asmx?wsdl");
Again, I successfully was able to pull data out of the web services when I ran the code outside of the wiki at the DOS prompt. But once in the Wiki extension code, my Wiki pages go blank!
Again, is there a setting that I am missing that will allow me to connect to databases and web services in TAG extensions?
Thanks
George A. Kiraz
-------------------------------------------------
George A. Kiraz, M.St. (Oxon), M.Phil., Ph.D. (Cantab)
Gorgias Press
180 Centennial Ave., Suite A
Piscataway, NJ 08854 USA
Tel. (732) 885-8900
Fax (732) 885-8908
Can someone give me the code to put into common.css that will reduce the
fontsize used by the sidebar by 2 points? And/or the code to set it to
specific font size?