I want to know if there is a "suggested " set of ownership & permissions
for a mediawiki install>
I currently have the site running on linux server: basic LAMP; installed
& running ( not correctly) in /vat/www/mywiki. I have been having a
great number of errors in uploading images as well as having
instantCommons images thumbnails created. Just want to make sure that I
have it set up correctly.
Also are the maintenance scheduled scripts supposed to run
automatically. I have been doing a lot of upgrading & the script
runJobs.php seems to require manually running it. Is that correct.
I'm trying to get Scribunto working and keep receiving this error when
trying to use Modules:
Script error: Lua error: Cannot create process: proc_open(/dev/null):
failed to open stream: Operation not permitted.
Does this mean that proc_open is restricted on my server?
Not sure to where to publish some helpful gallery CSS add-ons. I've crafted
some CSS (patched together from things I've found on the net) for creating
the following inside a Mediawiki:
1. A "Pinterest" "Masonry" Like Gallery. This is where a gallery of photos
dynamically fit together inside rows. This is pure CSS -- it doesn't use
Masonry. Tested in almost all of the major browsers; however, most likely
will not work correctly in lower versions of ie. Semantic Results will
display formatted inside the gallery if the ask query is inside the
starting div and ending div.(tested with a video ask statement that pulled
all the videos I had on the site -- where the ask statement prints out to a
the gallery but the image sizes will not automatically re-size to the row
size like the other images do.
2. Expand Image Size upon Hover. This is where an image expands to double
the size it when the mouse or hand (on touch) goes over it. Will work with
Additionally will work with outside photos that are hot-linked and with
some types of embedded photos. Normally the image will expand and float
over other near-by images. In ie, when combined with the "Pinterest"
gallery above, the middle row images will enlarge inside the row but not
will float other images in the other rows.
Both CSS galleries can work together.
Of course I plan on having these on my site, but they seem like some things
more people would like. I plan on having an explanation on my site on how
do to these things, but it seems like there should be a better place to
However since they're not actually extensions not sure if they should be
published on Mediawiki.org. So where should they be published? (if they
I'm receiving this error:
Error creating thumbnail:
line 57: convert: command not found
But in LocalSettings.php I have convert set as:
$wgImageMagickConvertCommand = "/usr/local/bin/convert";
And $ls -l /usr/local/bin/convert shows:
-rwxr-xr-x 1 root root 25225 Apr 21 2011 /usr/local/bin/convert
What am I missing?
First of all thanks to everyone here making this piece of art.
Well, actually i need to convince my boss to move from XWIKI to MediaWIKI,
but the most difficult problem is the migration
Would you please give me any clue about the easiest way to migrate the
whole content from XWIKI to MediaWIKI
Thanks in advance :)
I am looking for a great PHP developer to join the software
development department at Wikimedia Germany. We have a lot of backend
tasks to do around Wikidata especially for the support of Wikimedia
Commons. More details about the position are available at
https://wikimedia.de/wiki/PHP_Backend_Developer_(f/m) If this is you
please do apply. If you know someone who fits please send them them
the link. This is a great chance to make a difference around
Lydia Pintscher - http://about.me/lydia.pintscher
Product Manager for Wikidata
Wikimedia Deutschland e.V.
Tempelhofer Ufer 23-24
Wikimedia Deutschland - Gesellschaft zur Förderung Freien Wissens e. V.
Eingetragen im Vereinsregister des Amtsgerichts Berlin-Charlottenburg
unter der Nummer 23855 Nz. Als gemeinnützig anerkannt durch das
Finanzamt für Körperschaften I Berlin, Steuernummer 27/681/51985.
Sorry for this help-asking email, I am just new here, and if this email is
not appropriate her please tell me where I should go.
I am just setting up a mediawiki on a linux server (both mediawiki and
linux are new to me), and have met a few problems. Now I want to enable the
email notification, let new users can confirm through email. I just
following this page:
to add the following lines into mediawiki/includes/DefaultSettings.php:
*$wgSMTP = array(*
* 'host' => "smtp.ym.163.com <http://smtp.ym.163.com>", // could also
be an IP address. Where the SMTP server is located*
* 'IDHost' => "ym.163.com <http://ym.163.com>", // Generally this
will be the domain name of your website (aka mywiki.org
* 'port' => 25, // Port to use when connecting to the
* 'auth' => true, // Should we use SMTP authentication
(true or false)*
* 'username' => "admin(a)createfuture.cn <admin(a)createfuture.cn>", //
Username to use for SMTP authentication (if being used)*
* 'password' => "XXXXXXXX" // Password to use for SMTP authentication
(if being used)*
which ym.163.com is providing enterprise email service for free, support
other domain name like what i put there.
After this, i visit my mediawiki through Chrome, go to Preference page, at
the bottom of page there is a Email confirmation box in red, click "Confirm
your email address", then and then, the webpage shows the following message:
*CreateFuture's Wiki could not send your confirmation mail. Please check
your email address for invalid characters.*
*Mailer returned: Failed to set sender: apache(a)192.168.6.110
<apache(a)192.168.6.110> [SMTP: Invalid response code received from server
(code: 501, response: 5.1.7 Bad sender address syntax)]*
I have googled it for a very long time, but didn't get anything useful. Is
there anybody can help me to solve this problem? Or direct my which manual
or mediawiki help page I should read? Many thanks!
== Closing the Phabricator RFC ==
As previously announced , we've been facilitating an RFC proposing to
replace Wikimedia's current product management tools and development
toolchain by a tool called Phabricator:
We'd like to thank everybody for discussing and testing Phabricator and
providing very helpful feedback for the last three weeks! In order to
move forward and avoid letting the RFC be forgotten in a dusty corner of
the wiki, it's now time to close and summarize it.
The goal of the RFC was to gauge interest in simplifying our development
toolchain and consolidating our tools (gitblit, Gerrit, Jenkins,
Bugzilla, RT, Trello, and Mingle) into Phabricator.
At first glance, it seems that there is support for this proposal. The
consensus is also that there are blockers that must be addressed before
any migration is considered, and that any migration must be carefully
planned and as carefully executed.
To be clear: It's not yet been decided to move to Phabricator. The RFC
has shown that there is interest and enthusiasm about Phabricator, and
this means resources could now be devoted to work more specifically on
the blockers and the migration plan. We expect that there will be
another (shorter) discussion down the road to serve as a reality check.
Its format will be lighter than that of the RFC, since its goal will
mostly to check that blockers have been resolved and the migration plan
== Plan for blockers and migration ==
A first phase of the migration would focus on migrating all the Bugzilla
data to Phabricator, and merging the project management work being done
in Trello and Mingle.
A second phase —that could be worked in parallel— would focus on
substituting Gerrit for code review, and RT. There is also a possibility
to deprecate Jenkins as a continuous integration tool, but this option
is out of scope for now.
A few blockers have been identified in these areas, and we will
collaborate with the Phabricator community to fix them.
The schedule for this migration depends on resolving those issues which
are blockers for Wikimedia moving to Phabricator.
The Engineering Platform team at the Wikimedia Foundation would lead
this project allocating the resources necessary to define a detailed
plan, proceed with the migration, and maintain the new infrastructure.
A longer version, requirements to still sort out first, and concerns
raised have been summarized by Quim at
== Join the next discussions ==
There will be a session about Phabricator at the Wikimedia hackathon in
Zürich this week-end (see ), as well as another IRC discussion next
week (in #wikimedia-office on Wednesday, May 14, at 18:00 UTC:
Guillaume and Andre (and Quim)
Andre Klapper | Wikimedia Bugwrangler
I am the webmaster of Moegirlpedia. We currently got about 60,000
visitors/day and noticed that single VPS can't support the website. This is
a wiki about Japanese Anime. So images, videos and dynamic functions are
Currently the topology of servers looks like:
A Linode 2GB for mysql with memcached.
A linode 4GB for Mediawiki with APC and image storage.
Multiple VPS or host by donates for Varnish cache.
We would like to add multiple web servers for Mediawiki and storage image
on a single major server. However, we don't know how to set Mediawiki so
that it will upload and storage images to another server.
Any help about speeding up and images storage are appreciated!
Bask Ice | 晒太阳的冰
2290 3rd Avenue Basement, New York, United States