I've updated the Special:Export schema in MediaWiki 1.5 to include a
<siteinfo> chunk with some site configuration information.
For example at:
http://commons.wikimedia.org/wiki/Special:Export/Chlamyphorus_truncatus
you can see the custom namespace assignments.
and at:
http://es.wiktionary.org/wiki/Especial:Export/aristocratizar
you can see that wiki's marked as case-sensitive.
This should make it easier to ensure that page titles are processed
correctly on import.
I've also added an xml:space="preserve" hint to the <text> elements,
which may or may not keep some overzealous tools from stripping the
whitespace automatically.
The XML Schema definition for version 0.3 of the export format is at
http://www.mediawiki.org/xml/export-0.3.xsd and in the docs/
subdirectory in MediaWiki CVS HEAD.
We'll be providing the full-wiki public data dumps in this format
starting in a few days, replacing the old SQL dumps. For the reasons
behind this switch, see my earlier posting:
http://mail.wikipedia.org/pipermail/wikitech-l/2005-May/029298.html
-- brion vibber (brion @ pobox.com)
----- Original Message -----
From: "Rowan Collins" <rowan.collins(a)gmail.com>
To: "MediaWiki announcements and site admin list"
<mediawiki-l(a)wikimedia.org>
Sent: Tuesday, July 05, 2005 4:10 AM
Subject: Re: [Mediawiki-l] RHES* to Debian Sarge migration
On 01/07/05, Edward De Jongh <Edwardd(a)discovery.co.za> wrote:
> No where would I?
By clicking the "history" tab, just like with any other article.
> It has been sorted though. I simply clicked on edit
> and there was all the info, once I saved it, it was fine. I would still
> love to know how/why.
Probably a caching issue: you probably viewed the main page just after
you installed the new wiki, and the rendered version got cached; then,
when you imported the other version directly into the database, the
software didn't know to clear this cache. Consequently, the old
version was loaded from the cache until you forced it to be purged
[the simplest way of doing this, by the way, is to use the parameter
"action=purge" in the URL].
--
Rowan Collins BSc
[IMSoP]
_______________________________________________
MediaWiki-l mailing list
MediaWiki-l(a)Wikimedia.org
http://mail.wikipedia.org/mailman/listinfo/mediawiki-l
.
No where would I? It has been sorted though. I simply clicked on edit
and there was all the info, once I saved it, it was fine. I would still
love to know how/why.
Thanks
ed
-----Original Message-----
From: mediawiki-l-bounces(a)Wikimedia.org
[mailto:mediawiki-l-bounces@Wikimedia.org] On Behalf Of Dori
Sent: Friday, July 01, 2005 2:10 AM
To: MediaWiki announcements and site admin list
Subject: Re: [Mediawiki-l] RHES* to Debian Sarge migration
On 6/30/05, Edward De Jongh <Edwardd(a)discovery.co.za> wrote:
> Hi all I'm new to this list so please point me in the right direction
> should I have posted this here incorrectly.
>
>
>
> I have a mediawiki instance running on a RHES8 server and I am trying
to
> migrate it to Debian Sarge. I have followed numerous docs to the T and
> got quite far my problem however is this: when I dump my wikidb to a
> .sql file and then recreate the new wikidb the standard main page:
> http://somehost/index.php/Main_Page end is still the normal page and
not
> the one I have on my original wiki site on RHES8. However when
clicking
> the "Random page" link I get back all the original info that was on my
> old wiki.
>
> So my question is how, do I tell my wiki where to get the main page
info
> from.
Have you checked the history of [[Main Page]]?
_______________________________________________
MediaWiki-l mailing list
MediaWiki-l(a)Wikimedia.org
http://mail.wikipedia.org/mailman/listinfo/mediawiki-l
I've been installing a number of different wikis on one MySQL server, but accidentally neglected to specify a different table name prefix on all of the configuration pages until I started to realize that each subsequent wiki I was creating, which was supposed to have a different language-configuration, was being configured with the language designation of whatever the last wiki was which I had installed.
When I realized what I was (or was not) doing I tried altering the "$wgDBprefix" in LocalSettings to a new prefix but quickly found that I had screwed up everything unless I was able to somehow get back to the configuration page and specify a different table name finally. But after spending far too long trying to poke around in MySQL I can't seem to figure out how to create or alter the original table name prefix.
Is there some way I can do this or have I got to delete the installation altogether now?
Thanks in advance.
Malcolm
I'm trying to install MediaWiki 1.5beta1, but I cannot get past the
installation page. I always get the error "Couldn't connect to
database" associated with the "MySQL server" form.
At this point, you might say "a-ha, MySQL 4.1... authentication
protocol ... pre-4.1-style password!". But here's the odd thing: I'm
running MySQL 4.0.20-standard, not 4.1+.
The database I'm trying to connect to is on localhost (I have also
tried the values "127.0.0.1" and ""). The settings I'm typing in
worked for a test system.
Any ideas would be greatly appreciated.
Matt
> > Out wiki has been running fine - really fine - until yesterday.
> > Starting this morning our editors and myself started seeing when we
> > used Mozilla-based browsers that we had to flush cache to see a change.
> > http://sequenza21.com/wiki/
> Shot in the dark, but could the date on the server be wrong suddenly?
>
> Ed
The date's fine from the shell I have. The Apache time stamp is CDT and the
MediaWiki timestamp is UDT (I assume). Is that the problem perhaps? The dates
are fine. Should I set the MediWiki time to match our website provider's
Apache time?
TIA...
JEff
Hi folks,
I really want to install wikimedia on my computer so I can use it as a
simple way of creating content for a website.
I only need to install it on my own machine - not on a website (ie.
remote server), because I just want to use it as an easier way to
create the text and links for a website (and transfer them to a proper
web-creation tool later).
(It's for a good cause - it's a website about spirituality and
psychology).
I'm using Windows 2000 and I was wondering if anyone was willing to
volunteer to help me install it!
I've followed the instructions on the site
(http://meta.wikimedia.org/wiki/Wiki_on_a_stick), but I've run into a
problem.
When I get to the section called "Initial wiki configuration", section
2.1, where it says "Fill out the form..." I find that there is no
proper form on the page - just alot of gobbledygook.
When I click "INSTALL" it's supposed to "write" a file, but it does
nothing. Also I don't think i'm doing the earlier section about the
batch file properly either.
I really need a little help on this. Or - perhaps someone might even
be so kind as to create a readymade folder with all the stuff in it
for me...?! (Alot to ask, I know!)
But I'm really stumped.
If any brave soul was willing to volunteer for this Arthurian task I'd
really appreciate it!
Hello MediaWiki Gurus:
I have set-up the user restriction and page white list features
described in "Preventing Access"
(http://meta.wikimedia.org/wiki/Access_Restrictions).
There are 2 enhancements I would like to make to these security
features, I have been looking around in the code and am not seeing a
clear path to pursue, could someone provide a hint or two?
The two enhancements I am trying to do are:
(1) To restrict searches to logged in users, or change search to use
alternative search engine for non-logged in users.
(2) To amend to pages specified in $wgWhitelistRead with pages in a
specific/special category (e.g. Category:WhiteList)
Why do I think I should try to do these two things?
- I know that there are a lot of new security features coming in 1.5
and I want to good future compatibility
- I need to make sure I don't leak non-public or not-yet approved
information
(about 80% of the site content requires restriction)
- Public information could be leaked though the search function
(existence of topics/documents/etc)
- I need pages to default (fail-safe) to restricted, but I need users
to be able to flag a page as public or released
(I can use policy controls and category monitoring to detect user
errors etc.)
- It is unclear to me if Jérôme Combaz's patch matches the 1.5 security
philosophy, and doesn't default to restricted
Is there a better way (that I appear unaware of) to try to meet my
needs?
Thanks to anyone who has any insights or can push me toward good ideas.
If I am able to get something working I will post results back to Wiki
Media.
Thanks and best regards,
Erik
I am attempting to install the new Mediawiki 1.5beta1 on a server
belonging to a group I am part of. After uploading the files, I get
this message:
Warning: ini_set() has been disabled for security reasons in
/data/members/paid/t/h/the-5.nl/htdocs/www/stneg/wiki/config/index.php
on line 118
Warning: main(includes/Defines.php): failed to open stream: No such
file or directory in
/data/members/paid/t/h/the-5.nl/htdocs/www/stneg/wiki/config/index.php
on line 122
Fatal error: main(): Failed opening required 'includes/Defines.php'
(include_path='.:/data/apache/php/mmp_lib:/data/session') in
/data/members/paid/t/h/the-5.nl/htdocs/www/stneg/wiki/config/index.php
on line 122
-----
I'm not fluent in PHP, but a bit of research suggests to me that the
administrator needs to enable ini_set(). When I e-mailed him, he
replied that it was a permissions problem, and that it was something I
needed to do because I uploaded the files.
What needs to be done? More precisely, how do I or the admin go about doing it?
Thanks in advance,
-Chops
Out wiki has been running fine - really fine - until yesterday.
Starting this morning our editors and myself started seeing when we used
Mozilla-based browsers that we had to flush cache to see a change.
http://sequenza21.com/wiki/
It's possible that our website provider changed an Apache setting and
I'm not to keen on changing the Headers. Is this problem well known and
is there a solution that I can ask our provider to change? Or do I need
to modify the headers in a certain manner?
Thanks for any advice, the problem has ground our building process to a
halt as it seems our contributors are becoming confused that their
contributions are not 'sticking'.
Jeff Harrington
WikiSysop Sequenza21
jeff(a)parnasse.com