Project:Support desk

Jump to: navigation, search

About this board

<translate>

vde   Welcome to MediaWiki.org's Support desk, where you can ask MediaWiki questions!

There are also other places where to askCommunication: IRCCommunication#Chat, mailing listsMailing lists, Q&A etc.

Before you post

Post a new question

  1. To help us answer your questions, please always indicate which versions you are using (reported by your wiki's Special:Version page):
    • MediaWiki
    • PHP
    • Database
  2. Please include the URL of your wiki unless you absolutely can't. It's often a lot easier for us to identify the source of the problem if we can look for ourselves.
  3. To start a new thread, click "Start a new topic".
Language: English  español

</translate>

By clicking "Add topic", you agree to our Terms of Use and agree to irrevocably release your text under the CC BY-SA 3.0 License and GFDL
70.162.99.246 (talkcontribs)

Hi All,

Trying to upgrade from 1.25.2 to 1.27.1 on a RHEL 6.8 system running php 5.5.29 with mysql 5.5.45 and receiving the below errors.

I downloaded the tar.gz mediawiki directly from mediawiki.org and uncompressed it to a new directory and then copied over all of the "other files" listed at Manual:Upgrading#Other files . I didn't have any extensions installed other than the ones that come as part of the tar.gz download.

I then ran the upgrade.php and then navigate to the site, at which point I get the below errors.

I have verified that the /tmp directory is writable:

ls -l | grep tmp

drwxrwxrwt. 6 root root 12288 Sep 26 20:01 tmp

Any help/suggestions appreciated,

[298bb9adbc1dbdac3e37308f] /mediawiki-1.27.1/ MWException from line 132 of /var/www/mediawiki-1.27.1/includes/cache/localisation/LCStoreCDB.php: Error writing to CDB file "/tmp/l10n_cache-en.cdb.tmp.206954764".

Backtrace:

#0 /var/www/mediawiki-1.27.1/includes/cache/localisation/LocalisationCache.php(1021): LCStoreCDB->set(string, boolean)

#1 /var/www/mediawiki-1.27.1/includes/cache/localisation/LocalisationCache.php(462): LocalisationCache->recache(string)

#2 /var/www/mediawiki-1.27.1/includes/cache/localisation/LocalisationCache.php(379): LocalisationCache->initLanguage(string)

#3 /var/www/mediawiki-1.27.1/includes/cache/localisation/LocalisationCache.php(294): LocalisationCache->loadSubitem(string, string, string)

#4 /var/www/mediawiki-1.27.1/languages/Language.php(2561): LocalisationCache->getSubitem(string, string, string)

#5 /var/www/mediawiki-1.27.1/includes/cache/MessageCache.php(869): Language->getMessage(string)

#6 /var/www/mediawiki-1.27.1/includes/cache/MessageCache.php(827): MessageCache->getMessageForLang(Language, string, boolean, array)

#7 /var/www/mediawiki-1.27.1/includes/cache/MessageCache.php(768): MessageCache->getMessageFromFallbackChain(Language, string, boolean)

#8 /var/www/mediawiki-1.27.1/includes/Message.php(1178): MessageCache->get(string, boolean, Language)

#9 /var/www/mediawiki-1.27.1/includes/Message.php(801): Message->fetchMessage()

#10 /var/www/mediawiki-1.27.1/includes/Message.php(892): Message->toString()

#11 /var/www/mediawiki-1.27.1/includes/title/MalformedTitleException.php(49): Message->text()

#12 /var/www/mediawiki-1.27.1/includes/title/MediaWikiTitleCodec.php(296): MalformedTitleException->__construct(string, string)

#13 /var/www/mediawiki-1.27.1/includes/Title.php(3343): MediaWikiTitleCodec->splitTitleString(string, integer)

#14 /var/www/mediawiki-1.27.1/includes/Title.php(367): Title->secureAndSplit()

#15 /var/www/mediawiki-1.27.1/includes/MediaWiki.php(79): Title::newFromURL(NULL)

#16 /var/www/mediawiki-1.27.1/includes/MediaWiki.php(135): MediaWiki->parseTitle()

#17 /var/www/mediawiki-1.27.1/includes/MediaWiki.php(661): MediaWiki->getTitle()

#18 /var/www/mediawiki-1.27.1/includes/MediaWiki.php(519): MediaWiki->main()

#19 /var/www/mediawiki-1.27.1/index.php(43): MediaWiki->run()

#20 {main}

AhmadF.Cheema (talkcontribs)

From what I know this is caused because of incorrect ownership rules for the MW cache directory.

Try this: Topic:T7me7nu8tmlj8dhd

70.162.99.246 (talkcontribs)

All files in both directories are owned by the nginx user which is what both php-fpm and nginx run as.

FYI, the 1.25.2 site, had no issues with permissions when nginx owned everything.

Thanks

Ciencia Al Poder (talkcontribs)

You can try creating a temp folder inside MediaWiki installation files, giving all permissions to all users, setting $wgTmpDirectory to it and see if that solves the problem or not, so you can discard a permission or SELinux issue.

70.162.99.246 (talkcontribs)

Hi All,

Thanks for the help, it's always the easy things we miss.. Turns out the / partition was full. I cleared some space, tried again, but got an error about not being able to move the database to the new location.

I then tried Ciencia's suggestion of using an alternative temp location and that fixed the issue.

Thanks again!

Reply to "Resolved: Upgrade error, 1.25.2 -> 1.27.1"
Vjsuarez2002 (talkcontribs)

Hello, I am upgrading from MediaWiki version 1.16.4 and would like to go to the latest stable release 1.27.

I was wondering if I can upgrade straight to 1.27 or if I need to upgrade through the other versions first?

The sever is running Ubuntu 11.04 which I plan to upgrade to 16.04.

It is running PHP 5.3.5 which I will be upgrading to 5.6

MySQL 5.1.63

This comment was hidden by 87.123.36.240 (history)
This comment was hidden by 87.123.36.240 (history)
87.123.36.240 (talkcontribs)

Hi!

You can upgrade to 1.27 directly, there are no versions, which you have to take in between.

Note that MediaWiki 1.27 needs PHP 5.5 at least. On your old system with PHP 5.3, you only can use MediaWiki 1.26. So I would first upgrade PHP (which might make MW 1.16 non-functional at that point) and then upgrade MediaWiki to 1.27 in one go.

A complete guide is at Upgrade! If you have further questions, don't hesitate to ask!

Vjsuarez2002 (talkcontribs)

Thank you Very much!

Reply to "Upgrading from MediaWiki 1.16.4"
Wxl23 (talkcontribs)

On LinuxPadawan Wiki, I've followed Manual:Footer and yet I cannot get the footer links or text to change, except for the copyright stuff. Using $wgRights* I've managed to change the copyright stuff. I did add the Termsofservice link to the array. Changing the right pages has no affect on the actual footer:

Product Version
MediaWiki 1.26.2
PHP 5.5.9-1ubuntu4.17 (fpm-fcgi)
PostgreSQL 9.5.1
87.123.36.240 (talkcontribs)

The different pages, which you can change, are not located inside the LinuxPadawan_Wiki namespace, but inside the MediaWiki namespace, e.g. MediaWiki:Aboutsite.

Reply to "Footer links don't change"
212.9.128.231 (talkcontribs)

Hi,

I don't know exactly where/to whom I should ask this question...

Is it possible to add an advanced filter functionality to the arrays?

Example : https://en.wikipedia.org/wiki/Comparison_of_mail_servers

How can I get items that runs on Linux/Unix that have the GPLv2 license?

Is there still a module that can do that? How can I make this suggestion to the Wikipedia team?

Thanks!

Jackmcbarn (talkcontribs)

See if Semantic MediaWiki does what you want.

212.9.128.231 (talkcontribs)

In fact when I said "I don't know exactly where/to whom I should ask this question..." I meant I would like to submit the idea for the wikipedia.org website, but I only found article related to the content itself, not the website functionality... To avoid that I also search on the Chrome web store to find extensions that can handle that... but nothing interesting in that area.

And so I can't really test if Semantic MediaWiki does what I want. Maybe it is too sophisticated and too heavy...

121.214.103.220 (talkcontribs)

Just sort the columns by clicking on them. You can even shift+click to sort by multiple columns.

http://i.imgur.com/eeJCx3R.png

212.9.128.231 (talkcontribs)

Ok this is what I did till now, but sorting columns has limitations. What I would like to do is filtering column...

This comment was hidden by Quiddity (WMF) (history)
Reply to "Filter array"

max-width in Vector skin to control site layout width

9
111.69.202.141 (talkcontribs)

It's one of the dumber design aspects of MediaWiki and Wikipedia and their skins that the site fills 100% of the screen width, regardless of resolution, leading to a ridiculous appearance on high resolution monitors.

Short of a grid layout or other sophisticated approaches, what is required is a sensible max-width for the entire site layout, in the order of 1000 - 1300 px I suggest, allowing the site to scale horizontally below that but freeze on decent res screens.

I had a bunch of CSS modifications for Monobook that worked well, but they made use of the #globalWrapper which is not present in Vector. I am trying to migrate my old Monobook styling across to Vector.

I played around with adding styles to the various page elements in Vector, and even the <body> tag, but ended up frustrated trying to get the header and sidebar elements to cooperate.

Has anyone worked out some CSS for Vector that does the trick?

MarkAHershberger (talkcontribs)

This is as close as I can get:

/* upper blue line */
#mw-head-base {
	margin-left: auto !important;
	margin-right: auto !important;
  max-width: 1000px !important;
}
/* lower blue line + footer content */
#footer {
	margin-left: auto !important;
	margin-right: auto !important;
  max-width: 1000px !important;
}
/* main content */
#content {
	margin-left: auto !important;
	margin-right: auto !important;
  max-width: 1000px;
}
111.69.202.141 (talkcontribs)

