I've posted an existing document to a MediaWiki and broken it up into
sections (not pages). I want registered users to comment on each
section as follows:
* Users can add/edit/delete their own comments section
* Users (except admins) can't edit/delete other people's sections
* Users (except admins) can't edit the original document at all: it's protected
* Users' comments will be fairly long: multiple lines, not a single line
* At the bottom of the page, users can add general comments, not
specific to a given section
What's the best way to do this? Using the inputbox extension (thanks
for letting me know about this, Lonny!)? Or something else?
What I have now is ugly and doesn't do some of the things above:
http://wiki.lspace.org/index.php?title=Sandbox&oldid=10855
[pretend this page is protected and named APF-the-light-fantastic]
Bad things about this:
* Each "comment block" is a new page, which may confuse users-- they
want to add a comment and end up on a blank page. I realize I can
use "Preload" (or even inputbox) to pre-load a template when a new
page is created, but that still seems ugly.
* Once a "comment block" page is created, the search engine may return
it as a result, confusing users (they want to see the document with
annotations, not a single annotation). The comment block pages are
"subpages" of the original, but that's still not great
* Since the "comment block" is just a regular MediaWiki page, users
can edit/delete each other's comments (this part actually doesn't
bug me too much-- it's important that the original document be
uneditable, but it may be OK if users can edit/delete each other's
comments)
* Overall, I sense my approach is kludgey and incorrect. I'm sure
there's a more standardized/"correct" way of doing this.
--
We're just a Bunch Of Regular Guys, a collective group that's trying
to understand and assimilate technology. We feel that resistance to
new ideas and technology is unwise and ultimately futile.
Is there an easy way to change the names of the default namespaces
and have all the existing pages migrated over? Specifically, I'd like
to change "Talk" to "Comments" and "User_talk" to "Wall".
Thanks.
I installed the Cite extension by following instructions on Meta.
Afterwards, my wiki's text appeared very large, like I had zoomed in.
I disabled it. I had the same problem with the Makesysop extension.
Any ideas? I tried contacting Tim Starling directly, as Makesysop is
his, but no reply yet. Any help solving this problem is appreciated.
Thanks
--
Gary Kirk
I have a MediaWiki page listing all the rivers of the world [not
really] as local hyperlinks. Whenever someone creates a "river page"
by clicking on the link, I want the page automatically populated with
a "river template".
Can I do this?
I realize I could pre-populate all the river pages with the river
template, but, of the one million river links, I only expect about
100K of them to ever be created, and it seems like a waste of space to
create 1 million template pages when I'll only need 100K.
--
We're just a Bunch Of Regular Guys, a collective group that's trying
to understand and assimilate technology. We feel that resistance to
new ideas and technology is unwise and ultimately futile.
Hi,
I'm following the instructions at
http://meta.wikimedia.org/wiki/Help:Running_MediaWiki_on_Windows#Installing…
to install a wiki on my computer and seem to have made it through
everything except the very end.
When I try to access http://localhost/mediawiki/, I get the following error:
-----
Warning: main(./includes/WebStart.php): failed to open stream: No such
file or directory in C:\OTW\MediaWiki\index.php on line 4
Fatal error: main(): Failed opening required './includes/WebStart.php'
(include_path='.;C:\Program Files\TSW\Apache2\php\pear\pear\') in
C:\OTW\MediaWiki\index.php on line 4
-----
I've got TSW Control Center working under http://localhost:3000/, and
http://localhost/ shows a folder called MediaWiki. When I try to click
on the folder I get the same error as above, but the files appear to be
there.
I'm operating on Windows XP. I installed TSW (The Saint WAMP). On my C
drive, I set the directory OTW, under which I have the subdirectory
MediaWiki, with all 884 files, which seem to have the appropriate files.
All the Apache services appear to be working.
It seems like something simple, but I can't solve it. Can anyone help me
with this?
Best regards
Benjamin Barrett
a cyberbreath for language life
livinglanguages.wordpress.com
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
January 24, 2007
This is a bug-fix update that fixes some installation and upgrade issues
with the original 1.9.0 release.
* (bug 3000) Fall back to SCRIPT_NAME plus QUERY_STRING when REQUEST_URI
is not available, as on IIS with PHP-CGI
* Security fix for DjVu images. (Only affects servers where .djvu file
uploads are enabled and $wgDjvuToXML is set.)
* (bug 8638) Fix update from 1.4 and earlier
* (bug 8641) Fix order of updates to ipblocks table for updates from <=1.7
* (bug 8673) Minor fix for web service API content-type header
* Fix API revision list on PHP 5.2.1; bad reference assignment
* Fixed up the AjaxSearch
* Exclude settings files when generating documentation. That could
expose the database user and password to remote users.
* ar: fix the 'create a new page' on search page when no exact match found
* Correct tooltip accesskey hint for Opera on the Macintosh (uses
Shift-Esc-, not Ctrl-).
* (bug 8719) Firefox release notes lie! Fix tooltips for Firefox 2 on
x11; accesskeys default settings appear to be same as Windows.
Full release notes:
http://svn.wikimedia.org/svnroot/mediawiki/tags/REL1_9_1/phase3/RELEASE-NOT…
Download:
http://download.wikimedia.org/mediawiki/1.9/mediawiki-1.9.1.tar.gzhttp://download.wikimedia.org/mediawiki/1.9/mediawiki-1.9.1.patch
MD5 checksum:
89f77d8f39fbefa4325e0fe4d06746c7 mediawiki-1.9.1.tar.gz
e9e3785068f9edc6169c4215bc65eff0 mediawiki-1.9.1.patch
SHA-1 checksum:
11418c10ac59c044ece1cc0dd20a32c74b96ec86 mediawiki-1.9.1.tar.gz
6eaf11390c1aaea87ff48d798f7fe564a341f249 mediawiki-1.9.1.patch
PGP signatures:
http://download.wikimedia.org/mediawiki/1.9/mediawiki-1.9.1.tar.gz.sighttp://download.wikimedia.org/mediawiki/1.9/mediawiki-1.9.1.patch.sig
Before asking for help, try the FAQ:
http://www.mediawiki.org/wiki/Manual:FAQ
Low-traffic release announcements mailing list:
(Please subscribe to receive announcements of security updates.)
http://lists.wikimedia.org/mailman/listinfo/mediawiki-announce
Wiki admin help mailing list:
http://lists.wikimedia.org/mailman/listinfo/mediawiki-l
Bug report system:
http://bugzilla.wikimedia.org/
Play "stump the developers" live on IRC:
#mediawiki on irc.freenode.net
- -- brion vibber (brion @ pobox.com / brion @ wikimedia.org)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFFtyKJwRnhpk1wk44RAmIQAJsH/xB/lV+/gFHAbhEVWsXv1yoMLgCfWChB
r3LSI7FwfucNJ4qOliFJ8QA=
=rKzE
-----END PGP SIGNATURE-----
Is there some way, how to get usage over time data from MW server (MW 1.6.8
running on Linux machine).
What I would like to achieve are RRDTools graphs of number of page reads and
page edits over the time. If the data are in the database, it is not problem
for me to write down the scripts for RRDTool to get them out, but I don't
know where to search for them. Or is there any other way to create MW site
statistics? (I'm running some other webs on the same Apache server so the
general statistics for the web server are not good solution for me.)
Thanks in advance for any help
Jakub
But, how can i use the script maintenance/importTextFile?
> ----- Original Message -----
> From: "Rob Church" <robchur(a)gmail.com>
> To: "MediaWiki announcements and site admin list" <mediawiki-l(a)lists.wikimedia.org>
> Subject: Re: [Mediawiki-l] How to migrate a lot of text files?
> Date: Thu, 25 Jan 2007 21:17:24 +0000
>
>
> On 25/01/07, Ashar Voultoiz <hashar(a)altern.org> wrote:
> > You can use the script maintenance/edit.php . You can do something like:
>
> There's also maintenance/importTextFile.php, which could be used with
> a loop in a shell script to achieve the desired bulk-import.
>
>
> Rob Church
>
> _______________________________________________
> MediaWiki-l mailing list
> MediaWiki-l(a)lists.wikimedia.org
> http://lists.wikimedia.org/mailman/listinfo/mediawiki-l
>
=
Zepter Tablecloth Sets
Roma, Venezia, Siena and Nancy Tablecloth Sets are made of stain resistant Damask cloth, made in Europe.
http://a8-asy.a8ww.net/a8-ads/adftrclick?redirectid=118c79b15576e1bb275ae51…
--
Powered by Outblaze
How do I protect part of a page with MediaWiki?
I want to let users annotate a historical document line by line
without changing the historical document itself. Example:
Four score and seven years ago <- this would be protected (no edit, no delete)
a score is 20 years <- would be editable/deletable
our fathers brought forth upon this continent <- protected
[this section could be blank if no one had any annotations on that line]
a new nation, conceived in liberty <- protected
Protected lines/section could only be unprotected, deleted, or changed
by WikiSysop or equivalent. Ideally, protected sections would be in a
different font/color/style to differentiate the original document from
the annotations.
Can I do something like this directly? Using a plug-in? Indirectly?
--
We're just a Bunch Of Regular Guys, a collective group that's trying
to understand and assimilate technology. We feel that resistance to
new ideas and technology is unwise and ultimately futile.
Today I had an interesting experience: talking a fairly elderly
journalist (now mostly an occasional columnist) through creating a
Wikipedia account and creating an article.
Apart from en:wp's Byzantine policy considerations, it was an
interesting experience in finding out in real time just how horrible
the MediaWiki interface is in some ways. Trying to explain where to
find the thing that was on my screen and I *knew* was on his screen,
that sort of thing.
This is the sort of person it would be nice to create something for:
someone who knows a *lot*, can't work a computer and loves Wikipedia
as a reader.
A major part of excellence in technology design is to create something
that lets geeks go wild *and* is entirely usable by people who
basically can't work computers. MediaWiki is pretty good at this
already, I think - en:wp has quite a lot of contributors who can't
work computers but are excellent writers, researchers, editors and
even admins. But there's a long way to go.
Do we have any friendly organisations who can set up interface testing
labs with normal people in them? That relative whose computer you
really, really hate cleaning up for them.
Phil Sandifer posted about this to wikien-l today with regards to
en:wp's grossly newbie-hostile policy thicket:
http://en.wikipedia.org/wiki/User:Phil_Sandifer/Susan
The text is:
Susan is a hypothetical Wikipedian, selected because she behaves in a
manner basically consistent with most of our editors.
Susan is a 40-year-old stay-at-home mother. She majored in English
many years ago, and still has a fondness for Jane Austen. She is idly
browsing the Internet, and happens by Pride and Prejudice. In five
minutes, her son gets off the school bus. She finds an error on the
page.
Wikipedia policy and process should be designed so that Susan can make
this change and have it not get reverted.
In fact, there ought not be any small task on Wikipedia that cannot be
completed by Susan.
This requires some things.
1. There must not be any policies or processes that are
sufficiently complex that Susan would have to look them up before
doing anything. Everything should be both memorizable and of
sufficient simplicity that the remembered version will be trustworthy.
That is to say that Susan should be able to get by with the nutshell
versions of our policies.
2. There must not be a bunch of code or formatting for what she
wants to do. If Susan has to go "Wait, what's the template for this?"
then she will have to get up and go meet her son instead of fixing the
problem.
3. We must not require anything that Susan does not have fast
access to. No research projects, no scavenger hunts. Not even a Google
search or pulling a book off of a shelf. Susan should be able to
improve Wikipedia on her own.
4. There must be a culture of good faith so that Susan's
contribution (which will probably come in as an IP contribution) will
not instantly be met with suspicion. Remember - if Susan goes back the
next day and her change has been reverted without explanation, she is
unlikely to edit again.
Think carefully about these issues when designing something for
Wikipedia. Susan is intelligent, well-meaning, and a valuable
resource. She will improve Wikipedia if we let her. And there are
thousands of Susans out there. Susan, or someone with Susan's
circumstances, is our average and most common editor.
Design for Susan.
- d.