Project:Support desk

Jump to: navigation, search

About this board

vde   Welcome to'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".
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
Maxedrom (talkcontribs)

Hello Comunity. Good morning.

Actually my Wiki, is configured to send mails using php mail, but i need to change to smtp autenticated. I need to know where i can change the parameters like username password and the smtp server.

Any one knows?

Reply to "PHP SEND MAIL"

Site just stopped working - (cannot access the database)

4 (talkcontribs)

Hi, the website just stopped working last night. The host - godaddy - confirmed there were no updates to the server. There are no error messages on the server log. I tried turning on debug as well with no errors being reported. The only indication i get is

Sorry! This site is experiencing technical difficulties.

Try waiting a few minutes and reloading.

(Cannot access the database)

I also checked the database path and the password - re entered just to make sure. I checked all database tables - these are ok. The tech support at godaddy had no answers confirming database paths/passwords and consistency of database tables. So assuming the database and connectivity is fine does anyone else know what it could be? Please click on the link above and click any of the subjects to test. Thanks

Ciencia Al Poder (talkcontribs)

Please set $wgShowExceptionDetails and $wgShowSQLErrors to true in LocalSettings.php and see if it gives at least a reason for the "Cannot access the database". Also, what SQL engine (mysql, sqlite...) are you using? (talkcontribs)

Thank you... I will give that a try... You reply is much appreciated. The database engine is mysql (talkcontribs)

I changed the variables as suggested. Still nothing reported. The same error presents. No error log being triggered... It has me a bit baffled.

Reply to "Site just stopped working - (cannot access the database)"

Official signature for board members

VictorPorton (talkcontribs)

Currently I control a nonprofit organization entirely by myself. As a democratic (in wide sense) person, I want to recruit "board members" and make the decisions and money to be controlled by voting.

New board members can be hired by agreement of most existing board members. Currently I am the only board member.

I want the new board members to sign an official document.

My question: What format to present this document in? Should it be a PDF file? or can it be done as a MediaWiki page (how to style it, possibly for printing?) Should we accept an electronic signature? (If yes, what could be counted as electronic signature? just press of "Agree" button? if yes, what should happen on pressing?) or should we require to send a signed paper?

Reply to "Official signature for board members"

Vector Skin Messed Up After MW 1.26.2 Upgrade

Summary by Ciencia Al Poder
Jon Adcock (talkcontribs)

After upgrading MediaWiki from 1.24.1 to v1.26.2 (Windows) none of my pages display the logo or the top menu (View Edit Read View source View History) or anything outside of the main page frame. I noticed that the navigation pane (sidebar) is displayed below the website data. I downloaded the latest Vector skin and re-installed it but it didn't make any difference. Changing to Modern works OK, but changing back the Vector breaks it again. Any ideas?

Jon Adcock (talkcontribs)

version info: MW: 1.26.2 PHP: 5.5.11 MySQL: 5.7.9 Windows Server 2008 R2 Internal wiki only. (talkcontribs)

Do you still have old files, which may cause errors?

See Upgrade for more information on this issue!

Jon Adcock (talkcontribs)

To "" I have two questions. 1) Specifically what old files are you talking about? I downloaded MW 1.26.2 to a separate directory, so yes I have the original 1.24.1 directory structure. 2) I read "Upgrade" in detail before I upgraded, and again in detail after I ran into this issue post-upgrade. There is NOTHING listed about this issue. What on that "Upgrade" page addresses the Vector skin issue that I listed? (talkcontribs)

What I mean is that you should install the new MediaWiki version into an empty directory and then copy over only those things, which you still need, e.g. LocalSettings.php, the folder images/ and so on. If you have files from your old MediaWiki version inside the new folder, then these files may cause problems. I would have liked to link you the exact section on the Upgrading page, it is called "Files remaining that may cause errors", but the spam filter won't let me.

If you downloaded the tarball of the 1.26 release, then you should not have to download the Vector skin separately again. In contrast it should be included in the 1.26 tarball. Inside the skins/ folder, make sure you delete the folder Vector/ and the file Vector.php. Same for the other skins, which come with the tarball, e.g. Monobook/ and ... you got it. Then put the new folder Vector/ in the skins/ directory.

Jon Adcock (talkcontribs)

OK, I'm a little clearer on what you are saying now. Yes I performed the "upgrade" by extracting the tarball (.tar.gz file) to a new directory structure. Not overwriting the existing directory structure. So there SHOULD have been no "old" files involved. Therefore the "Files remaining that may cause errors" section is N/A.

Regarding the fact that I re-downloaded/re-added the Vector skin, you are correct that I shouldn't have had to, but I did that because Vector was not displaying properly (and it's still not).

