I'm happy to announce my latest MediaWiki extension, called Cargo:
If you use Semantic MediaWiki, or have been curious about it, Cargo may be
of interest to you. Cargo is essentially an alternative to SMW. It holds
much of the functionality of SMW and many of its related extensions, but
distilled into a fine brandy, if you will. It is one extension that
literally takes the place of 14 extensions, with a much smaller code base
and a significantly simpler database structure. It achieves this simplicity
by eschewing the use of Semantic Web triples in favor of a direct use of
database tables to store the data, with (usually) one table per template.
And querying of the data is done using a fairly thin wrapper around SQL.
If you have no interest in Semantic MediaWiki, on the other hand, you
probably won't be interested in Cargo either.
And if you know that I'm part of the SMW community, and are wondering why
I've created an extension that seeks to replace SMW, there's a long answer
to that, that we hashed out on the SMW mailing list. The short answer is
that I still consider myself very much a member of the SMW community, and
that I would call this new software an evolution, not a break from the past.
Feel free to check out the documentation, try it out, and let me know if
you have any questions.
WikiWorks · MediaWiki Consulting · http://wikiworks.com
I am updating an old 1.19 wiki to a new server with mediawiki 1.24. The
O/S has also gone from CentOS 6 to 7. So far no real problems, but when
I access the 'Special pages' link, all I see is a blank page. The PHP
error is logged as:
PHP Fatal error: Class 'SpecialAllpages' not found
on line 410
Has anyone else seen this? I'm not really sure what it means - or rather
what to do about it!
John Horne Tel: +44 (0)1752 587287
Plymouth University, UK
First, apologies if this is an inappropriate place to post this. It's just
that the ideal candidate is someone who can hit the ground running with
MediaWiki. If it is inappropriate please let me know and I'll refrain from
doing it in the future.
Second, I'm not involved with hiring...I just want to give the college
students in the Houston area an opportunity to apply for this cool opening.
If you get the position you will work with me a lot, so feel free to ask me
anything about what I do.
Okay, here's the semi-official job req:
Stinger Ghaffarian Technologies in Houston, TX is offering a paid
internship where you will get to work at NASA's Neutral Buoyancy Lab
(NBL) and Mission Control Center (MCC), working within the Mission
Operations group at Johnson Space Center in charge of Extravehicular
Activities (EVAs a.k.a. spacewalks). This group plans on-orbit
activities, trains astronauts to perform spacewalks (at the NBL and other
facilities), and assists astronauts with execution of missions from MCC.
For this internship the chosen applicant would be involved with all of
these planning, training and execution activities. Additionally, they would
be working on a project to improve the EVA Wiki (EVA's knowledge managment
system using MediaWiki ). The extent of this project depends upon the
chosen applicant's interests and skills. Applicants proficient in software
development could help improve existing software or developing their own
extensions. Other applicants could work on improving the content within the
wiki. For some info on how the EVA group uses MediaWiki see .
Applicants must be graduate students or undergraduate juniors or seniors.
Graduate students work 30-40 hours per week. Undergraduates work 16-28
hours per week. Application is open to all students, but goes through San
Jacinto College. To apply please contact Linda Drobnich at Linda.Drobnich
AT sjcd DOT edu.
I hope someone can help with a 1.23.8 to MW 1.24 upgrade and a custom
skin I am trying to convert. It is a very basic custom skin based on
Vector I "authored" a while ago, but without a proper understanding and
with lots of help from this list.
I get no output (blank) and I see the log says it is due to a skin
Looking through the release notes, I see the problem will be down to the
skin "auto-discovery" changes. Looking at the help page about migrating
skins to 1.24 :
I have tried to adjust my custom skin files but without success. In
1.24.1 skins/ I have :
ZedDocs is the custom skin based on Vector.
The Apache error I get is :
Tue Jan 13 15:43:10 2015] [error] [client 192.168.0.124] PHP Warning:
failed to open stream: No such file or directory in
/home/user/mediawiki-1.24.1/skins/zeddocs/ZedDocs.skin.php on line 9,
On line 9 of zeddocs/ZedDocs.skin.php I have/had :
require_once( dirname( __FILE__ ) . '/../Vector.php' );
If I set this to :
require_once( dirname( __FILE__ ) . '/../Vector/Vector.php' );
I get error :
[Tue Jan 13 16:38:50 2015] [error] [client 192.168.0.124] PHP Catchable
fatal error: Argument 1 passed to SkinVector::__construct() must
implement interface Config, string given, called in
/home/user/mediawiki-1.24.1/includes/Setup.php on line 285 and defined
in /home/user/mediawiki-1.24.1/skins/Vector/SkinVector.php on line 38,
I have tried to set up my skin files (and renamed as CamelCase) as per
the Skin_autodiscovery manual page.
I have made changes to files ZedDocs.php and ZedDocs.Skin.pnp, please
see the attached PHP files. I have added a .txt extension for the list
(just in case).
Can someone have a look and see where I am going wrong?
I have a situation where I'm introducing a group (internal to my
organization) to our internal wiki and adding them to a specific user
group. Instead of having each individual create an account, then contact me
to be added to the user group, its there a way to pre-load these users and
add them to the group before they login for the first time?
This way, the first time they login they can hit the ground running without
a back and forth of adding them to the group individually?
I thought about adding new rows to the "user" and "user_groups" tables, but
that doesn't seem to be the best way forward.
I have been testing the $wgReadOnly and $wgReadOnlyFile options. My
understanding is that these will prevent mediawiki from writing to the
database and hence not allow pages to be updated. I have tried both
options on servers running mediawiki 1.19.2 and 1.24.0 - neither option
on either server seems to work. In all cases I am still able to modify
For the $wgReadOnlyFile option I created the file with some plain text
in it, and change the ownership to that of the web server (apache).
Does anyone have any idea what I might be doing wrong here? I intend to
use the file option for wiki backups, but obviously don't want people
updating things while the backup is occurring.
John Horne Tel: +44 (0)1752 587287
Plymouth University, UK
Some recently downloaded templates from Wikipedia are calling for
Special:StablePages in the scripts. What is this and how do I install
it. I have Mediawiki 1.24.1 installed and completely updated. Any tips
JW Foster & Associates
This may be simple to everyone, but i just started working with MediaWiki
in our company. we are using MediaWiki for maintaining our documents in
company's internal wiki site.
I was trying to insert a *text box with all the quick links* below the
right Table of contents box on the project homepage; was not successful
Could anyone help me with this... Really appreciate your time and help.