Yep I got about as far myself.

  1. mw-page-base can be styled similarly but the page tabs, personal links, and the sidebar (which would now float over top of the content on lower resolutions) stump me.
MarkAHershberger (talkcontribs)

Just came up with something I like a little better:

/* upper blue line */
#mw-head-base {
	margin-left: auto !important;
	margin-right: auto !important;
	max-width: 1000px !important;
}
/* lower blue line + footer content */
#footer {
	margin-left: auto !important;
	margin-right: auto !important;
	max-width: 1000px !important;
}
/* main content */
#content {
	margin-left: auto !important;
	margin-right: auto !important;
	max-width: 1000px;
}
#bodyContent {
	z-index: 10;
}
#mw-navigation {
	margin-right: auto !important;
	max-width: 1190px;
        min-width: 1000px;
	position: absolute;
	top: 0;
        left: 50%;
        margin-left: -500px;
}
div#mw-panel {
	position: relative;
	left: 0;
	margin-left: -190px;
        width:160px;
}
div#mw-head {
	position: relative;
        right: 0;
        margin-right: 0;
        max-width: 1000px;
}
111.69.202.141 (talkcontribs)

That is an improvement. The page/discussion tabs are not left-aligned to the article, and the sidebar disappears off the screen at lower resolutions, but it's promising.

