For some updates to MDC we plan to do, these extensions will be needed. These should be installed on staging once the staging upgrade to MediaWiki 1.9.x has been done and tested, so that we can work on our new breadcrumbs and other templates.
Moving these two bugs into Server Operations: Projects as it is more of a project.
Component: Server Operations → Server Operations: Projects
These extensions are at these URLs: http://meta.wikimedia.org/wiki/ParserFunctions http://meta.wikimedia.org/wiki/StringFunctions
I'm working on adding these extensions. StringFunctions requires the mbstring PHP extension. Do we have that installed? It's not part of the standard install of PHP, but is required for support of multibyte characters, so there's a fair chance we do have it.
Yes we have mbstring.
Also, I'll need to put these in the settings file when you have them ready.
OK, I've committed the extensions into the repository. The docs for them say these lines need to be added to the settings file: require_once( "$IP/extensions/ParserFunctions/ParserFunctions.php" ); require_once ("$IP/extensions/StringFunctions/StringFunctions.php");
I've also add the RDF extension; that needs to be hooked in as well.
These have been installed.
Status: NEW → RESOLVED
Last Resolved: 12 years ago
Resolution: --- → FIXED
Did the RDF extension get switched on too? It's been around 20 minutes and isn't showing up yet on the versions special page.
What is the process for installing the rdf extension? It can't be required like the other two, because it immediately starts spitting out text.
Turns out RDF requires the RAP API extension for PHP. There's info on that here: http://sites.wiwiss.fu-berlin.de/suhl/bizer/rdfapi/ Once that's installed, this is what the RDF readme says to add to the LocalSettings.php file: define("RDFAPI_INCLUDE_DIR", "/full/path/to/rdfapi-php/api/"); require_once("extensions/Rdf/Rdf.php");
I'm going to file a separate bug for RDF since it also involves installing the PHP extension.
Product: mozilla.org → mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.