Hello
New to the list.
My question is regarding installation of MediaWiki on Mandriva Linux 9.2
When running the config / setup script I reach the follow message and stop:
"PHP's XML module is missing; the wiki requires functions in this module
and won't work in this configuration. If you're running Mandrake,
install the php-xml package."
I do not have administrative access to the box. I had the admin install
the php-xml package however it didn't change the outcome.
I'm looking for any additional help other can provide me.
Thanks in advance.
-ch
When a user asks for a password reminder, I want to include a nice,
all-inclusive link in the generated email.
I've had good success, except for one quirk in our particular wiki
conventions: all user names are pre-defined as "Firstname Lastname"
-- including the space between the two --, rather than dealing with
the username/realname dichotomy.
So I have the following (in part) in MediaWiki:Passwordremindertext:
You should log in and change your password now, by going to:
{{SERVER}}{{localurl:Special:Userlogin|wpName=$2&wpPassword=
$3&returnto=Special:Preferences}}
But unfortunately, this shows up in email with the space intact
between "Firstname" and "Lastname":
http://www.somesite.org/wiki?title=Special:Userlogin&wpName=Jan
Steinman&wpPassword=qHU5wGG&returnto=Special:Preferences
which is no longer a valid, clickable URL, which sort of defeats the
purpose!
Before you say "RTFM", I've been all over http://meta.wikimedia.org/
wiki/Help:Variable . If there is a better place to get that info, let
me know.
That page says to put "/" between the page name and the query string,
but that results in the following mess:
http://www.ecoreality.org/wiki/Special:Userlogin/%3FwpName%3D%
242%26wpPassword%3D%243%26returnto%3DSpecial:Preferences
which doesn't seem to perform properly when clicked.
Any thoughts?
Oh yea, I think I've discovered a bug: I have account creation turned
off (MW 1.5.2), but in the previous example, you end up with the
account creation fields! (I haven't actually tried to see if it would
actually let an account be created this way.)
:::: Given an infinite source of energy, population growth still
produces an inescapable problem. The problem of the acquisition of
energy is replaced by the problem of its dissipation. -- Garrett Hardin
:::: Jan Steinman <http://www.Bytesmiths.com/Van>
Thanks for taking time to look into my backup problem.
But I still have serious problem with backup and
restore.
My wiki is customized with modification of the
Special:Allmessages and two new namespaces.
I did the backup and restore as described earlier and
I copied the LocalSettings.php over. But most of my
defined templates have no content in it after the
resrore. Some articles have no content either.
Any suggestions
jc
judi chen wrote:
> 5. Install MediaWiki as usual, but change the
> database's name from the default 'wikidb' to
> 'chpwikidb' MediaWiki will detect there is a
> pre-existing database and try to upgrade it when
> necessary.
>
> Also, the language setting MUST be the same as the
> original one!!
>
>
> But Finally, the new mediawiki I restored on server
B
> does not have all the info of the mediawiki on
Server
> A
>
> Would you pls kindly let me know what I did wrong.
First, you didn't say what was wrong. "does not have
all the info"
doesn't tell us anything specific.
Second, you didn't say if you have any customizations
or custom
configurations. These may very likely make a
difference.
Copy your old LocalSettings.php and fix up the paths
to be correct.
Check for differences between the prior and the new
one.
-- brion vibber (brion @ pobox.com)
__________________________________
Yahoo! FareChase: Search multiple travel sites in one click.
http://farechase.yahoo.com
The error that is being received states "move_uploaded_file(): SAFE MODE Restriction in effect"; the user your website scripts are running as doesn’t have permission to move the file.
If you can't disable safe mode then you need to look at the user settings for php and for your webserver.
-Arthur
-----Original Message-----
From: mediawiki-l-bounces(a)Wikimedia.org [mailto:mediawiki-l-bounces@Wikimedia.org] On Behalf Of Hans Voss
Sent: 23 November 2005 15:23
To: MediaWiki announcements and site admin list
Subject: Re: [Mediawiki-l] Warning: move_uploaded_file(): SAFE MODERestrictionin effect.
Hmm, to me that's not very likely:
From the LocalSettings.php:
## If you want to use image uploads under safe mode,
## create the directories images/archive, images/thumb and
## images/temp, and make them all writable.
But that's just my € 0.02. I haven't tested this and I could be wrong.
(And my wiki currently runs on windows so it's not checkable how this
works on Unix).
On 11/23/05, Arthur Guy <Arthur(a)assys.net> wrote:
> The answer is in the subject, safe mode restriction in effect; you need to disable safe mode in the php.ini file.
>
> -Arthur
> -----Original Message-----
> From: mediawiki-l-bounces(a)Wikimedia.org [mailto:mediawiki-l-bounces@Wikimedia.org] On Behalf Of Hans Voss
> Sent: 23 November 2005 14:38
> To: MediaWiki announcements and site admin list
> Subject: Re: [Mediawiki-l] Warning: move_uploaded_file(): SAFE MODERestriction in effect.
>
> Courtesy translation between the original mail.
>
> Martin, are you sure that the intermediate directories are also at
> least mode 711 or 755? (If directory B is a subdir of A and B has mode
> 777 but A has 700 then nobody can use directory B).
>
> On 11/23/05, Martin Baumann <mailsgetlost(a)web.de> wrote:
> >
> > Hallo,
> >
> > ich habe eine neue Wiki auf im Rechenzentrum der Uni installiert. Soweit hat alles geklappt. Nun möchte ich Bilder und Dateien hochladen. Dabei kommt folgender Fehler:
> I have installed a new Wiki in the serverroom of the University. So
> far everything is OK. Now I want to upload images and files. Then I
> get the following error:
> >
> >
> > Warning: move_uploaded_file(): SAFE MODE Restriction in effect. The script running as uid 600 is not allowed to write to directory /[...]/.public_html/wiki/images/temp owned by uid 38106 in /[...]/.public_html/wiki/includes/SpecialUpload.php on line 370
>
> >
> > Warning: move_uploaded_file(/[...]/.public_html/wiki/images/temp/20051123141254!Texturing.png): failed to open stream: No such file or directory in /[...]/.public_html/wiki/includes/SpecialUpload.php on line 370
> >
> > Warning: move_uploaded_file(): Unable to move '/tmp/phprQj3sa' to '/[...]/.public_html/wiki/images/temp/20051123141254!Texturing.png' in /[...]/.public_html/wiki/includes/SpecialUpload.php on line 37
> >
> >
> > Ich habe das Verzeichnis 'images' mit Recht 777 versehen. Die Unterverzeichnisse 'archive', 'temp', 'thumb' habe ich von Hand erstellt und auch mit 777-Rechten versehen.
> I have changed the 'images' directory to mode 777 and the
> subdirectories 'archive' 'temp' 'thumb' as well.
> >
> > Trotzdem kommt der Fehler ...
> Despite that I get the error.
> >
> >
> > Hat jemand eine Idee?
> Does anybody have any idea.
> >
> > Vielen Dank,
> Thank you.
> >
> >
> > Martin
> > __________________________________________________________________________
> > Erweitern Sie FreeMail zu einem noch leistungsstarkeren E-Mail-Postfach!
> > Mehr Infos unter http://freemail.web.de/home/landingpad/?mc=021131
> >
> > _______________________________________________
> > MediaWiki-l mailing list
> > MediaWiki-l(a)Wikimedia.org
> > http://mail.wikipedia.org/mailman/listinfo/mediawiki-l
> >
>
>
> --
> ----
> Met vriendelijke groeten / With kind regards
> Hans Voss
> ---------------------------------------
> skype: hans.voss
> google talk enabled
> I am looking for people to invite to Gmail. I have 100 invitations left.
> _______________________________________________
> MediaWiki-l mailing list
> MediaWiki-l(a)Wikimedia.org
> http://mail.wikipedia.org/mailman/listinfo/mediawiki-l
> _______________________________________________
> MediaWiki-l mailing list
> MediaWiki-l(a)Wikimedia.org
> http://mail.wikipedia.org/mailman/listinfo/mediawiki-l
>
--
----
Met vriendelijke groeten / With kind regards
Hans Voss
---------------------------------------
skype: hans.voss
google talk enabled
I am looking for people to invite to Gmail. I have 100 invitations left.
The answer is in the subject, safe mode restriction in effect; you need to disable safe mode in the php.ini file.
-Arthur
-----Original Message-----
From: mediawiki-l-bounces(a)Wikimedia.org [mailto:mediawiki-l-bounces@Wikimedia.org] On Behalf Of Hans Voss
Sent: 23 November 2005 14:38
To: MediaWiki announcements and site admin list
Subject: Re: [Mediawiki-l] Warning: move_uploaded_file(): SAFE MODERestriction in effect.
Courtesy translation between the original mail.
Martin, are you sure that the intermediate directories are also at
least mode 711 or 755? (If directory B is a subdir of A and B has mode
777 but A has 700 then nobody can use directory B).
On 11/23/05, Martin Baumann <mailsgetlost(a)web.de> wrote:
>
> Hallo,
>
> ich habe eine neue Wiki auf im Rechenzentrum der Uni installiert. Soweit hat alles geklappt. Nun möchte ich Bilder und Dateien hochladen. Dabei kommt folgender Fehler:
I have installed a new Wiki in the serverroom of the University. So
far everything is OK. Now I want to upload images and files. Then I
get the following error:
>
>
> Warning: move_uploaded_file(): SAFE MODE Restriction in effect. The script running as uid 600 is not allowed to write to directory /[...]/.public_html/wiki/images/temp owned by uid 38106 in /[...]/.public_html/wiki/includes/SpecialUpload.php on line 370
>
> Warning: move_uploaded_file(/[...]/.public_html/wiki/images/temp/20051123141254!Texturing.png): failed to open stream: No such file or directory in /[...]/.public_html/wiki/includes/SpecialUpload.php on line 370
>
> Warning: move_uploaded_file(): Unable to move '/tmp/phprQj3sa' to '/[...]/.public_html/wiki/images/temp/20051123141254!Texturing.png' in /[...]/.public_html/wiki/includes/SpecialUpload.php on line 37
>
>
> Ich habe das Verzeichnis 'images' mit Recht 777 versehen. Die Unterverzeichnisse 'archive', 'temp', 'thumb' habe ich von Hand erstellt und auch mit 777-Rechten versehen.
I have changed the 'images' directory to mode 777 and the
subdirectories 'archive' 'temp' 'thumb' as well.
>
> Trotzdem kommt der Fehler ...
Despite that I get the error.
>
>
> Hat jemand eine Idee?
Does anybody have any idea.
>
> Vielen Dank,
Thank you.
>
>
> Martin
> __________________________________________________________________________
> Erweitern Sie FreeMail zu einem noch leistungsstarkeren E-Mail-Postfach!
> Mehr Infos unter http://freemail.web.de/home/landingpad/?mc=021131
>
> _______________________________________________
> MediaWiki-l mailing list
> MediaWiki-l(a)Wikimedia.org
> http://mail.wikipedia.org/mailman/listinfo/mediawiki-l
>
--
----
Met vriendelijke groeten / With kind regards
Hans Voss
---------------------------------------
skype: hans.voss
google talk enabled
I am looking for people to invite to Gmail. I have 100 invitations left.
_______________________________________________
MediaWiki-l mailing list
MediaWiki-l(a)Wikimedia.org
http://mail.wikipedia.org/mailman/listinfo/mediawiki-l
Hallo,
ich habe eine neue Wiki auf im Rechenzentrum der Uni installiert. Soweit hat alles geklappt. Nun möchte ich Bilder und Dateien hochladen. Dabei kommt folgender Fehler:
Warning: move_uploaded_file(): SAFE MODE Restriction in effect. The script running as uid 600 is not allowed to write to directory /[...]/.public_html/wiki/images/temp owned by uid 38106 in /[...]/.public_html/wiki/includes/SpecialUpload.php on line 370
Warning: move_uploaded_file(/[...]/.public_html/wiki/images/temp/20051123141254!Texturing.png): failed to open stream: No such file or directory in /[...]/.public_html/wiki/includes/SpecialUpload.php on line 370
Warning: move_uploaded_file(): Unable to move '/tmp/phprQj3sa' to '/[...]/.public_html/wiki/images/temp/20051123141254!Texturing.png' in /[...]/.public_html/wiki/includes/SpecialUpload.php on line 37
Ich habe das Verzeichnis 'images' mit Recht 777 versehen. Die Unterverzeichnisse 'archive', 'temp', 'thumb' habe ich von Hand erstellt und auch mit 777-Rechten versehen.
Trotzdem kommt der Fehler ...
Hat jemand eine Idee?
Vielen Dank,
Martin
__________________________________________________________________________
Erweitern Sie FreeMail zu einem noch leistungsstarkeren E-Mail-Postfach!
Mehr Infos unter http://freemail.web.de/home/landingpad/?mc=021131
It shouldn't be too hard, I'm working on a similar hack myself (mine is slightly more complicated, as I want to give some groups read permission, some read-write, and each page can have more than 0-n groups in each. In other words, Unix style rw permission on pages). All you really need is a page to add people to groups (by adding them to the user_groups table), and you need to mark down the group of the editor in the table when you first create the page- either a new field in the table or in the page_restrictions field. Then change the Title::userCanEdit function to check if $wgUser is in the same group. If not, return false otherwise process as normal. I think that ought to be sufficient to do it.
Gabe
-----Original Message-----
From: mediawiki-l-bounces(a)Wikimedia.org [mailto:mediawiki-l-bounces@Wikimedia.org] On Behalf Of Rob Church
Sent: Friday, November 11, 2005 11:35 AM
To: Matthias Hirsch-Hoffmann; MediaWiki announcements and site admin list
Subject: Re: [Mediawiki-l] Page access restiction
The simple answer is no, not with the current software, and to be honest, it's almost guaranteed it will never support what you describe. You can either hack the software yourself, or you can search for an extension to do what you ask.
http://meta.wikimedia.org/wiki/Category:MediaWiki_extensions might be a good starting point; remember also Google is your friend.
Rob Church
On 11/11/05, Matthias Hirsch-Hoffmann <mhh(a)ethz.ch> wrote:
> Hi all wikianers
>
> My Newbie-Question on a Wiki 1.5 System:
> I have two groups, G1 and G2 with users.
> I want to set the permission as follow:
> All users can read all pages, created by users of G1 and G2.
> Only users of G1 can edit pages created by users of G1 and only users
> of G2 can edit pages created by users of G2.
>
> Is there a way?
>
> Thanks for your help.
> Regards
> Matthias Hirsch-Hoffmann
> ETH Zurich (Switzerland)
> mhh at ethz dot ch
>
>
>
>
>
> _______________________________________________
> MediaWiki-l mailing list
> MediaWiki-l(a)Wikimedia.org
> http://mail.wikipedia.org/mailman/listinfo/mediawiki-l
>
_______________________________________________
MediaWiki-l mailing list
MediaWiki-l(a)Wikimedia.org
http://mail.wikipedia.org/mailman/listinfo/mediawiki-l
Hi, folks. Just a quick note to let you know that there's an extension
for MediaWiki available that allows customized RDF output and in-page
user input of Turtle RDF. Code is here:
http://wikitravel.org/~evan/mw-rdf-0.3.tar.gz
This is in production on Wikitravel, only works for MediaWiki 1.4.x (at
least for the history model, probably some other stuff is broken with
the new database schema, too). More info here:
http://wikitravel.org/en/Wikitravel:RDFhttp://meta.wikimedia.org/wiki/RDF
README file is attached for below for people who don't follow URLs so
much. I'll add it to extensions section of mediawiki CVS RSN, but I've
been using darcs for version control so far and I CBA to merge to CVS
yet.
~Evan
________________________________________________________________________
MediaWiki RDF extension
version 0.3
16 November 2005
This is the README file for the RDF extension for MediaWiki
software. The extension is only useful if you've got a MediaWiki
installation; it can only be installed by the administrator of the site.
The extension adds RDF (= Resource Definition Framework) support to
MediaWiki. It will show RDF data about a page with a new special page,
Special:Rdf. It allows users to add custom RDF statements to a page
between <rdf> ... </rdf> tags. Administrators and programmers can add
new automated RDF models, too.
This is the first version of the extension and it's almost sure to
have bugs. See the BUGS section below for info on how to report
problems.
== License ==
Copyright 2005 Evan Prodromou <evan(a)wikitravel.org>
This program is free software; you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation; either version 2 of the License, or
(at your option) any later version.
This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
You should have received a copy of the GNU General Public License
along with this program; if not, write to the Free Software
Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307
USA
== Installation ==
You have to have MediaWiki 1.4.x installed for this software to work.
Sorry, but that's the version I've got installed, so it's the one this
software works with.
You also have to install RAP, the RDF API for PHP
(www.wiwiss.fu-berlin.de/suhl/bizer/rdfapi/) . I used version 0.92,
plus some custom hacks to make the N3 parser less fragile. You have to
apply a patch to the distribution if you want RDF to work; it's
included in this distribution. (Future versions of RAP will have these
enhancements).
You can copy the file MwRdf.php to the extensions directory of your
MediaWiki installation. Then add these lines to your LocalSettings.php:
define("RDFAPI_INCLUDE_DIR", "/full/path/to/rdfapi-php/api/");
require_once("extensions/MwRdf.php");
== 60-second intro to RDF ==
RDF is a framework for making statements about resources. Statements
are in the form:
subject predicate object
Here, "subject" is a "resource" such as a person, place, idea, Web
page, picture, concept, or whatever. "Predicates" are names of
properties of a resource, like its color, shape, texture, size,
history, or relationships to other "resources". The object is the
value of the property. So "car color red" would be a statement about a
car; "Evan hasBrother Nate" would be a statement about a person.
Of course, it's important to be definite about which resources and
which properties we're discussing. In the Web world, each "resource"
is identified with a URI (usually an URL).
For electronic resources, this is usually pretty easy; the main page
of English-language Wikipedia, for example, has the URI
"http://en.wikipedia.org/wiki/Main_Page". However, for analog subjects
like people or ideas or physical objects, this can be a little
trickier.
There's no general solution, but the typical workaround is to use real
or made-up URIs to "stand in" for offline entities. For example, you
could use the URI for my Wikitravel user page,
"http://wikitravel.org/en/User:Evan", as the URI for me. Or you could
use my email address in URI form, like "mailto:evan@wikitravel.org".
People who need to agree on statements often create 'vocabularies' or
'schemas' that map concepts, object, and relationships to URIs. By
popularizing such a mapping, we can all agree about what a particular
URI "means".
For example, the Dublin Core Metadata Initiative (DCMI)
(http://www.dublincore.org/) has a schema for very simple metadata,
such as you'd find on a library card. They've defined (among other
things), that the idea of authoring or creating something is
represented by the URL http://purl.org/dc/elements/1.1/creator. So
you could say:
http://www.fsf.orghttp://purl.org/dc/elements/1.1/creator
mailto:rms@gnu.org
... means that the creator of the Free Software Foundation is Richard
Stallman.
There are a lot of RDF models out there; you can also create your own
if you want.
RDF statements can be encoded in a number of different ways. By far
the most popular is as XML, sometimes called "RDF/XML". "Turtle" is
another format, which uses plain text rather than XML; and "Ntriples"
is still another.
== Models ==
For any given resource you can describe it from many different
perspectives. For example, you can describe a man in terms of his
academic career, his job experience, his family members, his body
parts' size and weight, his location in space, his membership in
organizations, his hobbies and interests, etc.
In this extension, we use the term "model" to describe a perspective
on a resource. For example, listing the links to and from a page is
one model; its edit history is another model. You can choose which
models you want to know about when querying the system for RDF
statements about a subject, and only statements in that model are
returned.
This is mostly a concession to performance; it doesn't make sense to
calculate information about the history of a page if calling program
isn't going to use it.
There are a number of models built into this extension; you can also
add your own, if you know how to code PHP. The models have short
little codenames for easy access, listed below.
Models built in:
* dcmes: Dublin Core Metadata Element Set (DCMES) data. Mostly
information about who edited a page, when, and other simple stuff.
Titles, format, etc. This is a common vocabulary that's very
useful for general-purpose bots.
* cc: Creative Commons metadata. Gives license information; there
are a few tools and search engines that use this data.
* linksto, linksfrom, links: Internal wiki links to and from a page.
"links" is a shortcut for both.
* image: DCMES information about images in a page.
* history: version history of a page; who edited the page and when.
* interwiki: links to different language versions of a page.
* categories: which categories a page is in.
* inpage: a special model for blocks of RDF embedded into the source
code of MediaWiki pages; see "In-page RDF" below for info.
== Special:RDF ==
You can view RDF for a page using the [[Special:Rdf]] feature. It
should be listed on the list of special pages as "Rdf". Enter the
title of the page you want RDF for in the title box, and choose one or
more of the RDF models from the multiselect box. You can also select
which output format you want; XML is probably most useful and can be
viewed in a browser.
The Special:Rdf page can also be called directly, with the following
parameters:
* target: title of the article to get RDF info about. If no target
URL is provided, the special page shows the input form.
* modelnames: comma-separated list of model names, like
"links,cc,history". Default is a list of standard models,
configurable per-site (see below).
* format: output format; one of 'xml', 'turtle' and 'ntriples'.
Default is XML.
== In-page RDF ==
Any user can make additional RDF statements about any resource by
adding an in-page RDF block to the page. The RDF needs to be in Turtle
format (http://www.dajobe.org/2004/01/turtle/), which is extremely
simple. It's a subset of Notation3
(http://www.w3.org/DesignIssues/Notation3.html), for which there is a
good introduction. (http://www.w3.org/2000/10/swap/Primer.html)
RDF blocks are delimited by the tag "<rdf>". They're invisible for
normal output, but they can provide information for RDF-reading items.
Here's an example:
Mathematics is ''very'' hard.
<rdf>
<> dc:subject "Mathematics"@en .
</rdf>
Here, the rdf block says that the subject of the article is
"Mathematics". Note that <> in Turtle means "this document". Another
example:
Chilean wines are quite delicious.
<rdf>
<> dc:source <http://example.org/chileanwines.html> .
<http://example.org/chileanwines.html>
dc:creator "Bob Smith" .
</rdf>
Here, we've said that the article's source is another Web page on
another server; we can also say that that other Web page's author is
Bob Smith.
In-page RDF is displayed whenever the "inpage" model is requested for
Special:RDF; it's one of the defaults. It's also useful for people
making MediaWiki extensions; you can have users add information in
in-page RDF, and then extract it and read it using the function
MwRdfGetModel(). This lets users add data that isn't for presentation
but perhaps for automated tools to use.
Note also that MediaWiki templates are expanded when in-page RDF is
queries. So if the syntax of Turtle is daunting, you can add templates
that make it easier. For example, we could create a template
Template:Source for showing source documents:
<rdf>
<> dc:source <{{{1}}}> .
<{{{1}}}> dc:creator "{{{2|anonymous}}}" .
</rdf>
We could then make the same statement as above with a template
transclusion:
{{source|http://example.org/chileanwines.html|Bob Smith}}
Note that a number of namespaces are pre-defined for your RDF blocks.
Some basic namespaces are provided by RAP; you can define custom
namespaces with the global variable $wgRdfNamespaces . In addition,
each of the article namespaces is mapped to a namespace prefix in
Turtle, so you can say something like this:
<rdf>
Wikitravel_talk:Spelling dc:subject Wikitravel:Spelling .
:Montreal dc:spatial "Montreal" .
</rdf>
Note that the default prefix (":") is the article namespace.
== Customization ==
There are a few customization variables available, mostly for
programmers.
$wgRdfDefaultModels -- an array of names of the default models to use
when no model name is specified.
$wgRdfNamespaces -- You can add custom namespaces to this associative
array, of the form 'prefix' => 'uri' .
$wgRdfModelFunctions -- an associative array mapping model names to
functions that generate the model. See below for
how to add a new model.
$wgRdfOutputFunctions -- A map of output format to functions that
generate that output. You can add new output
formats by adding to this array.
== Extending ==
You can add new RDF models to the framework by creating a model
function and adding it to the $wgRdfModelFunctions array. The function
will get a single MediaWiki Article object as a parameter; it should
return a single RAP Model object (a collection of statements) as a
result. For example,
function CharacterCount($article) {
# create a new model
$model = ModelFactory::getDefaultModel();
# get the article source
$text = $article->getContent(true);
# ... and its size
$size = mb_strlen($text);
# Get the resource for this article
$ar = MwRdfArticleResource($article);
# Add a statement to the model
$model->add(new Statement($ar, new
Resource("http://example.org/charcount"),
new Literal($size)));
# return the model
return $model;
}
You can then give the model a name like so:
$wgRdfModelFunctions['charcount'] = 'CharacterCount';
You can add a message to the site describing your model like so:
$wgMessageCache->addMessages(array('rdf-charcount' => 'Count of
characters'));
You can also create model-outputting functions if you so desire; they
should accept a RAP model as input and make output as they would to
the Web. This is probably only useful if you want a specific RDF
encoding mechanism that's not RDF/XML, Turtle, or Ntriples; for
example, TriG or TriX.
== Future ==
These are some future directions I'd like to see things go:
* Store statements in DB: statements could be stored in the database
when the page is saved and retrieved when needed. This would make it
to do extended queries based on information about *all* pages.
* Performance: there wasn't much performance tuning and there are
probably way too many DB hits and reads and such.
* Semantic tuning: I'd like to make sure that the statements in the
standard models are accurate and useful.
== Bugs ==
Send bug reports, patches, and feature requests to Evan Prodromou
<evan(a)wikitravel.org> .
--
Evan Prodromou <evan(a)wikitravel.org>
Wikitravel (http://wikitravel.org/) -- the free, complete, up-to-date
and reliable world-wide travel guide
>From my experience, the reason MediaWiki is attractive is scalability and reliability. There's a lot of wikis that can provide the protection features needed, but they just aren't built to scale to thousands of users and 50K+ nodes. It's a lot easier to hack access restrictions and features onto a scalable architecture than it is to make a non-scalable but feature rich app scale.
I can understand why Wikipedia developers would be reluctant to add it- they don't need it. There is a side argument though- that if MediaWiki is used in more settings, people will write extensions and improvements for it, some of which WikiMedia can use. Wether this would be enough to be worth the tradeoff is hard to say.
>From Brion's comments though, if people were to produce docs (or better- code) to implement such a control mechanism, you would at least consider it for mainline?
Gabe
-----Original Message-----
From: mediawiki-l-bounces(a)Wikimedia.org [mailto:mediawiki-l-bounces@Wikimedia.org] On Behalf Of Jej
Sent: Tuesday, November 22, 2005 1:48 AM
To: MediaWiki announcements and site admin list
Subject: Re: [Mediawiki-l] Page access restiction (resend)
It seems that many people need this feature. Since I published this patch (http://conseil-recherche-innovation.net/index.php/1974/04/11/41-restrict-pa…),
we have 25% of visits on this single article. Generaly people need restriction feature to manage small wikis, private intranets. I guess they choose mediawiki for the syntax, templates, and reliabilty/community support, and not for the ability to manage projects as big as wikipedia nor encyclopedies.
From a wikipedia point of view, I think nobody wants more restriction features (protect is enough). We cannot polute the core of MW with features not useful for WP, it's difficult to maintain patches for ages, and it's not necessary to carry WP specific features in a forked project. So my choice would be a fifth... E. To write some specifications from needs, abstract the problem, and start a new project
:) Any ideas ?!...
Read you,
Jej
>Asking again...
>
>If someone were to get gung-ho about implementing access control
>measures in MediaWiki that go way beyond the immediate needs of
>Wikipedia, would you prefer that that person/group:
>
>A. Submit patches for inclusion in mainline MediaWiki B. Submit
>patches to extend the MediaWiki core to allow for a security layer C.
>Submit patches to modularize/wrap some MediaWiki components (e.g.
>the parser) in a way that they can be used as libraries for an
>otherwise forked/rewritten wiki product D. Fork MediaWiki
>
>Curious Robla
>
>
>
_______________________________________________
MediaWiki-l mailing list
MediaWiki-l(a)Wikimedia.org
http://mail.wikipedia.org/mailman/listinfo/mediawiki-l
Hi
I did the following steps to test the mediawiki backup
and restore process. But I cannot fully restored the
mediawiki, some template lost and some articles lost
too.
The steps I did are as following,
1. I dump the database.
mysqldump -u root -p --single-transaction chpwikidb >
backup.sql
2. Then I ftp the backup.sql in the BINARY mode from
server A to server B
3. Create a database with the same name 'chpwikidb' on
server B.
$ mysql -u root -p
Enter root password: ****
mysql> create database chpwikidb;
mysql> use chpwikidb;
4. Import 'chpwikidb' from A on B by executing the
dumped sql script, make sure it is located in the
current directory.
mysql> source backup.sql;
5. Install MediaWiki as usual, but change the
database's name from the default 'wikidb' to
'chpwikidb' MediaWiki will detect there is a
pre-existing database and try to upgrade it when
necessary.
Also, the language setting MUST be the same as the
original one!!
But Finally, the new mediawiki I restored on server B
does not have all the info of the mediawiki on Server
A
Would you pls kindly let me know what I did wrong.
Thanks
jc
__________________________________
Yahoo! FareChase: Search multiple travel sites in one click.
http://farechase.yahoo.com