Project:Support desk

Welcome to the MediaWiki Support desk, where you can ask MediaWiki questions!

(Read this message in a different language)

See also

Other places to ask for help:

• Chat rooms
• Email groups
• StackOverflow (third-party)
• Unofficial MWUsers forum (third-party)

Before you post

• Check the basic How does MediaWiki work? guide.
• Check the FAQ and Errors and symptoms .
• If your question is about a specific feature, check the relevant technical manual , end-user help or extension page and consider asking on its talk page .
• For issues about the mediawiki.org website, report to Current issues instead.
• For trying out wiki editing, use the Sandbox instead.

Post a new question

1. To help us answer your questions, please indicate which versions you are using, as found on your wiki's Special:Version page:
   • MediaWiki version
   • PHP version
   • Database type and version
2. Please include the web address (URL) to your wiki if possible. It's often easier for us to identify the source of the problem if we can see the error directly.
3. To start a new thread, click "Start a new topic".

Hi crontab space is full how to add space in pywikibot toolforge No space left on device /usr/local/bin/crontab: unable to execute remote crontab command.......

@Kaleem Bhatti How is this related to the MediaWiki software? Please ask Toolforge questions in Toolforge support places. Thanks.

Principally all core, Hebrew-installed MediaWiki 1.34.2 with Extension:ContactPage.

My ContactPage contact form comes with two default fields - "Your email address" field and "subject" field.

The labels of these two fields are automatically translated to Hebrew as "כתובת הדוא"ל שלך" and "נושא".

I desire to change the translations to different translations.

I can change the translations with JavaScript but I desire a backend (most preferably directly from the MediaWiki CMS) solution.

How to change the label translations of ContactPage?

See Localisation

This is quite a large page with most data not associated with the very specific task I ought to do; furthermore, Extension:ContactPage is not mentioned there;

I desire a user-interface way to control the translations, is that even exist? (changing from files with text editor is not a good solution for me because the new translations will get automatically changed in upgrades).

I upgraded MediaWiki 1.27.3 to 1.35 on a test system and have been struggling to figure out why the toggle icons no longer showed and why the Category Tree no longer showed in the sidebar

I regressed the Vector Skin to that provided in MediaWiki 1.34 and both now work.

Some incompatible change was likely made in the Vector skin version between 1.34 and 1.35. Posting this here in case it might help someone else in their upgrade and in the hope that the MediaWiki developers can investigate why the toggle icons no longer display in the sidebar using the Vector skin and why the categorytree-portlet is not displayed after upgrading to MW 1.35

i think collapsible sidebars got removed because people thought it gave the impression that the site loaded slowly.

Dont know about cattree, that should still work afaik

Thanks Bawolff

The MediaWiki:Sidebar still collapses or expands but no icons are displayed

I tried all the entries I found on getting the CategoryTree to display in the sidebar as a portlet but none of them worked until I renamed the Vector skin folder and installed the Vector skin from MediaWiki 1.34

I forgot to mention that I am using Extension:CollapsibleVector to collapse the sidebar

As far as I know the Vector skin provided the toggle icons, It that is not the case, why would reverting to the 1.34 Vector skin resolve my problem

by toggle do you mean the icon to collapse/uncollapse or something else?

Yes, that is what I mean

I'm trying to set up and configure SimpleSAMLphp on a MediaWiki installation to connect with and authenticate via the AWS SSO service. I'm totally new to setting up SSO, so am completely stumbling and haven't been able to track down much of any documentation on how to do this. The end goal is to move the entire MediaWiki site behind authentication. SimpleSAMLphp and PluggableAuth are installed and a rough configuration is in place. The LocalSettings.php file currently contains the following:

# PluggableAuth

wfLoadExtension( 'PluggableAuth' );

$wgGroupPermissions['*']['autocreateaccount'] = false;

$wgPluggableAuth_EnableAutoLogin = true;

$wgPluggableAuth_EnableLocalLogin = true;

$wgPluggableAuth_EnableLocalProperties = false;

$wgPluggableAuth_ButtonLabel = 'Sign On with SSO';

$wgPluggableAuth_ExtraLoginFields = [];

#SimpleSAML

wfLoadExtension( 'SimpleSAMLphp' );

$wgSimpleSAMLphp_InstallDir = '/bitnami/mediawiki/extensions/SimpleSAMLphp';

$wgSimpleSAMLphp_AuthSourceId = 'https://portal.sso.us-west-2.amazonaws.com/saml/assertion/<<redacted>>';

$wgSimpleSAMLphp_RealNameAttribute = 'RealNameAttribute';

$wgSimpleSAMLphp_EmailAttribute ='EmailAttribute';

$wgSimpleSAMLphp_UsernameAttribute = 'UsernameAttribute';

When we go to the MediaWiki, we're presented with the login screen and an option to use SSO. Once the username and password are provided and we click on the "Sign On with SSO" button, we're given a blank http://<<site>>/wiki/Special:PluggableAuthLogin page.

What are we missing?

make sure to enable php error reporting (see How to debug)

Right... that gave us enough error data to at least get a missing prerequisite installed. Thanks! Now digging into configuration to make sure we've gotten that right.

Okay, got quite a bit further. We now need to exchange metadata with the IdP, but only MediaWiki is running on this server so we have no access to the /simplesaml web portal. Do we need to install Apache and configure all of that, or can this be done through MediaWiki since that's the only place we're using SimpleSAMLphp?

Got it all working after a few rounds of banging my head. Thanks for your help.