Does anyone have any troubleshooting tips on how I can figure this out? (talkcontribs)

Does the wiki have a URL so that I could have a look at it?

In the source code of your wiki pages, there are a few links to load.php. I am guessing that there is something wrong with the output of these load.php calls, if you are using the Vector skin. Maybe one of the according calls gives an error...

Jon Adcock (talkcontribs)

"" it's an internal only site, so no. But good news. I got it working!

I did a lot more "Google'ing" and found several references to a known bug relating to this ( I made my TEMP directory writable for the IIS_IUSR group and that didn't resolve it. But on another site discussing this ( landollweb said that they deleted the files in the TEMP directory and that fixed it for him. So I deleted a bunch of old files/folders in TEMP and it worked for me too.

The Vector skin is working for me now.

Jon Adcock (talkcontribs)

I spoke too soon!

About 5 minutes later, it quit working. I was still seeing the error in the "Web Console" (press F12 in Firefox).

More "Google'ing"... I found the MediaWiki key/variable $wgCacheDirectory. It was set to false. I set it to a specific directory that the IIS_IUSR had permissions to, and it's working again. I hope it lasts for more than 5 minutes... (talkcontribs)

Boa tarde.

Eu carrego uma imagem e ela aparece deste tipo:

Quando clico na imagem ele retorna um error:

Internal Server Error

The server encountered an internal error or misconfiguration and was unable to complete your request.

Ciencia Al Poder (talkcontribs)

It's a possible problem with .htaccess in the upload directory. See Manual:Configuring file uploads#Check .htaccess file. A directive in the .htaccess file may not be allowed in your setup, causing an error when you load a file inside that folder (talkcontribs)

Não consegui compreender.

Abrir o arquivo .htaccess mas não encontrei nada lá dentro.

Você poderia me explicar melhor ?


Ciencia Al Poder (talkcontribs)

Es extraño que el archivo .htaccess esté vacío. Prueba a cambiar el nombre del archivo .htaccess para que no lo tome en cuenta y ver si se produce el error. Si se sigue produciendo el error, deberías consultar el registro de errores de apache, que debería contener un mensaje más detallado del motivo del error. Normalmente está en /var/log/apache/error.log o similar. (talkcontribs)

Vou tentar verificar aqui então.

Obrigado pela ajuda.

2602:306:366A:F1D0:6957:F8DA:139B:BF32 (talkcontribs)

dosn't say if right if typed in right (talkcontribs)

Não entendi mano.

Erro ainda persistem. Faço o upload da imagem e ela me retorna o seguinte erro:

The server encountered an internal error or misconfiguration and was unable to complete your request

Todas as pastas estão com 777 no ftp.

Ciencia Al Poder (talkcontribs)

Este tipo de error normalmente no se debe a permisos.

Solo para confirmar, eliminó o renombró el archivo .htaccess de la carpeta /images/? De ser así, sugiero contactar con el soporte de tu hosting.

Reply to "Problema no upload imagem"

Problem with LDAP after MW 1.26.2 Upgrade

2 (talkcontribs)

I upgraded MW to 1.26.2, and I also updated the LDAPAuthentication extension to the latest version. The domains no longer show up in the dropdown box on the Login page. The dropdown box is now empty. Logins are not working anymore. (talkcontribs)

I solved the issue. I don't think it is MW version related. The update for the LDAPAuthentication extension changed the order in which you can place the config options in LocalSettings.php. You must specify the following options first before any other options:


$wgAuth = new LdapAuthenticationPlugin();

In an older version of the extension, it was perfectly valid to specify these items last. That was useful because I have many separate wiki instances sharing the same MW code base, and I always put these lines in each wiki's custom LocalSettings file. Then, if for some reason I wanted to disable LDAP for a particular wiki, I would just comment out these lines for that wiki. The other wiki instances would continue to use LDAP. I have the domains and the other LDAP options in a global LocalSettings file so that every wiki instance gets the same LDAP domains and settings.

Reply to "Problem with LDAP after MW 1.26.2 Upgrade"

My Wiki do not load after I changed IP Address

AlexMX2016 (talkcontribs)

I was working perfect with my wiki, I installed SSL Certificate successfully, but, since  a requirement for the SSL is that the site must have an Static IP, I decided to change the IP from Dynamic to Static. After the IP I did also change my DNS registers to the new IP Address. Related to the SSL-Certificate all ran pretty well, certificates are found, but in the moment I wanted to load my wiki, I got his in my browser:



* This is the main web entry point for MediaWiki.


* If you are reading this in your web browser, your server is probably

* not configured correctly to run PHP applications!


* See the README, INSTALL, and UPGRADE files for basic setup instructions

* and pointers to the online documentation.




* ----------


* This program is free software; you can redistribute it and/or modify

* it under the terms of the GNU General Public License as published by

* the Free Software Foundation; either version 2 of the License, or

* (at your option) any later version.


* This program is distributed in the hope that it will be useful,

* but WITHOUT ANY WARRANTY; without even the implied warranty of


* GNU General Public License for more details.


* You should have received a copy of the GNU General Public License along

* with this program; if not, write to the Free Software Foundation, Inc.,

* 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.



* @file


// Bail on old versions of PHP, or if composer has not been run yet to install

// dependencies. Using dirname( __FILE__ ) here because __DIR__ is PHP5.3+.

require_once dirname( __FILE__ ) . '/includes/PHPVersionCheck.php';

wfEntryPointCheck( 'index.php' );

require __DIR__ . '/includes/WebStart.php';

$mediaWiki = new MediaWiki();


Why I get this if before the changes the Wiki was working perfect? (talkcontribs)

What you see there is unparsed PHP code. Obviously, the content of .php files now no longer is parsed so that MediaWiki is no longer working. Note that this is not only a functional problem, but this actually is an urgent security problem! You should either work around it by deactivating your domain for now or solve it by making .php files be parsed again.

Ciencia Al Poder (talkcontribs)

Apparently, you disabled PHP while you were changing the configuration to enable SSL

Xdx24 (talkcontribs)

I also met this problem. I deactivated my domain, but still get this message. It pumped up with a download file, I don't know how to configure, any more help? Thanks!

Ciencia Al Poder (talkcontribs)

I think you should ask for support to your hosting provider, if that's a PHP misconfiguration

Reply to "My Wiki do not load after I changed IP Address" (talkcontribs)

Unable to Scribunto/Lua working on our wiki. Getting the following error:

Fatal error: Call to undefined function pcntl_wifsignaled() in/home/jackdl5/public_html/ on line 645Fatal error: Call to undefined function

Permissions for the Engine binaries are all set correctly and both Scribunto and Lua show as being installed on Special:Version.

Any thoughts?

Ciencia Al Poder (talkcontribs)

pcntl_wifsignaled() is a PHP function, that needs to be installed/enabled on the server, although it's not listed as a requirement in Extension:Scribunto. I wonder how many shared host provide that requirement. (talkcontribs)

Because we're on a shared server our host is telling us it's not possible to get this set up, is there another work around?

TheDJ (talkcontribs)

The alternative to luastandalone is luasandbox, but that requires even more influence on the php server I believe.

TheDJ (talkcontribs)

Seems this dependency was introduced in may 2015. (talkcontribs)

Would using an older version pre-May 2015 help combat this issue for now?

TheDJ (talkcontribs)

Apparently this is a known issue logged as phab:T128048. It links to a proposed patch, that has not fully been tested yet, that might workaround this. (talkcontribs)

Believe it or not that actually worked! Pages are loading again, but I'm getting this error now:

Lua error: Internal error: The interpreter has terminated with signal "11".

Next step?

MarkAHershberger (talkcontribs)

I'm glad it worked for you.

Re: Signal 11:

Signal 11, or officially know as "segmentation fault", means that the program accessed a memory location that was not assigned. That's usually a bug in the program.

I'm going to guess that the wrong lua binary is being used. Hmm... Do you have shell access to the machine? Can you run "uname -a" and paste the result here?

Alternatively, if you can create a phpinfo page and copy-paste the result, that may help. (talkcontribs)

Does this help...? (talkcontribs)

Whoops, meant this...

Reply to "Error with Scribunto/Lua"
User587668 (talkcontribs)

How can you create a thumb which links to its full url?

[[File:Example.jpg|200px]] should link to is for a template, so I don't know the URL. [[Media:File:Example.jpg]] is only a text link. (talkcontribs)

Use the filepath magic word. I'd post an example, but this stupid comment system doesn't allow it.

Subfader (talkcontribs)

Reply to "Image thumb link= full url?" (talkcontribs)

Hi, im kinda new. I used Mediawiki verison 1.25.3. And i faced this problem which is Error: LightnCandy class not defined whenever im trying to upload file. Can someone help me.. Kinda desperate and in hurry.. huhuhh.. Thanks (talkcontribs)

This error should not happen, if you installed MediaWiki from an official tarball, which is built for "Upload-Install-Use". So, if all you want is version 1.25.x, then grab a recent tarball of it and make sure you actually uploaded all files.

If you in contrast want to do development with this wiki, then run composer update to get the latest dependencies. If you installed from Git, then you need to do some more steps to set up. The Git version is built for use on wmf wikis only. You can use it, but you need to know the risk and what to do if something doesn't work.

Reply to "LightnCandy class"