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
Dear All,
According to http://download.wikimedia.org/enwiki/latest the most
recent successful history dump of enwiki is from 2008-Apr-05. Do you
happen to know, if a more recent version of this file (or an
equivalent) is available somewhere? I'm not quite sure that within
reasonable time the history of the pages could be download directly
through the "history" links.
Thanks
Hi guys,
I moved my wiki from the root directory of socialopedia.org to a
subdirectory xxx.alwaydata.net/wiki to which is linked the transferred
domain socialopedia.org.
I imported the .htaccess file and, as I expected, it introduced problems.
Basically, I can only see the page content and no more the sidebar, the
footer, etc...
You may check at www.socialopedia.org
I tried to change a bit my .htaccess file, but I couldn't fix it... BTW, I
was before with 1.13 and went to 1.14
Here is the content:
RewriteEngine on
RewriteCond %{REQUEST_URI} !index.php
RewriteCond %{REQUEST_FILENAME} -f [OR]
RewriteCond %{REQUEST_FILENAME} -d [OR]
RewriteCond %{REQUEST_FILENAME} -l
RewriteRule ^(.+) $1 [L]
# redirect to main page
RewriteRule ^/*$ /index.php?title=Accueil [L,QSA]
# anything else is to be treated as a title
RewriteCond %{REQUEST_URI} !index.php
RewriteRule ^(.+)$ /index.php?title=$1 [L,QSA]
Inserting /wiki/ before index.php in the rules does not help, since it wants
to go to www.socialopedia.org/wiki, whereas socialopedia.org redirects to
the wiki subfolder...
Any help would be of great help !
Regards, Rmatt
Hi John, thank you for the reply. I commented out the relevant section in
main.css and refreshed the screen but it refused to work. I then deleted the
section completely but it still didn't work either. I thought that by
restarting the computer, it would work but it didn't.
Actually, I am still having problems with:
body.page-Main_Page #siteNotice { display: none; }
in Monobook.css. It looks like the Monobook.php page is not working. Do I
need Monobook.js? (I didn't use it as it is said to be superseded by
Common.js.)
PM Poon
On Tue, Mar 10, 2009 at 9:52 AM, Rice, John <jrice(a)e3computer.com> wrote:
> The first heading is actually controlled from main.css
> http://www.aseanpedia.com/skins/monobook/main.css?195
>
> In that file you will find this line:
>
> #firstHeading {
> margin-bottom: .1em;
> line-height: 1.2em;
> padding-bottom: 0;
> }
>
>
> The firebug plugin for FireFox is a great tool for identifying these css
> issues.
>
>
>
>
>
> -----Original Message-----
> From: mediawiki-l-bounces(a)lists.wikimedia.org
> [mailto:mediawiki-l-bounces@lists.wikimedia.org] On Behalf Of Ekompute
> .info
> Sent: Monday, March 09, 2009 8:48 PM
> To: MediaWiki announcements and site admin list
> Subject: [Mediawiki-l] Mediawiki:Monobook.css file not working
>
> Hi, it seems like my Mediawiki.Monobook.css file is not working. I have:
>
> body.page-Main_Page h1.firstHeading { display: none; }
>
> in Monobook.css but the page title still appear in my homepage at
> Aseanpedia<
> http://www.aseanpedia.com/Aseanpedia,_the_free_online_unofficial_
> ASEAN_Encyclopedia>.
> It used to be working fine until I transferred my Mediawiki files into a
> folder instead of in publichtml, thinking it is neater. However, it did not
> work, so I reverted it to its original position. All other functions seem
> to
> work just fine, except this page.
>
> PM Poon
> _______________________________________________
> MediaWiki-l mailing list
> MediaWiki-l(a)lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
>
>
> _______________________________________________
> MediaWiki-l mailing list
> MediaWiki-l(a)lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
>
I'm using rawhtml in my mediawiki and putting javascript into the
pages. This is mostly working fine, except when the javascipt has an
ampersand (&) in it. MW converts the ampersand into an entity and
breaks the script. Is there any way to stop MW from doing this?
Rob
Web Design and Technical Documentation
Faculty of Science
University of Auckland
Aotearoa New Zealand
Building 303 Room 395
Phone +64 9 373 7599 x85336
http://www.sit.auckland.ac.nz/User:Robert_Carter
I’ve just put in Wikimedia’s org application for Google Summer of Code
2009… Hopefully we’ll get in. :)
http://www.mediawiki.org/wiki/Summer_of_Code_2009
^ Add and update cool project ideas as a starting point for student
applicants!
We’ve had mixed luck in previous years with GSoC, but I think we’ve got
enough internal bandwidth this year that we can make sure there’s enough
effort put into interacting with the student candidates ahead of time to
pick the coolest and most go-get-em self-starter awesome projects and
then support them through the project term.
I’ve also tossed up a student application template if you want to get
started early. :)
http://www.mediawiki.org/wiki/Summer_of_Code_2009/Application_template
-- brion
What is the current best practice for moving all images from one wiki "A" into a second, ACTIVE wiki "B"? Requirements are:
1. Detect any image naming collisions between the two wikis, and resolve them before import
2. Transfer all "File:..." pages from wiki "A" into wiki "B", including their revision history
3. Transfer all images from wiki "A" into wiki "B", including all old versions
Is /maintenance/importImages.php is the right tool? I could imagine finding all images in the /images folder and feeding them to importImages.php. Will that work together with importing all "File:..." pages from wiki "A" into wiki "B" via /maintenance/importDump.php? (It won't import all revisions of each image however....)
Or could we simply copy the /images folder from the first wiki to the second (using ordinary filesystem copy operations), and then use /maintenance/importDump.php to import the entire "File:" namespace from the first wiki into the second? Do all the hashed image file paths get preserved and continue to work?
Or is there a better method? Remember that wiki "B" is active and not a new, empty wiki.
Thanks,
DanB
Hi, I was trying to upgrade from Version 1.10 to 1.14 and ended up with data
corruption. Apparently, there is something wrong with my /includes/media
files:
*Warning*: imagesx(): supplied argument is not a valid Image resource in *
/home/aseanped/dummipedia.org/includes/media/Bitmap.php* on line *210
*Error is visible on Firefox at
Dummipedia.org<http://dummipedia.org/Free_Simplified_Online_Encyclopedia>but
returns empty pages in Internet Explorer.
**I tried to restore the database but apparently, the same errors still
remain. How can I resolve this problem. (Fortunately, in shifting the
website, I still maintain my website with my old webhost so all is not
lost.) I have always have a fear of upgrading as I haven't done it before
and haven't been able to do it. Just couldn't understand the manual, LOL.
PM Poon
I've installed the extension OggHandler on my wiki, but the server hasn't
FFmpeg installed so it cannot create the still image of video.
I'd like to know if it's possible to replace the dinamic generated by FFmpeg
image with a static image (like an icon).
Thanks
Hi List!
I was asked to move one of our wikis (see
http://uwe-kern.de/winfwiki/index.php/Spezial:Version) from
"uwe-kern.de/winfwiki/index.php/" to the new domain
"wiki.intermoves.de/index.php/". The server is still the same, only the
document root changed (namebased virtual hosting).
So i copied all the wiki-files into the new directory, removed the images
directory from the old location and linked it into the new, and changed
$wgScriptPath in the new location's LocalSettings.php to match the new
URL:
old:
$wgScriptPath = "/winfwiki";
new:
$wgScriptPath = "";
All other pathes still have default values.
Then the wiki was accessable via both URLs.
When an article that links to other articles using the "[[articlename]]"
syntay was written by someone using the "uwe-kern.de/winfwiki/index.php/"
URL and someone else using "wiki.intermoves.de/index.php/" clicks the
links, he gets the "not found" apache error page:
Not Found
The requested URL /winfwiki/index.php/Testseite was not found on this
server.
Apache Server at wiki.intermoves.de Port 80
This behaviour is occasionally and we have no clue why.
If a page that contains false links is then edited using the new
"wiki.intermoves.de/index.php/" URL and saved again, the links work for
"wiki.intermoves.de/index.php/" but not always for
"uwe-kern.de/winfwiki/index.php/".
Could it be that paths are also stored in the DB and not
runtime-calculated?
We deactivated all caching and accelerating engines.
This is what LocalSettings says about caching:
## Shared memory settings
$wgMainCacheType = CACHE_NONE;
$wgMemCachedServers = array();
# When you make changes to this configuration file, this will make
# sure that cached pages are cleared.
$configdate = gmdate( 'YmdHis', @filemtime( __FILE__ ) );
$wgCacheEpoch = max( $wgCacheEpoch, $configdate );
Any help/hint is very welcome as we can't move our wiki until this issue
is resolved :(
With regards,
Heiner Wulfhorst