MarkAHershberger (talkcontribs)

I don't have time to do more now. And I still don't understand why you don't adjust your window to make it look better. But maybe someone else can offer more help.

74.91.102.250 (talkcontribs)

For me, I want to do this because my browser window has other tabs that conform to modern browsing standards, so I don't want to resize my window every time I switch to or from a wikipedia tab.

If someone is able to help, I think I almost have it, on a very vanilla vector-skinned site: http://www.aerenamasters.com/wiki/index.php?title=MediaWiki:Common.css

I can't figure out how to make the navigation behave well:

/* working ... */
#content{
        margin-left:auto !important;
        margin-right:auto;
	max-width: 950px;
}

#footer {
	margin-left: auto !important;
	margin-right: auto;
	max-width: 950px;
}

/* testing */
#mw-navigation {
        margin-left: auto !important;
	margin-right: auto;
	max-width: 1140px;
        top: 0;
}

Thanks for any help!

MarkAHershberger (talkcontribs)

For anyone who wants to try this but doesn't know how, you need to put it on your common.css page.

Spas.Z.Spasov (talkcontribs)

For Vector skin put next lines into MediaWiki:Vector.css or into your custom vector.css.

    /* set max width and fix the background */
    html,
    body {
    	position: relative;
    	margin-left: auto !important;
    	margin-right: auto !important;
    	max-width: 1280px;
        background-position: top left;
        background-repeat: repeat-x;
    	background-size: 100% 5em;
        background-image: url(/skins/Vector/images/page-fade.png);
        background-color: #f6f6f6;
        background-image: -webkit-gradient(linear,left top,left bottom,color-stop(50%,#ffffff),color-stop(100%,#f6f6f6));
        background-image: -webkit-linear-gradient(top,#ffffff 50%,#f6f6f6 100%);
        background-image: -moz-linear-gradient(top,#ffffff 50%,#f6f6f6 100%);
        background-image: linear-gradient(#ffffff 50%,#f6f6f6 100%);
    }
    
    /* set blue right border */
    .mw-body { border-right: 1px solid #A7D7F9; }
    
    /** fix the position of:
    			personal user menu
    			search bar
    			the pop-up indicator of language selector
    			search suggestions 
    **/
    #p-personal { right: 3pt; }
    #p-search { margin-right: 3pt; }
    .imeselector { position: fixed; }
    .suggestions { right: 3pt !important; }

If you want to apply this CSS for the restricted pages, write down next line into your `LocalSettings.php`, but first check this comment:

    $wgAllowSiteCSSOnRestrictedPages = true;
Reply to "max-width in Vector skin to control site layout width"
92.83.196.215 (talkcontribs)

Hey. I upgraded mediawiki from 1.25.2 to 1.27.1, on my testwiki, on xampp, using git. I used <nowiki>git clone -b REL1_27 https://gerrit.wikimedia.org/r/mediawiki/core</nowiki> and cloned it to htdocs in the xampp folder. Then I installed composer in the new mediawiki version. I must mention that I only managed to do the first step of the installation instructions for composer, as it gave an error at the second one 'corrupted installer'. I downloaded the composer.phar snapshot manually then managed to install it, after all, using the instruction provided on this wiki. Then I copied the extensions, images and localsettings from the old medawiki and ran both the web updater and update.php from the shell (just to be extra sure). The problem was that, every time I tried to log in, it would redirect me to the old version. After I moved the old version out of the folder, it gave me an error saying it can't find the site. So what I did was change the name of the new version to that of the old version. It worked, but I couldn't log in using the credentials that I had. It still let me log in on the wiki, though, because, after two failed tries, the option to 'skip' appeared. So I changed the password in the database, to both the root account and the personal account and now I got this error and I just can't get around to it:

Sorry! This site is experiencing technical difficulties.

Try waiting a few minutes and reloading.

(Cannot access the database)


You can try searching via Google in the meantime.

Note that their indexes of our content may be out of date.

I really don't know what else to do. I can't understand how to change the database to the new version, without having to change the name of the new version. Maybe I need to move the accounts or something? What am I doing wrong? Please reply as I would like to do the same thing on the real wiki. I must mention I used git clone instead of git checkout because the old version was downloaded and unzipped manually. I would appreciate any help. Thanks!

87.123.55.96 (talkcontribs)

So to sum it up, you say that you have installed the new version, that you have successfully updated the database. Basically at this point your upgrade is finished. If there are no problems, this would be it. There is nothing needed to change names or to move an account. At this point, you realized that you are having a problem with login, that is that login did not work.

The error message "Cannot access the database" points to wrong database credentials. I don't know, what you have changed in the steps where you say that you have changed the password in the database, but I think that what you did there was wrong.

Make sure that in your LocalSettings.php file you are using the correct username and password for your MySQL database! Should you have changed the password of the MySQL user, which you are using to access this database, make sure that both, the password as stored in MySQL and in LocalSettings.php, are the same!

Note that these credentials, of the MySQL user, which you also have in LocalSettings.php, are different from the credentials of MediaWiki users - even if you might have users inside MediaWiki, which have the same username as the MySQL user.

92.83.196.215 (talkcontribs)

Hey. So, I followed your steps and made sure that both the MySQL password and the one in localsettings match. I, also, saw that there is the script path so I changed that, too. Now, I am not getting any database errors, but even though the passwords match, I am still getting this: "Incorrect password entered. Please try again." I swear I entered the exact same password and username. I really have no idea what to do from here on. Basically, when I changed the password in 'phpmyadmin', I went to user accounts -> chose the right account -> edit privileges -> change password.

87.123.36.240 (talkcontribs)

Can you please specify, where the error message

 "Incorrect password entered. Please try again."

is displayed?

What you had before my answer was that MediaWiki was not working at all, because of wrong database credentials in LocalSettings.php: $wgDBuser and $wgDBpassword. Is it correct that error is solved? Is the wiki basically working now?

92.83.196.215 (talkcontribs)

Yes, the wiki is working now, but I cannot log in using those credentials, even though they are the same '''both''' in phpmyadmin and localsettings.php. I am getting the error message on the login screen (http://prnt.sc/cn06vs). Even though I made extra sure that I was using the right credentials, I kept getting the same error. Then, I simply entered the old password and it gave me this (the old password was made out of 6 letters): http://prntscr.com/cn09b5

92.83.196.215 (talkcontribs)

Well, I'll be damned. I changed the password on the wiki itself (on the second image) and it worked! It used to give a 'Fatal MWexception' or something like that, before, but it worked, thsi time. Anyway, thanks for helping me get through the issue!

This comment was hidden by AhmadF.Cheema (history)
87.123.36.240 (talkcontribs)

Please note that you are speaking about two very different things:

  • There is the password for the MySQL database. This password - and the according username - must be put inside LocalSettings.php. They belong inside the variables $wgDBuser and $wgDBpassword. With the error messages, which you are now getting, these two variables, $wgDBuser and $wgDBpassword, both are correct. Do not touch them, they are ok!
  • The second thing is the login into MediaWiki - this is what your two screenshots are showing. This login is using a MediaWiki username and the associated password. Both are stored inside the database (in the user table most likely) and they don't have 'anything to do with the MySQL credentials, which you ave to put into LocalSettings.php. What you need to log in to MediaWiki just is your MediaWiki username and its password.

The usernames inside MediaWiki and the usernames in MySQL (of which is used to access the database), are two completely different things!

92.83.196.215 (talkcontribs)

Since it's a wiki used for testing, I am using the same credentials all over the places and I thought that was the problem.

Reply to "Upgrading mediawiki version"
NessBirdSupport (talkcontribs)

Is there any way to configure the wiki to allow it to be embedded in an iframe? It is forbidden due to X-Frame-Options. I want to use the wiki as the help for my online system. It won't be editable by the public, so I'm not concerned with the security. I'm using a free hosting service where I can't make system-wide configuration changes.

Thanks for your help.

Florianschmidtwelzow (talkcontribs)

As far as I know, viewing a page in an iframe should be possible with the default configuration, just the edit page is not allowed to be framed.

NessBirdSupport (talkcontribs)

Hm. Strange. OK, thank you.

Reply to "Allow wiki in iFrame?"

How to customize article page, so that user contact to author/owner of article?

2
182.74.178.178 (talkcontribs)

How to customize article page, so that user contact to author/owner of article?

Malyacko (talkcontribs)

Article pages do not have "owners". Initial authors can be found under "History", which is linked on top of every article page.

Reply to "How to customize article page, so that user contact to author/owner of article?"
Shooshte (talkcontribs)

I am using the wikipedia API to query for a search word, for example by making a GET request to this URL:

https://en.wikipedia.org/w/api.php?action=query&format=json&list=search&utf8=1&srprop=snippet&continue=&srsearch=Slovenia

This query returns a total of 51429 hits, but will only display the first 10 results. From reading the documentation on this topic, I gather that to get the next 10 results I should pass in the continue parameter.

The relevant parameters in the API response are here:

continue: {

sroffset: 10,

continue: "-||"

}

So I build my url in the following way:

https://en.wikipedia.org/w/api.php?action=query&format=json&list=search&utf8=1&srprop=snippet&continue=-||&srsearch=Slovenia

But the URL returns the same set of results.

What am I doing wrong?

Reply to "Using the &continue parameter"

Is Crypto++ AES-256 GCM supports Windows XP?

4
Sudhirkumarsharma (talkcontribs)

Crypto++ AES-256 CBC mode supports Windows XP, but I want to know whether GCM ciphor mode also supports Windows XP?

Ciencia Al Poder (talkcontribs)

Your question doesn't seem related to MediaWiki. Maybe you're asking on the wrong site?

87.123.36.240 (talkcontribs)

It might be related to Manual:$wgSessionInsecureSecrets. I have added information on the different encryption mechanisms to that page some time ago.

The important thing is the PHP version I guess. If you are running a rather new version of PHP, chances are that the necessary algorithms will be in as well.

87.123.36.240 (talkcontribs)

On Windows XP, the last version of PHP, which you can run, is PHP 5.4. This version allows you to run any version of MediaWiki up to MediaWiki 1.26, but not MW 1.27.

With other words: MediaWiki 1.27, in which $wgSessionInsecureSecrets has been introduced as a new option, will not work on Windows XP. So basically, if you are running on Windows XP, $wgSessionInsecureSecrets and its possible values are irrelevant for you.

Reply to "Is Crypto++ AES-256 GCM supports Windows XP?"