Hello

I bought a domain http://www.gwki.ga on freenom. And I added nameserver so connected my wiki server. (Installed urlshortener too)

So I need to set .htaccess file, but I don't know how to.

Help me please.

+ and LocalSettings.php settings please.

Try this for .htaccess: Manual:Short_URL/Apache.

What extension does the English Wikipedia use to add all of the additional page protection options/permissions?

None that I'm aware of. See Manual:$wgRestrictionLevels

Thank you!

Problem resolved.

I see that I have to be an administrator to do everything I need to do...but I can't find anywhere how to become an administrator.

I would assume that the first registered account would have admin rights...but I don't seem to have those rights.

Please help!

Thanks much

FAQ#Initial user was not created by installer or it is not an administrator.

Thank you!

I'm running the latest version, so the part I'm getting hung up on is how to do the following

Execute the following SQL statement against the database:

   * INSERT INTO user_groups ( ug_user, ug_group ) VALUES ( <id>, 'bureaucrat' ), ( <id>, 'sysop' );

What does it mean to execute that statement...where would I do that?

Thanks much!

You'd do that from a mysql command line client (or phpmyadmin). Its probably easier to use one of the other methods listed in the FAQ if you're not sure about how to edit your database.

Thank you! I think I've got it now :-)

Hi ! How did you solved your last problem ? I am also getting hung up on how to do the following

Execute the following SQL statement against the database:

  * INSERT INTO user_groups ( ug_user, ug_group ) VALUES ( <id>, 'bureaucrat' ), ( <id>, 'sysop' );

Where you did it ?

Thanks in advance

REduardo (I have a ticket above, but waiting for answer...!

Please mention complete with all filled names. SQL query so that i can use the same to change .

If you just want to give admin rights to a user, instead of SQL queries, see Manual:CreateAndPromote.php.

Where can i runn this code ?

The SQL query through phpMyAdmin, the PHP code through SSH.

Hi, I am trying to build some functionality into an extension and I need to get the results of a query (cirrussearch query), which I know how to do in js using the API.

For this extension, I need to do that in php, so I'm planning on just doing new ApiQuery() etc.

Is that the best way, or am I missing something obvious?

Thank you

See Extension:CirrusSearch#API

Thank you very much Ammarpad.

The CirrusSearch API is also http api, my question was more related to the fact I'm calling it from within PHP.

i.e. using the quiery api from a browser that makes sense (or the cirrussearch api for that matter), but I'm wondering if from within PHP, is the best practice way also to use the ApiQuery API directly?

I'm just asking because I have grepped the code and I see generally no instances of apis being used within the php codebase, with the exception of tests of course.

Thank you

I noticed a recent comment by Ammarpad in "Issues after updating wiki to latest version" linking to phab:T263911, which ends with a comment stating that the following is not needed any more:

if( defined( 'MW_INSTALL_PATH' ) ) {
    $IP = MW_INSTALL_PATH;
} else {
    $IP = dirname( __FILE__ );
}

$path = array( $IP, "$IP/includes", "$IP/languages" );
set_include_path( implode( PATH_SEPARATOR, $path ) . PATH_SEPARATOR . get_include_path() );

require_once( "$IP/includes/DefaultSettings.php" );

if ( $wgCommandLineMode ) {
    if ( isset( $_SERVER ) && array_key_exists( 'REQUEST_METHOD', $_SERVER ) ) {
        die( "This script must be run from the command line\n" );
    }
}

I still have all this (though no known problems arising). Is there an easy way to get a fresh LocalSettings.php for adding my site settings to again? I've not cleaned it out since installing version 1.5 or 1.6...

You usually do that by deleting the existing LocalSettings.php before upgrading (or preferably by moving it to somewhere else so that you can restore any custom settings you might have later). The installer looks for it at its default location and if it's there, it won't be regenerated.

I see now. I think I followed the instructions each time which now say:

After extracting the tarball, you should copy or move some files and folders from the old installation directory to the new one:

• LocalSettings.php, which contains your old configuration settings.

...

Run the update script

Next time I upgrade should I run upgrade.php without my old LocalSettings.php file, then merge the old and newly-created files into one file containing the current "boilerplate" stuff plus the necessary settings (database credentials, skins, extensions etc) from the old file?

Yes

Thank you very much :-)

Thinking about it, which is preferable? Downloading the files then:

• Running upgrade.php as described above.
• Running install.php as described in Manual:Installing_MediaWiki#Run_the_installation_script.
• Using the online installation form, as described in Manual:Config_script#Opening_the_MediaWiki_installation_form.

On most wikis, the project namespace is just an alias. For example, on Wikipedia, the project namespace is Wikipedia. On Wiktionary, it is Wiktionary. On Wikibooks, it is Wikibooks. MediaWiki is a project that stands out in this area, because it just uses the namespace Project. I kind of know why, but I am asking to make sure. To my knowledge, the namespace is just "Project," because logically, MediaWiki should have "MediaWiki:" as the namespace prefix, but MediaWiki: is a restricted namespace for system messages. So Project: has to be used instead, is that the reason why?

Project: is the "canonical" name of that namespace. Like for example, all English namespace names can be used on any wiki in other languages and they will redirect to the localized namespace name.

I'm not sure but you're probably right that it remains in its canonical form here to prevent it a clash on the MediaWiki: namespace.

Note also that the project namespace is often the same as the SITENAME, but it doesn't need to be the same

yes, we use Project: for $wgMetaNamespace due to conflict with MediaWiki