Hello all
At the developer meetup, I announced that Wikimedia Deutschland is offering
contracts for a couple of projects we feel are important. We again invite anyone
to apply NOW for any project that interests you.
The DEADLINE for applying is SUNDAY, APRIL 19!
We did not receive any offer for the most urgent project: Evaluate the impact
of using flagged revisions on the German Wikipedia, see
<http://www.mediawiki.org/wiki/WMDE_contract_offers/Evaluate_the_impact_of_u…>.
We feel that it would be very helpful to run a full analysis on this before the
English language Wikipedia decides on how to implement flagged revisions. It's a
powerful tool, and we should make sure we use it to it's full potential.
Below, the other projects are listed again:
* Rewrite CatScan, a tool for finding pages in a set of categories recursively,
based on various criteria -
http://www.mediawiki.org/wiki/WMDE_contract_offers/Rewrite_CatScan
* Store interwiki-links in the database, just like we already store
interlanguage-links -
http://www.mediawiki.org/wiki/WMDE_contract_offers/Store_interwiki-links_in…
* Improve the Gadgets extension to allow for gadgets to be enabled per default,
be restricted to specific user groups, etc -
http://www.mediawiki.org/wiki/WMDE_contract_offers/Improve_the_Gadets_exten…
* Implement full support for TIFF files, including multi-page TIFFs, similar to
how DjVu is handled -
http://www.mediawiki.org/wiki/WMDE_contract_offers/Implement_full_support_f…
If you would like to help with any of the above, please contact me at
<daniel.kinzler AT wikimedia.de> and provide the following information:
* Your real name and country of residence
* How you plan to go about implementing the desired function
* Any experience working with MediaWiki
* How many working hours you would spend on it, and how much you ask for it
* In what time frame you would be able to do the job
This information is also available at
http://www.mediawiki.org/wiki/WMDE_contract_offers
Thanks you all for your interest!
-- daniel
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
I would like to know how to allow only some ip (local LAN) to edit. Or
to block some ip`s (all the others) from editing, adding users, comment,
etc. Before placing this question I was really at least 10 minutes
searching at http://www.mediawiki.org/wiki/MediaWiki.
Thank you
2009/4/9 Sarel Wesssels (Agri Wiki) <swessels(a)agriwiki.co.za>:
> What is the easiest why to let all users register, to get a username and
> password, and then they will be able to change or edit articles on a wiki.
>
> Currently all articles are 'open' and anyone, without logging in, can
> change these articles. But the risk involved in that is getting bigger
> everyday.
>
> Should we change all articles protection to 'block new and unregistered
> users'?
>
Hi Sarel,
You will probably also get just a little bigger response if you start a new thread for your questions. (Or at least change the subject.)
Courtney Christensen
I've run into a problem on my wiki where it appears image conversions are
consuming all my available memory.
I've uploaded a screen shot of the the processes currently running, you can
see it here:
http://www.richardson.co.nz/load.jpg
Note the "convert" process that is consuming 99megs per instance. How can I
stop this from happening?
Thanks,
Samuel Richardson
Freelance Web Developer
www.richardson.co.nz | 0405 472 748
Sorry, I forgot to include my system data in the first message.
Product Version
MediaWiki <http://www.mediawiki.org/> 1.14.0
PHP <http://www.php.net/> 5.2.9 (apache2handler)
MySQL <http://www.mysql.com/> 5.0.67-log
I want to setup 4 wikis ol, ml, ssip and v4v with the last 3 sharing the
tables: 'user', 'user_groups', 'interwiki', 'ipblocks' of the first one: ol
I know that I can do this by using only one database for all 4 wikis and
different table prefixes for each. However, I was hoping to be able to
use 4 separate dbs so that I don't "put all my eggs in one basket", so
to speak. My problem is that my host setup automatically assigns a
different username to each db (as well as arbitrarily placing dbs on
different db servers according to availability at the time of creation,
but I can solved that by simply creating, deleting and creating again
until I get them on the same db server). I can also change the passwords
so that they are the same.
So I was looking into the coding to see if I might be able to make a
change to enable the shared situation even though the db usernames are
all different. I found where the code in database.php where function
tableName( $name ) adjusts the input variable (which is the
concatenation of the simple tablename with the database name) to replace
the database name with that of the shared one for those tables which are
in the shared array - set in local settings. This all looks great, but
it occurred to me, how can this work for table JOIN operations? Don't
JOIN operations necessarily need to be relative to the same database?
Is there any working installation with shared tables on different
databases so that it is known that this works? Given that it does
(somehow?), why would it also not be possible to have different
usernames for the different databases?
Do the experts here see any totally impossibility to me setting things
so that for a shared table the username can be changed in addition to
the database name (and perhaps even change the db server as well)? I am
not asking directly how this would done (although such help would
certainly be appreciated), since I am confident that if it can be done
at all, then I can figure it out myself.
Another possibility that I have thought of (particularly if shared
tables do not actually work on different databases, but only on
different prefixed tables within one database, because of the join
problem that I mentioned above) is to place the db parameters of all 4
dbs in the local settings of each (in an array of course) and then
whenever a shared table is *written to* it will be written to on all 4
wiki databases. In this manner they will all be kept in sync. What do
the experts here think of that idea, given that something easier and
less modifying of the system code is not possible.
Thanks muchly in advance for any helpful ideas.
--Paul Wakfer
MoreLife for the rational - http://morelife.org
Reality based tools for more life in quantity and quality
The Self-Sovereign Individual Project - http://selfsip.org
Self-sovereignty, rational pursuit of optimal lifetime happiness,
individual responsibility, social preferencing & social contracting
--
--Paul Wakfer
MoreLife for the rational - http://morelife.org
Reality based tools for more life in quantity and quality
The Self-Sovereign Individual Project - http://selfsip.org
Self-sovereignty, rational pursuit of optimal lifetime happiness,
individual responsibility, social preferencing & social contracting
Hi Bobby,
There is definitely a problem with the Content-type generated at your
site:
http://en.wikipedia.org/w/index.php?
title=MediaWiki:Common.css&usemsgcache=yes&ctype=text%
2Fcss&smaxage=18000&action=raw&maxage=18000 yields text/css
and <snip>/w/index.php?
title=MediaWiki:Common.css&usemsgcache=yes&ctype=text%
2Fcss&smaxage=18000&action=raw&maxage=18000 yields text/html
Some stylesheet URLs (which I'm guessing are served directly by the
web server, Apache/2.0.63 (Unix) mod_ssl/2.0.63 OpenSSL/0.9.8b
mod_auth_passthrough/2.1 mod_bwlimited/1.4 FrontPage/5.0.2.2635 PHP/
5.2.5) seem to be fine. (like /w/skins/common/shared.css?195)
Can you check your Apache httpd error logs?
I can't dig much more right now, maybe someone else has a suggestion.
Jeremy
On Apr 14, 2009, at 8:42 PM, Bobby S wrote:
<snip>
> I deleted the common.js page because I thought it might be what was
> causing the css issue. If you look at the site on Firefox the css
> doesn't load. If you look at the site on IE or Chrome it does. Not
> sure why this is - really odd.
>
> Regarding the Feedback widget, I just couldn't get it working so I had
> removed the stuff for now. If you wanted to try I have set up a
> username and password for you:
<snip>
> I gave you upgraded status so you can play. :)
>
> Bobby
>
> On Mon, Apr 13, 2009 at 8:41 PM, Jeremy Baron
> <jeremy(a)tuxmachine.com> wrote:
>> You don't have a staging site I can see? If you like I can leave
>> the URL
>> out of public communications...
>>
>> Do you have a URL for the CSS issue? (or is that all mediawiki
>> instances?)
>> open the Error Console (tools menu) and clear it then open the
>> page with
>> the css issue and see what it says. (make sure it's set to show all
>> messages)
>>
>> Jeremy
>>
>> On Apr 13, 2009, at 11:10 AM, Bobby S wrote:
>>>
>>> I know this makes it more difficult, but I would rather not right
>>> now
>>> - I am launching in two weeks, so I will revisit it then - this is
>>> just a refinement, obviously not part of the base product, so I am
>>> fine with that. Thanks so much though! I will follow up soon.
>>>
>>> By the way, have you ever had issues with Firefox not loading
>>> monobook.css and common.css? I seem to have that issue, but only in
>>> Firefox - even when I click CTRL + F5 it doesn't work.
>>>
>>> Bobby
>>>
>>> On Sun, Apr 12, 2009 at 6:02 PM, Jeremy Baron
>>> <jeremy(a)tuxmachine.com>
>>> wrote:
>>>>
>>>> Can I have a link to your wiki to see it myself?
>>>>
>>>> On Apr 12, 2009, at 5:56 PM, Bobby S wrote:
>>>>>
>>>>> Jeremy,
>>>>>
>>>>> Hey - I tried what you wrote re: Get Satisfaction's widget, but
>>>>> what I
>>>>> end up with is a text FEEDBACK link at the bottom of each
>>>>> page. It
>>>>> should be a feedback graphic like the one on the right of this
>>>>> page:
>>>>>
>>>>> http://getsatisfaction.com/widgets
>>>>>
>>>>> Also, with regard to the capitalization issue - that actually
>>>>> is my
>>>>> point, that Fort_wayne_tincaps has never existed, but when you
>>>>> type in
>>>>> fort wayne tincaps it goes to Fort Wayne TinCaps. On my
>>>>> Mediawiki
>>>>> install I created a page called "Fort Wayne TinCaps", but when
>>>>> I type
>>>>> in "fort wayne tincaps" it says the page doesn't exist -
>>>>> basically I
>>>>> would have to set up a redirect.
>>>>>
>>>>> Bobby
>>>>>
>>>>> On Sun, Apr 12, 2009 at 2:51 PM, Jeremy Baron
>>>>> <jeremy(a)tuxmachine.com>
>>>>> wrote:
>>>>>>
>>>>>> I forgot to mention that you'll need to load the script and
>>>>>> wait until
>>>>>> the
>>>>>> JS is finished loading before calling it's functions.
>>>>>>
>>>>>> So try this:
>>>>>> common.css:
>>>>>> @import
>>>>>>
>>>>>> url('http://s3.amazonaws.com/getsatisfaction.com/feedback/
>>>>>> feedback.css');
>>>>>>
>>>>>> common.js:
>>>>>>
>>>>>>
>>>>>> importScriptURI("http://s3.amazonaws.com/getsatisfaction.com/
>>>>>> feedback/feedback.js");
>>>>>> addOnloadHook(function importGSFN(){
>>>>>> var tab_options = {}
>>>>>> tab_options.placement = "right"; // left, right, bottom, hidden
>>>>>> tab_options.color = "#FFF"; // hex (#FF0000) or color (red)
>>>>>>
>>>>>>
>>>>>> GSFN.feedback('http://getsatisfaction.com/jetblue/feedback/
>>>>>> topics/new?display=overlay&style=idea',
>>>>>> tab_options);});
>>>>>>
>>>>>> The thing about adding the container still applies with this
>>>>>> code.
>>>>>>
>>>>>> On Apr 12, 2009, at 2:38 PM, Jeremy Baron wrote:
>>>>>>>
>>>>>>> There's no need to write an extension or modify any php.
>>>>>>>
>>>>>>> You can accomplish that just by modifying common.js and
>>>>>>> common.css
>>>>>>> ( http://www.mediawiki.org/wiki/Manual:Interface/Common.js ,
>>>>>>> http://www.mediawiki.org/wiki/Manual:Interface/Common.css )
>>>>>>>
>>>>>>> It looks like part of it is just a floating iframe w/
>>>>>>> position fixed +
>>>>>>> absolute so it might be fine out of the box but you might end up
>>>>>>> having
>>>>>>> a
>>>>>>> piece placed at an undesirable location. (possibly changing
>>>>>>> from page
>>>>>>> load
>>>>>>> to page load or browser to browser)
>>>>>>>
>>>>>>> If there are any problems you can use an undocumented feature
>>>>>>> of their
>>>>>>> JS
>>>>>>> (at least not documented at getsatisfaction.com/widgets ):
>>>>>>> add this line before GSFN.feedback: tab_options.container =
>>>>>>> "mycontainerid";
>>>>>>> add a div somewhere on your site with that id
>>>>>>> Then the getsatisfaction html will be placed in that
>>>>>>> container div
>>>>>>> instead
>>>>>>> of just document.write'ing. "mycontainerid" can be whatever
>>>>>>> you want
>>>>>>> (assuming no conflicts with Since it's an undocumented feature
>>>>>>> there's
>>>>>>> no
>>>>>>> guarantee that it won't break without notice.
>>>>>>>
>>>>>>> On Apr 12, 2009, at 1:35 PM, Bobby S wrote:
>>>>>>>>
>>>>>>>> I am trying to add the Get Satisfaction widget to
>>>>>>>> Mediawiki. Here is
>>>>>>>> some sample code:
>>>>>>>>
>>>>>>>> <style type='text/css'>@import
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> url('http://s3.amazonaws.com/getsatisfaction.com/feedback/
>>>>>>>> feedback.css');</style>
>>>>>>>> <script
>>>>>>>>
>>>>>>>> src='http://s3.amazonaws.com/getsatisfaction.com/feedback/
>>>>>>>> feedback.js'
>>>>>>>> type='text/javascript'></script>
>>>>>>>> <script type="text/javascript" charset="utf-8">
>>>>>>>> var tab_options = {}
>>>>>>>> tab_options.placement = "right"; // left, right, bottom,
>>>>>>>> hidden
>>>>>>>> tab_options.color = "#FFF"; // hex (#FF0000) or color (red)
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> GSFN.feedback('http://getsatisfaction.com/jetblue/feedback/
>>>>>>>> topics/new?display=overlay&style=idea',
>>>>>>>> tab_options);
>>>>>>>> </script>
>>>>>>>>
>>>>>>>> Does anyone know how I could do this? I assume there are
>>>>>>>> two routes
>>>>>>>> -
>>>>>>>> one directly in Monobook.php and another as an extension. I'm
>>>>>>>> actually surprised there isn't an extension for this, but could
>>>>>>>> anyone
>>>>>>>> help me out on what to do?
>>>>>>>>
>>>>>>>> Thanks!
>>>>>>>> Bobby
Hi, I'm going to be away from an internet connection for a few weeks at a
time over the next few weeks but would like to be able to carry a snapshot
of my Wiki to reference so I can work on some materials while I'm on the
road. I've been looking around via Google and I'm finding a number of
projects that look promising but everyone I've looked at so far seems to
fall into the vaporware category. Does anyone know of a workable solution?
Something that runs in either Linux or XP would be good. Or maybe there's
something out there that'll let me take an export of a bunch of page from my
wiki and produce a pdf or something?
Anything that'll let me carry and comfortably view a bunch of articles from
the wiki would be helpful.
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
I have an odd problem - it seems the monobook.css and common.css
aren't loading for Firefox (but they are for IE and Chrome). I have
tried CTRL + F5 to reload the cache, and I have even noted this
problem on a few different PCs, so it isn't isolated. Has anybody
every noticed this issue before? I am on 1.14, and the only thing
that is different about my installation is that it is behind a
username and password to get to the site right now. Below is the
portion of the page source that has the CSS calls.
<link rel="stylesheet" href="/w/skins/common/shared.css?195"
type="text/css" media="screen" />
<link rel="stylesheet" href="/w/skins/common/commonPrint.css?195"
type="text/css" media="print" />
<link rel="stylesheet" href="/w/skins/monobook/main.css?195"
type="text/css" media="screen" />
<!--[if lt IE 5.5000]><link rel="stylesheet"
href="/w/skins/monobook/IE50Fixes.css?195" type="text/css"
media="screen" /><![endif]-->
<!--[if IE 5.5000]><link rel="stylesheet"
href="/w/skins/monobook/IE55Fixes.css?195" type="text/css"
media="screen" /><![endif]-->
<!--[if IE 6]><link rel="stylesheet"
href="/w/skins/monobook/IE60Fixes.css?195" type="text/css"
media="screen" /><![endif]-->
<!--[if IE 7]><link rel="stylesheet"
href="/w/skins/monobook/IE70Fixes.css?195" type="text/css"
media="screen" /><![endif]-->
<link rel="stylesheet"
href="/w/index.php?title=MediaWiki:Common.css&usemsgcache=yes&ctype=text%2Fcss&smaxage=18000&action=raw&maxage=18000"
type="text/css" />
<link rel="stylesheet"
href="/w/index.php?title=MediaWiki:Print.css&usemsgcache=yes&ctype=text%2Fcss&smaxage=18000&action=raw&maxage=18000"
type="text/css" media="print" />
<link rel="stylesheet"
href="/w/index.php?title=MediaWiki:Monobook.css&usemsgcache=yes&ctype=text%2Fcss&smaxage=18000&action=raw&maxage=18000"
type="text/css" />
<link rel="stylesheet"
href="/w/index.php?title=-&action=raw&maxage=18000&smaxage=0&ts=20090413150731&gen=css"
type="text/css" />
<!--[if lt IE 7]><script type="text/javascript"
src="/w/skins/common/IEFixes.js?195"></script>
<meta http-equiv="imagetoolbar" content="no" /><![endif]-->
